Date: Tue, 21 Oct 2008 09:17:16 +0200 From: Thomas Quinot <thomas@FreeBSD.ORG> To: Ben Kaduk <minimarmot@gmail.com> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: delayed panic loading atapicam (after failed burncd) Message-ID: <20081021071716.GA50364@melamine.cuivre.fr.eu.org> In-Reply-To: <47d0403c0810202228s18b21c35ybd073ccfb6548a87@mail.gmail.com> References: <47d0403c0810111730p41bb17feva35729f31d0d2f44@mail.gmail.com> <20081020165449.GB10340@melamine.cuivre.fr.eu.org> <47d0403c0810202228s18b21c35ybd073ccfb6548a87@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* Ben Kaduk, 2008-10-21 : > # kldload atapicam > acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 > cd0 at ata1 bus 0 target 0 lun 0 > cd0: <HL-DT-ST RW/DVD MU10N 1.05> Removable CD-ROM SCSI-0 device > cd0: 3.3000MB/s transfers > cd0: Attempt to query device size failed: NOT READY, Medium not present Looks good. After that point device cd0 does exist, right? > warm boot (no acd0 found): > # kldload atapicam > [nothing] If there's no acd0 that indicates that the ATA layer does not see the drive so it's not completely unepected that ATAPI/CAM, which sits on top of ATA, doesn't see it either. > cold boot: > > # kldload atapicam > acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 > cd0: at ata1 bus 0 target 0 lun 0 > cd0: <HL-DT-ST RW/DVD MU10N 1.05> Removable CD-ROM SCSI-0 device > cd0: 3.300MB/s transfers > cd0: cd present [3778x2048 byte records] > acd0: FAILURE - READ_BIG ILLIGAL REQUEST asc=0x64 ascq=0x00 > (cd0:ata1:0:0:0): READ(10). CDB: 28 0 0 0 e c1 0 0 1 0 > (cd0:ata1:0:0:0): CAM Status: SCSI Status Error > (cd0:ata1:0:0:0): SCSI Status: Check Condition > (cd0:ata1:0:0:0): ILLEGAL REQUEST asc:64,0 > (cd0:ata1:0:0:0): Illegal mode for this track > (cd0:ata1:0:0:0): Unretryable error > (cd0:ata1:0:0:0): cddone got error 0x6 back > [no panic] Does cd0 exist at this point? > warm boot: > # kldload atapicam > [nothing happens] Same as above. For the case of the unit disappearing at warm reboot, it would be interesting to have a complete transcript of a verbose boot (boot -v). To avoid copying everything by hand, you can hook a serial console to your machine and log the messages on a second machine. > I don't have the media that was causing the panic here at home; I'll > try to test that tomorrow and see if the panic > is gone with the new snapshot. OK, thanks, let me know. Thomas.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081021071716.GA50364>