Re: ATAng issues status report
Nate Lawson <[EMAIL PROTECTED]> writes: >> > * Lost interrupt for ATA-SLAVE on reboot. Last event: 2003/10/7 >> > I'm unsure if this is actually a problem but occasionally it prints a >> > message right before rebooting about loosing an interrupt. I'll try to >> > get more info. I'm getting "missing interrupt" messages from ATAng on one of my older PPro200 machines that was stable with a June kernel, but is not with an October 22 kernel. I don't know that they're related, and I haven't had a chance to look more deeply into it yet. These are the only suspicious messages that make it into the log. The de0-related messages have always happened with no harm. Oct 23 16:52:21 mole kernel: de0: abnormal interrupt: transmit underflow (raising TX threshold to 96|256) Oct 23 16:54:14 mole kernel: de0: abnormal interrupt: transmit underflow (raising TX threshold to 128|512) Oct 23 17:07:31 mole kernel: de0: abnormal interrupt: transmit underflow (raising TX threshold to 160|1024) Oct 23 22:59:41 mole kernel: ad2: WARNING - WRITE_DMA recovered from missing interrupt It's an old machine, but it's never had any serious problems before. Now it hangs hard every day. It doesn't panic or drop into DDB. ata0-slave: pio=0x0c wdma=0x22 udma=0x cable=40pin ata0-master: pio=0x0c wdma=0x22 udma=0x44 cable=40pin ad0: setting WDMA2 on Intel PIIX3 chip ad0: ATA-4 disk at ata0-master ad0: 9541MB (19541088 sectors), 19386 C, 16 H, 63 S, 512 B ad0: 16 secs/int, 1 depth queue, WDMA2 [0] f:80 typ:165 s(CHS):0/1/1 e(CHS):1023/15/63 s:63 l:19541025 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 acd0: setting PIO4 on Intel PIIX3 chip acd0: CDRW drive at ata0 as slave acd0: read 5512KB/s (5512KB/s) write 2067KB/s (2067KB/s), 2048KB buffer, PIO4 ... ata1-master: pio=0x0c wdma=0x22 udma=0x45 cable=80pin ad2: setting WDMA2 on Intel PIIX3 chip ad2: ATA-6 disk at ata1-master ad2: 58623MB (120060864 sectors), 119108 C, 16 H, 63 S, 512 B ad2: 16 secs/int, 1 depth queue, WDMA2 I've configured a console that will allow invoking DDB with ctrl-alt-esc, so I'll try to gether more information. regards, -- Robert ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATAng issues status report
Saturday, October 25, 2003, 7:51:58 AM, you wrote: >>> * Resume fails, hanging with drive light on. Last event: 2003/10/2 >>> Appears to be a lost interrupt during reset. >> >> I've just committed some changes that makes suspend/resume work just >> fine on the notebooks I have access to. > > This works great for me! I have suspended/resumed to S3 many times now, > no problems. Still problems with a Compaq Armada M700. During resume it freezes on resetting ata1, after done ata0. An information that may be useful: about one/two weeks ago the booting process was halting for 30 seconds on ata1 (where no devices are attached), while with the latest commits it doesn't halt anymore. -- Alex Dupre [EMAIL PROTECTED] http://www.alexdupre.com/ [EMAIL PROTECTED] Today's excuse: Just type 'mv * /dev/null'. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATAng issues status report
It seems Nate Lawson wrote: > > > * Panic occurs after ATAFD fails to probe. Last event: 2003/10/6 > > > I have no ATAFD device on my system and normally no messages are printed > > > about it on boot. However, periodically ATAFD will print a bunch of > > > messages on console about failing to probe. The machine works normally > > > but at some point during use, it panics with a re-use of freed memory, > > > last user was ATAFD. Most of the time the machine doesn't print anything > > > about ATAFD and there is no panic but maybe 1/5 reboots it does. > > > > This should be fixed in current. > > Fixed for me. Sometimes acd0 takes a little longer to probe but otherwise > I have not been able to recreate the panic now. Good! > > > * Resume fails, hanging with drive light on. Last event: 2003/10/2 > > > Appears to be a lost interrupt during reset. > > > > I've just committed some changes that makes suspend/resume work just > > fine on the notebooks I have access to. > > This works great for me! I have suspended/resumed to S3 many times now, > no problems. Excelent! > > > * Lost interrupt for ATA-SLAVE on reboot. Last event: 2003/10/7 > > > I'm unsure if this is actually a problem but occasionally it prints a > > > message right before rebooting about loosing an interrupt. I'll try to > > > get more info. > > > > No idea about that on. > > It's gone as well. I can't reproduce any more whereas before I could > reproduce often. So now I have no problems with ATAng and I can run > it on all [EMAIL PROTECTED] panic Okies, so you are a happy camper :) -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATAng issues status report
On Fri, 10 Oct 2003, Soren Schmidt wrote: > It seems Nate Lawson wrote: > > Here is an updated status of ATAng for me. I periodically test it to see > > if any of the following problems go away. > > > > * Panic occurs after ATAFD fails to probe. Last event: 2003/10/6 > > I have no ATAFD device on my system and normally no messages are printed > > about it on boot. However, periodically ATAFD will print a bunch of > > messages on console about failing to probe. The machine works normally > > but at some point during use, it panics with a re-use of freed memory, > > last user was ATAFD. Most of the time the machine doesn't print anything > > about ATAFD and there is no panic but maybe 1/5 reboots it does. > > This should be fixed in current. Fixed for me. Sometimes acd0 takes a little longer to probe but otherwise I have not been able to recreate the panic now. > > * Resume fails, hanging with drive light on. Last event: 2003/10/2 > > Appears to be a lost interrupt during reset. > > I've just committed some changes that makes suspend/resume work just > fine on the notebooks I have access to. This works great for me! I have suspended/resumed to S3 many times now, no problems. > > * Lost interrupt for ATA-SLAVE on reboot. Last event: 2003/10/7 > > I'm unsure if this is actually a problem but occasionally it prints a > > message right before rebooting about loosing an interrupt. I'll try to > > get more info. > > No idea about that on. It's gone as well. I can't reproduce any more whereas before I could reproduce often. So now I have no problems with ATAng and I can run it on all [EMAIL PROTECTED] panic ;-) Thanks again, Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ATAng issues status report
Here is an updated status of ATAng for me. I periodically test it to see if any of the following problems go away. * Panic occurs after ATAFD fails to probe. Last event: 2003/10/6 I have no ATAFD device on my system and normally no messages are printed about it on boot. However, periodically ATAFD will print a bunch of messages on console about failing to probe. The machine works normally but at some point during use, it panics with a re-use of freed memory, last user was ATAFD. Most of the time the machine doesn't print anything about ATAFD and there is no panic but maybe 1/5 reboots it does. * Resume fails, hanging with drive light on. Last event: 2003/10/2 Appears to be a lost interrupt during reset. * Lost interrupt for ATA-SLAVE on reboot. Last event: 2003/10/7 I'm unsure if this is actually a problem but occasionally it prints a message right before rebooting about loosing an interrupt. I'll try to get more info. Device is Intel 82801CA/CAM ICH3 ATA100 controller. There are no slave devices, just one master hard drive on primary and one master DVD/CDRW on secondary. -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
