In message Pine.BSF.4.21.0109302134440.95162-10@beppo Matthew Jacob writes:
: -current as of the last day or so- anyone else seen?
Do these happen with acpi disabled?
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
-current as of the last day or so- anyone else seen?
Sep 30 20:47:15 quarm ntpd[239]: kernel time discipline status change 2041
microuptime() went backwards (939.4410978 - 938.949317)
microuptime() went backwards (1382.4391199 - 1382.075447)
microuptime() went backwards (1382.4391190 -
-current as of the last day or so- anyone else seen?
Sep 30 20:47:15 quarm ntpd[239]: kernel time discipline status change 2041
microuptime() went backwards (939.4410978 - 938.949317)
Try turning off the ACPI timer:
debug.acpi.disable=timer
in loader.conf and see if it goes away. I'm
Cool. Yes. Will do. It also turns out that even with this being an SMP system
with IOAPIC that ACPI still shares an irq with isp0. How odd.
On Sun, 30 Sep 2001, Mike Smith wrote:
-current as of the last day or so- anyone else seen?
Sep 30 20:47:15 quarm ntpd[239]: kernel time
Cool. Yes. Will do. It also turns out that even with this being an SMP system
with IOAPIC that ACPI still shares an irq with isp0. How odd.
This is probably an artifact of the PCI interrupt swizzle; the ACPI
irq is typically an interrupt line out of the southbridge (where the power
