kern/103602: atapi device not working on JMicron 363 Controller

[Thomas Quinot]

The following reply was made to PR kern/103602; it has been noted by GNATS.

From: Thomas Quinot <thomas at FreeBSD.ORG>
To: Josh Carroll <josh.carroll at psualum.com>
Cc: FreeBSD-gnats-submit at freebsd.org, greg at rowes.org
Subject: Re: kern/103602: atapi device not working on JMicron 363 Controller
Date: Mon, 16 Oct 2006 00:25:41 +0200

 * Josh Carroll, 2006-09-27 :
 
 > Booting with CAMDEBUG options, as soon as it tries to mount root (and
 > query the CD device), I get:
 > 
 > atapi_action: hcb at 0xc66c6400: 12 0 0 0 24 0
 > atapi_cb: hcb at 0xc66c6400 error = 00: (sk = 00)
 > dev acd0: cmd 12 status 50 result 00
 > (probe0:ata2:0:1:0): . CDB: 12 0 0 0 60 0
 > atapi_action: hcb at 0xc66c63c0: 12 0 0 0 60 0
 > atapi_cb: hcb at 0xc66c63c0 error = 00: (sk = 00)
 > dev acd0: cmd 12 status 50 result 00
 > (probe0:ata2:0:1:0): . CDB: 12 1 80 0 ff 0
 > atapi_action: hcb at 0xc66c6380: 12 1 80 0 ff 0
 > 
 > At that point, I rebooted the box, but letting it run longer results
 > in similar messages with different addresses and values. I have two
 > pictures available here that show the screen (the box locks up in
 > single user mode at that point, I cannot ctrl-c it):
 
 I'm not sure I'm following the sequence of events here. Do you mean that
 enabling CAM debugging prevents the machine from going far enough into
 the boot process to let you reproduce the problem you described earlier?
 
 Thomas.