Re: 2.6.11-rc[1,2]-mmX scsi cdrom problem, 2.6.10-mm2 ok

2005-01-31 Thread Jens Axboe
On Mon, Jan 31 2005, Douglas Gilbert wrote: > Jens Axboe wrote: > >On Mon, Jan 31 2005, Douglas Gilbert wrote: > > > >>Jens Axboe wrote: > >> > >>>On Mon, Jan 31 2005, Fabio Coatti wrote: > >>> > >>> > Alle 09:00, lunedì 31 gennaio 2005, Jens Axboe ha scritto: > > > >>At this

Re: 2.6.11-rc[1,2]-mmX scsi cdrom problem, 2.6.10-mm2 ok

2005-01-31 Thread Douglas Gilbert
Jens Axboe wrote: On Mon, Jan 31 2005, Douglas Gilbert wrote: Jens Axboe wrote: On Mon, Jan 31 2005, Fabio Coatti wrote: Alle 09:00, lunedì 31 gennaio 2005, Jens Axboe ha scritto: At this point k3b is stuck in D stat, needs reboot. I was able to replicate this with a USB burner. My system didn't

Re: 2.6.11-rc[1,2]-mmX scsi cdrom problem, 2.6.10-mm2 ok

2005-01-31 Thread Jens Axboe
On Mon, Jan 31 2005, Douglas Gilbert wrote: > Jens Axboe wrote: > >On Mon, Jan 31 2005, Fabio Coatti wrote: > > > >>Alle 09:00, lunedì 31 gennaio 2005, Jens Axboe ha scritto: > >> > At this point k3b is stuck in D stat, needs reboot. > >>> > >>>The most likely suspect is the REQ_BLOCK_PC scsi

Re: 2.6.11-rc[1,2]-mmX scsi cdrom problem, 2.6.10-mm2 ok

2005-01-31 Thread Douglas Gilbert
Jens Axboe wrote: On Mon, Jan 31 2005, Fabio Coatti wrote: Alle 09:00, lunedì 31 gennaio 2005, Jens Axboe ha scritto: At this point k3b is stuck in D stat, needs reboot. The most likely suspect is the REQ_BLOCK_PC scsi changes. Can you try 2.6.11-rc2-mm1 with bk-scsi backed out? (attached) just

Re: 2.6.11-rc[1,2]-mmX scsi cdrom problem, 2.6.10-mm2 ok

2005-01-31 Thread Jens Axboe
On Mon, Jan 31 2005, Fabio Coatti wrote: > Alle 09:00, lunedì 31 gennaio 2005, Jens Axboe ha scritto: > > > > > At this point k3b is stuck in D stat, needs reboot. > > > > The most likely suspect is the REQ_BLOCK_PC scsi changes. Can you try > > 2.6.11-rc2-mm1 with bk-scsi backed out? (attached) >

Re: 2.6.11-rc[1,2]-mmX scsi cdrom problem, 2.6.10-mm2 ok

2005-01-31 Thread Fabio Coatti
Alle 09:00, lunedà 31 gennaio 2005, Jens Axboe ha scritto: > > > At this point k3b is stuck in D stat, needs reboot. > > The most likely suspect is the REQ_BLOCK_PC scsi changes. Can you try > 2.6.11-rc2-mm1 with bk-scsi backed out? (attached) just tried, right guess :) backing out that patch the

Re: 2.6.11-rc[1,2]-mmX scsi cdrom problem, 2.6.10-mm2 ok

2005-01-31 Thread Jens Axboe
On Mon, Jan 31 2005, Fabio Coatti wrote: > I'm seeing a problem with latest mm releases; with 2.6.11-rc1,2-mmX every > time > I fire up k3b, it get stuck here: (last line, previous lines just for > documentation :) ) > > open("/dev/hdc", O_RDONLY|O_NONBLOCK) = 11 > ioctl(11,

Re: 2.6.11-rc[1,2]-mmX scsi cdrom problem, 2.6.10-mm2 ok

2005-01-31 Thread Jens Axboe
On Mon, Jan 31 2005, Douglas Gilbert wrote: Jens Axboe wrote: On Mon, Jan 31 2005, Douglas Gilbert wrote: Jens Axboe wrote: On Mon, Jan 31 2005, Fabio Coatti wrote: Alle 09:00, lunedì 31 gennaio 2005, Jens Axboe ha scritto: At this point k3b is stuck in D stat, needs reboot. I

Re: 2.6.11-rc[1,2]-mmX scsi cdrom problem, 2.6.10-mm2 ok

2005-01-31 Thread Douglas Gilbert
Jens Axboe wrote: On Mon, Jan 31 2005, Douglas Gilbert wrote: Jens Axboe wrote: On Mon, Jan 31 2005, Fabio Coatti wrote: Alle 09:00, lunedì 31 gennaio 2005, Jens Axboe ha scritto: At this point k3b is stuck in D stat, needs reboot. I was able to replicate this with a USB burner. My system didn't

Re: 2.6.11-rc[1,2]-mmX scsi cdrom problem, 2.6.10-mm2 ok

2005-01-31 Thread Jens Axboe
On Mon, Jan 31 2005, Fabio Coatti wrote: I'm seeing a problem with latest mm releases; with 2.6.11-rc1,2-mmX every time I fire up k3b, it get stuck here: (last line, previous lines just for documentation :) ) open(/dev/hdc, O_RDONLY|O_NONBLOCK) = 11 ioctl(11, CDROM_SEND_PACKET,

2.6.11-rc[1,2]-mmX scsi cdrom problem, 2.6.10-mm2 ok

2005-01-30 Thread Fabio Coatti
I'm seeing a problem with latest mm releases; with 2.6.11-rc1,2-mmX every time I fire up k3b, it get stuck here: (last line, previous lines just for documentation :) ) open("/dev/hdc", O_RDONLY|O_NONBLOCK) = 11 ioctl(11, CDROM_SEND_PACKET, 0xbfffc4e0) = 0 close(11)