Re: ATACD issues slowly coming back...
It seems Vadim Belman wrote: > > > Bruce Cran wrote: > > > Your CD drive should indeed support UDMA33 - my DVD drive supports > > UDMA33, and my CDRW supports multi-word DMA, even though my BIOS only > > ever configures it for PIO4, and my DVD for UDMA33. FreeBSD only ever > > configures them for PIO during bootup, but, using the atacontrol > > program, it configures them both for maximum speed, even knowing they > > _can_ only do UDMA33,WDMA2. > > If you have a look at sysctl hw.ata tree, it'll give you the clue on > how to overcome this behaviuor. In simple words, what you need is to poot > > hw.ata.atapi_dma=1 > > in your /boot/loader.conf and have the nirvana of automatic DMA > detection... And remember the warning that it does not always work as expected, ATAPI DMA is a many headed monster... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATACD issues slowly coming back...
Bruce Cran wrote: Your CD drive should indeed support UDMA33 - my DVD drive supports UDMA33, and my CDRW supports multi-word DMA, even though my BIOS only ever configures it for PIO4, and my DVD for UDMA33. FreeBSD only ever configures them for PIO during bootup, but, using the atacontrol program, it configures them both for maximum speed, even knowing they _can_ only do UDMA33,WDMA2. If you have a look at sysctl hw.ata tree, it'll give you the clue on how to overcome this behaviuor. In simple words, what you need is to poot hw.ata.atapi_dma=1 in your /boot/loader.conf and have the nirvana of automatic DMA detection... -- /Voland Vadim Belman http://www.lflat.org http://www.lflat.net To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATACD issues slowly coming back...
On Sun, Dec 08, 2002 at 07:43:48PM -0700, Cliff L. Biffle wrote: > On Sunday 08 December 2002 03:28 pm, Bruce Cran wrote: > > I've got a A7V-266E motherboard with a KT266A chipset. The > > solution in my case was to tell the BIOS I didn't have any ATAPI drives. > > FreeBSD then found everything properly, without any problems - I think > > the BIOS was maybe configuring the master for UDMA33 and the slave for > > PIO4, whereas FreeBSD seems to prefer them both as PIO4, > > That just about makes sense, with the weirdnesses I've seen with this mobo in > the past. I'll give that a go and let y'all know what I find. I've got the > ATACD on its own channel because I've hit issues in the past with having a > DMA and PIO device on the same channel with this controller, but from reading > my boot messages this morning my CD drive thinks it supports UDMA 33. Go > fig. > > I should probably also sup the machine past DP2, but it's just been so > wonderfully stable...I'm so used to using -stable that this feels like > pushing my luck. :-) Your CD drive should indeed support UDMA33 - my DVD drive supports UDMA33, and my CDRW supports multi-word DMA, even though my BIOS only ever configures it for PIO4, and my DVD for UDMA33. FreeBSD only ever configures them for PIO during bootup, but, using the atacontrol program, it configures them both for maximum speed, even knowing they _can_ only do UDMA33,WDMA2. -- Bruce Cran To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATACD issues slowly coming back...
On Sunday 08 December 2002 03:28 pm, Bruce Cran wrote: > I've got a A7V-266E motherboard with a KT266A chipset. The > solution in my case was to tell the BIOS I didn't have any ATAPI drives. > FreeBSD then found everything properly, without any problems - I think > the BIOS was maybe configuring the master for UDMA33 and the slave for > PIO4, whereas FreeBSD seems to prefer them both as PIO4, That just about makes sense, with the weirdnesses I've seen with this mobo in the past. I'll give that a go and let y'all know what I find. I've got the ATACD on its own channel because I've hit issues in the past with having a DMA and PIO device on the same channel with this controller, but from reading my boot messages this morning my CD drive thinks it supports UDMA 33. Go fig. I should probably also sup the machine past DP2, but it's just been so wonderfully stable...I'm so used to using -stable that this feels like pushing my luck. :-) Thanks! -Cliff L. Biffle To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATACD issues slowly coming back...
On Fri, Dec 06, 2002 at 02:35:45PM -0700, Cliff L. Biffle wrote: > I mentioned earlier on the list that the ATA issues I'd been having with 4.7 > had disappeared since installing 5.0. They're still much less frequent -- > i.e. I can burn CDs now -- but I just got one of the old messages and wanted > to submit it for your perusal. > > cliff50 kernel: acd0: READ_BIG - MEDIUM ERROR asc=0x11 ascq=0x00 error=0x00 > > I'm not well versed on the ATA command set, but that looks like a command to > the drive failing to execute. Is this likely to be the drive, the > controller, both, or is it impossible to tell from the data set? > > This is on the aforementioned potentially-buggy Apollo KT133 chipset, but it's > never reported these errors on my hard disk (knock on wood), only the CD > drive. They -are- on separate channels. > > I'll see what information I can collect here, but suggestions on where to look > are appreciated. I reported a panic under -CURRENT a few days ago (see ATA/ATAPI related panic). When I tested out DP1 I never saw any ATAPI problems, but since trying DP2 I have, once more, seen errors. I've got a A7V-266E motherboard with a KT266A chipset. The solution in my case was to tell the BIOS I didn't have any ATAPI drives. FreeBSD then found everything properly, without any problems - I think the BIOS was maybe configuring the master for UDMA33 and the slave for PIO4, whereas FreeBSD seems to prefer them both as PIO4, but I really don't know. I kept seeing READ_CAPACITY and READ_BIG timeouts, along with data overrun errors. I think it probably is the controller, because even with no drives connected, my computer paused for a good few seconds while trying to probe the io/irq - it found the primary (which only has a hard drive on it) immediately, but paused far too long trying to find the secondary. -- Bruce Cran To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATACD issues slowly coming back...
It seems Cliff L. Biffle wrote: > I mentioned earlier on the list that the ATA issues I'd been having with 4.7 > had disappeared since installing 5.0. They're still much less frequent -- > i.e. I can burn CDs now -- but I just got one of the old messages and wanted > to submit it for your perusal. > > cliff50 kernel: acd0: READ_BIG - MEDIUM ERROR asc=0x11 ascq=0x00 error=0x00 This means the driver couldn't read a chunk of data of the media due to it being bad (damaged/scratched/dirty)... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ATACD issues slowly coming back...
I mentioned earlier on the list that the ATA issues I'd been having with 4.7 had disappeared since installing 5.0. They're still much less frequent -- i.e. I can burn CDs now -- but I just got one of the old messages and wanted to submit it for your perusal. cliff50 kernel: acd0: READ_BIG - MEDIUM ERROR asc=0x11 ascq=0x00 error=0x00 I'm not well versed on the ATA command set, but that looks like a command to the drive failing to execute. Is this likely to be the drive, the controller, both, or is it impossible to tell from the data set? This is on the aforementioned potentially-buggy Apollo KT133 chipset, but it's never reported these errors on my hard disk (knock on wood), only the CD drive. They -are- on separate channels. I'll see what information I can collect here, but suggestions on where to look are appreciated. -Cliff L. Biffle To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
