From owner-freebsd-bugs@FreeBSD.ORG  Sun Oct 15 22:30:34 2006
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
X-Original-To: freebsd-bugs@hub.freebsd.org
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id AFB0016A4EB
	for <freebsd-bugs@hub.freebsd.org>;
	Sun, 15 Oct 2006 22:30:34 +0000 (UTC)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0EF2343D45
	for <freebsd-bugs@hub.freebsd.org>;
	Sun, 15 Oct 2006 22:30:30 +0000 (GMT)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
	by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k9FMUU4A055105
	for <freebsd-bugs@freefall.freebsd.org>; Sun, 15 Oct 2006 22:30:30 GMT
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k9FMUUQ5055103;
	Sun, 15 Oct 2006 22:30:30 GMT (envelope-from gnats)
Date: Sun, 15 Oct 2006 22:30:30 GMT
Message-Id: <200610152230.k9FMUUQ5055103@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
From: Thomas Quinot <thomas@FreeBSD.ORG>
Cc: 
Subject: Re: kern/103602: atapi device not working on JMicron 363 Controller
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Thomas Quinot <thomas@FreeBSD.ORG>
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Oct 2006 22:30:34 -0000

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

From: Thomas Quinot <thomas@FreeBSD.ORG>
To: Josh Carroll <josh.carroll@psualum.com>
Cc: FreeBSD-gnats-submit@freebsd.org, greg@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@0xc66c6400: 12 0 0 0 24 0
 > atapi_cb: hcb@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@0xc66c63c0: 12 0 0 0 60 0
 > atapi_cb: hcb@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@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.