Date: Thu, 21 Mar 2002 21:25:55 -0700 From: Brad Jones <brad@kazrak.com> To: freebsd-stable@freebsd.org Subject: ATAPI issues with new ATA merge... Message-ID: <20020321212555.E39968@ophiuchus.kazrak.com>
next in thread | raw e-mail | index | archive | help
I ended up making two changes at the same time (well, three, but one was undoable and undoing it didn't fix anything), so I can't strictly guarantee that either of these is the fault of the new ATA code and not my new CDRW drive...however, since the drive seems to work for other things (burning ISOs) and at least one of the issues seems to be in the driver, I figured I'd throw it out here to see if anyone had ideas and/or fixes. 1) Ripping audio CDs hangs for no readily apparent reason. cdda2wav processes will just...stop. They're then stuck in disk-wait (ps state 'D', top state 'atprq') forever. I've rebuild the cdrtools port...no change. I can then run another cdda2wav, and it may work just fine...it may hang...no way to tell. No error messages are printed, nothing is added to dmesg or syslog. The process just stops where it is and never wakes up. dagrab has the same problem; no error message, no dmesg or syslog output...it just stops. 2) Burning VCDs doesn't seem to work. The command: 'burncd -s 4 -f /dev/cdrom vcd VCD.bin fixate' gives the following error message: writing from file VCD.bin size 391497 KB only wrote -1 of 37632 bytes err=5 I'll provide a full dmesg if anyone thinks it'll be useful; 'dmesg | grep ata' gives: atapci0: <VIA 82C686 ATA66 controller> port 0xd800-0xd80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 atapci1: <Promise ATA100 controller> port 0x7400-0x743f,0x7800-0x7803,0x8000-0x8007,0x8400-0x8403,0x8800-0x8807 mem 0xda000000-0xda01ffff irq 10 at device 17.0 on pci0 ata2: at 0x8800 on atapci1 ata3: at 0x8000 on atapci1 ad4: 76319MB <WDC WD800BB-53BSA0> [155061/16/63] at ata2-master UDMA100 ad6: 43979MB <IBM-DTLA-307045> [89355/16/63] at ata3-master UDMA100 acd0: CD-RW <PLEXTOR CD-R PX-W2410A> at ata0-master PIO4 (The third change, mentioned above, was setting hw.ata.atapi_dma to 1, which caused the last line of that dmesg to have UDMA33 instead of PIO4. The symptoms above occurred under both modes.) Any suggestions? Any information I can provide that may help people figure out the problem? BJ -- Brad Jones -- brad@kazrak.com "The line between good and evil, hope and despair, does not divide the world between 'us' and 'them'. It runs down the middle of each one of us." -- Robert Fulghum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020321212555.E39968>