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 differ
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
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: Removable CD-ROM SCSI-0 device
> > cd0: 33.000MB/s transfers
> > cd0: cd present [3737169375 x 3737169374 byte records]
>
> Several others have reported similar
Le 2003-09-13, Daniel Eischen écrivait :
> cd0 at ata1 bus 0 target 0 lun 0
> cd0: 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 data.
I suspect a problem in t
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 se
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 wr
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 do
> 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
> > xpt_
> 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
> > C
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
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,d439f00
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
always crash, but does so fairly frequently and leaves my laptop
l
12 matches
Mail list logo
