Re: delayed panic loading atapicam (after failed burncd)

On Tue, Oct 21, 2008 at 3:17 AM, Thomas Quinot <thomas_at_freebsd.org> wrote:
> * 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?

yes, /dev/cd0 exists here

>
>> 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.

Quite so.

>
>> 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?

Yes.

>
>> 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).

I took this a few weeks ago, basically when I first got
the machine, but it appears to display the behavior in question:
http://stuff.mit.edu/afs/sipb.mit.edu/user/kaduk/freebsd/prolix/dmesg.verbose


-Ben Kaduk

> 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.
>
>