In message <[EMAIL PROTECTED]>, Bruce E
vans writes:
>> I remember this one too. I think the problem is that we fail to
>> service the RTC intr for some reason. This patch was only a
>> workaround, and received a verbal broadside from Bruce if I
>> remember right.
>>
>> Maybe it should be added under a sysctl until a better solution
>> is know.
>>
>> --- clock.c Sat Sep 18 22:41:40 1999
>> +++ clock.c.new Sun Sep 5 13:21:35 1999
>> @@ -203,4 +203,6 @@
>> clkintr(struct clockframe frame)
>> {
>> + while (rtcin(RTC_INTR) & RTCIR_PERIOD)
>> + statclock(&frame);
>> if (timecounter->tc_get_timecount == i8254_get_timecount) {
>> disable_intr();
>
>Use a watchdog timeout like you should for any device that may hang.
>Don't waste time running it every clock tick.
>
>ISTR that we thought that the bug might be caused by a bug in unwanted
>SMI interrupt handling.
If anybody can reproduce this reliably on a *BX chipset I have
code that will block SMI interrupts we can test with...
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
