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: <PLEXTOR CD-ROM PX-40TS 1.13> at scbus0 target 5 lun 0 (pass0,cd0) <COMPAQ ST15150W 6216> at scbus1 target 0 lun 0 (pass1,da0) <COMPAQ DFHSS4W 4343> at scbus1 target 1 lun 0 (pass2,da1) <PLEXTOR CD-R PX-W1210A 1.09> at scbus2 target 0 lun 0 (pass3,cd1) <CREATIVE DVD5240E-1 1.30> at scbus2 target 1 lun 0 (pass4,cd2) current version of OS: [EMAIL PROTECTED]:~ > uname -a FreeBSD Noisy.localhost.localdomain 5.0-RELEASE-p3 FreeBSD 5.0-RELEASE-p3 #0: Mon Feb 24 16:01:23 CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NOISY5 i386 The full dmesg-output, kernel-config can be found at <http://users.pandora.be/bomberboy/fbsd5/> 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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
