Re: scsi_cd or atapicam crash in current.

2003-09-16 Thread Thomas Quinot
Le 2003-09-13, Daniel Eischen écrivait : cd0 at ata1 bus 0 target 0 lun 0 cd0: HL-DT-ST RW/DVD GCC-4240N D110 Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: cd present [3737169375 x 3737169374 byte records] Several others have reported similar completely bogus sector size

Re: scsi_cd or atapicam crash in current.

2003-09-16 Thread Daniel Eischen
On Tue, 16 Sep 2003, Thomas Quinot wrote: Le 2003-09-13, Daniel Eischen écrivait : cd0 at ata1 bus 0 target 0 lun 0 cd0: HL-DT-ST RW/DVD GCC-4240N D110 Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: cd present [3737169375 x 3737169374 byte records] Several others

Re: scsi_cd or atapicam crash in current.

2003-09-16 Thread Thomas Quinot
Le 2003-09-16, Daniel Eischen écrivait : I get this even without atapicam in the kernel. Is trying CAMDEBUG and CAM_DEBUG_CDB going to show anything interesting? No, indeed, probably not. Can you try the following patch: Index: ata-lowlevel.c

Re: scsi_cd or atapicam crash in current.

2003-09-16 Thread Daniel Eischen
On Tue, 16 Sep 2003, Thomas Quinot wrote: Le 2003-09-16, Daniel Eischen écrivait : I get this even without atapicam in the kernel. Is trying CAMDEBUG and CAM_DEBUG_CDB going to show anything interesting? No, indeed, probably not. Can you try the following patch: OK, on a different

Re: scsi_cd or atapicam crash in current.

2003-09-13 Thread Vladimir Kushnir
Hello, here camcontrol still shows bogus numbers when there's no CD: #camcontrol cmd cd0 -v -c 25 0 0 0 0 0 0 0 0 0 -i 8 i4 i4 -791621424 -791621424 No boot crashes, though, only the usual ones due to cdrecord usage which nobody seem to care about :-( On Fri, 12 Sep 2003, Kenneth D. Merry

Re: scsi_cd or atapicam crash in current.

2003-09-13 Thread Daniel Eischen
On Sun, 14 Sep 2003, Vladimir Kushnir wrote: Hello, here camcontrol still shows bogus numbers when there's no CD: #camcontrol cmd cd0 -v -c 25 0 0 0 0 0 0 0 0 0 -i 8 i4 i4 -791621424 -791621424 No boot crashes, though, only the usual ones due to cdrecord usage which nobody seem to care

Re: scsi_cd or atapicam crash in current.

2003-09-12 Thread Thomas Quinot
Le 2003-09-12, Kevin Oberman écrivait : cdstart(c419d500,c4192000,1,c407cc30,c407cc00) at cdstart+0xcb xpt_run_dev_allocq(c40b8c00,c407cc08,1,c418d800,c419d500) at xpt_run_dev_allocq+0xab xpt_schedule(c419d500,1,0,ce54ec78,dd5b6c70) at xpt_schedule+0xca cdstrategy(ce54ec78,0,0,0,d439f000)

Re: scsi_cd or atapicam crash in current.

2003-09-12 Thread Kenneth D. Merry
On Fri, Sep 12, 2003 at 08:57:22 -0700, Kevin Oberman wrote: I am seeing a peculiar, possibly timing sensitive, crash that looks like if is probably in either atapicam or scsi_cd. The system is CURRENT as of yesterday morning. The crash happens frequently when nautilus starts up. It does not

Re: scsi_cd or atapicam crash in current.

2003-09-12 Thread Kevin Oberman
Date: Fri, 12 Sep 2003 10:50:39 -0600 From: Kenneth D. Merry [EMAIL PROTECTED] On Fri, Sep 12, 2003 at 08:57:22 -0700, Kevin Oberman wrote: I am seeing a peculiar, possibly timing sensitive, crash that looks like if is probably in either atapicam or scsi_cd. The system is CURRENT as of

Re: scsi_cd or atapicam crash in current.

2003-09-12 Thread Kevin Oberman
Date: Fri, 12 Sep 2003 18:50:30 +0200 From: Thomas Quinot [EMAIL PROTECTED] Le 2003-09-12, Kevin Oberman écrivait : cdstart(c419d500,c4192000,1,c407cc30,c407cc00) at cdstart+0xcb xpt_run_dev_allocq(c40b8c00,c407cc08,1,c418d800,c419d500) at xpt_run_dev_allocq+0xab

Re: scsi_cd or atapicam crash in current.

2003-09-12 Thread Glenn Johnson
On Fri, Sep 12, 2003 at 08:57:22AM -0700, Kevin Oberman wrote: I am seeing a peculiar, possibly timing sensitive, crash that looks like if is probably in either atapicam or scsi_cd. The system is CURRENT as of yesterday morning. The crash happens frequently when nautilus starts up. It does