From owner-freebsd-current Mon Feb 24 8: 6:13 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B34B937B401 for ; Mon, 24 Feb 2003 08:06:10 -0800 (PST) Received: from eos.telenet-ops.be (eos.telenet-ops.be [195.130.132.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 36C8A43F75 for ; Mon, 24 Feb 2003 08:06:09 -0800 (PST) (envelope-from bruno.van.den.bossche@pandora.be) Received: from localhost (localhost.localdomain [127.0.0.1]) by eos.telenet-ops.be (Postfix) with SMTP id 5536C1FFB4 for ; Mon, 24 Feb 2003 17:06:06 +0100 (CET) Received: from Noisy.localhost.localdomain (D5E087A3.kabel.telenet.be [213.224.135.163]) by eos.telenet-ops.be (Postfix) with SMTP id 2AF441FFAA for ; Mon, 24 Feb 2003 17:06:06 +0100 (CET) Date: Mon, 24 Feb 2003 17:06:05 +0100 From: Bruno Van Den Bossche To: current@freebsd.org Subject: Atapicam-error when dma is not turned on Message-Id: <20030224170605.629888cf.bruno.van.den.bossche@pandora.be> X-Mailer: Sylpheed version 0.8.10 (GTK+ 1.2.10; i386-portbld-freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Since I upgraded to 5.0-Release the cam-stuff acted a bit weird. During the boot-proces, right after the SCSI-bus reset it gives these messages: (probe1:ata0:0:1:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe1:ata0:0:1:0): CAM Status: SCSI Status Error (probe1:ata0:0:1:0): SCSI Status: Check Condition (probe1:ata0:0:1:0): ABORTED COMMAND asc:4b,0 (probe1:ata0:0:1:0): Data phase error (probe1:ata0:0:1:0): Retrying Command (per Sense Data) (probe1:ata0:0:1:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe1:ata0:0:1:0): CAM Status: SCSI Status Error (probe1:ata0:0:1:0): SCSI Status: Check Condition (probe1:ata0:0:1:0): ABORTED COMMAND asc:4b,0 (probe1:ata0:0:1:0): Data phase error (probe1:ata0:0:1:0): Retrying Command (per Sense Data) (probe1:ata0:0:1:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe1:ata0:0:1:0): CAM Status: SCSI Status Error (probe1:ata0:0:1:0): SCSI Status: Check Condition (probe1:ata0:0:1:0): ABORTED COMMAND asc:4b,0 (probe1:ata0:0:1:0): Data phase error (probe1:ata0:0:1:0): Retrying Command (per Sense Data) (probe1:ata0:0:1:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe1:ata0:0:1:0): CAM Status: SCSI Status Error (probe1:ata0:0:1:0): SCSI Status: Check Condition (probe1:ata0:0:1:0): ABORTED COMMAND asc:4b,0 (probe1:ata0:0:1:0): Data phase error (probe1:ata0:0:1:0): Retrying Command (per Sense Data) (probe1:ata0:0:1:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe1:ata0:0:1:0): CAM Status: SCSI Status Error (probe1:ata0:0:1:0): SCSI Status: Check Condition (probe1:ata0:0:1:0): ABORTED COMMAND asc:4b,0 (probe1:ata0:0:1:0): Data phase error (probe1:ata0:0:1:0): Retries Exhausted (probe1:ata0:0:1:0): INQUIRY. CDB: 12 0 0 0 5f 0 (probe1:ata0:0:1:0): CAM Status: SCSI Status Error (probe1:ata0:0:1:0): SCSI Status: Check Condition (probe1:ata0:0:1:0): ABORTED COMMAND asc:4b,0 (probe1:ata0:0:1:0): Data phase error (probe1:ata0:0:1:0): Retrying Command (per Sense Data) My system is overclocked, and the error doesn't appear at boot-time when I run it at default speed. But it still gives me some trouble once running. For example 'cdrecord -scanbus' tends to hang. Not every time, but sometimes it does. And it can be reproduced by executing that command rapidly a few times. After that I can't kill it anymore. Not even with kill -9. If dma for atapi-devices is turned on, no problems arise, and everyting seems to be working fine. The motherboard is an Abit-VP6 and the drive that's giving me trouble is a Compaq dvd-drive, but it has been flashed with Creative-firmware (to make it region-free). The output of 'camcontrol devlist' is: at scbus0 target 5 lun 0 (pass0,cd0) at scbus1 target 0 lun 0 (pass1,da0) at scbus1 target 1 lun 0 (pass2,da1) at scbus2 target 0 lun 0 (pass3,cd1) at scbus2 target 1 lun 0 (pass4,cd2) current version of OS: bomberboy@Noisy:~ > uname -a FreeBSD Noisy.localhost.localdomain 5.0-RELEASE-p3 FreeBSD 5.0-RELEASE-p3 #0: Mon Feb 24 16:01:23 CET 2003 root@Noisy.localhost.localdomain:/usr/obj/usr/src/sys/NOISY5 i386 The full dmesg-output, kernel-config can be found at As I said, everything seems to be working fine with dma turned on and I haven't encountered any problems so far. Maybe (/probably?) it just is the hardware, but I don't really have the spare hardware to test. But the problem never occured while I was using 4.7 So I figured I should at least mention the problem on this list. If I need to do some more tests or supply more info, I'll be glad to (try and) help. Thanks. -- Bruno The soul would have no rainbow had the eyes no tears. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message