calcru: negative time (Interrupt Storm on cpu0: timer)
Hello, After reboot yesterday, my system suddenly started to flood syslog with following message: calcru: runtime went backwards from 1966191374 usec to 1966189453 usec for pid 29988 (screen) It's not only screen, i saw sh and su also, but in the last hour only screen. A vmstat -i and the same 5 seconds later: interrupt total rate irq1: atkbd0 1 0 irq13: npx01 0 irq14: ata0 410366 5 irq17: em0 20882069263 cpu0: timer158483081 2000 Total 179775518 2268 interrupt total rate irq1: atkbd0 1 0 irq13: npx01 0 irq14: ata0 410430 5 irq17: em0 20885602263 cpu0: timer158505514 2000 Total 179801548 2268 Is this an interrupt storm? I know that there is a FAQ entry about the negative time issue, but it seems this is more a bad workaround I guess. The system was running without problems for 3 months or so and as I said the problem suddenly appeared yesterday. Any hints on whats wrong here? Thanks in advance, Frank ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: calcru: negative time (Interrupt Storm on cpu0: timer)
Sorry, i forgot to mention: kern.osreldate: 600100 Frank ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: calcru: negative time (Interrupt Storm on cpu0: timer)
Only time I've ever seen this problem is running on a VMWARE virtual server. Is that the case here? If so, try: sysctl kern.timecounter.hardware=TSC That did the trick for me. Frank Steinborn wrote: Hello, After reboot yesterday, my system suddenly started to flood syslog with following message: calcru: runtime went backwards from 1966191374 usec to 1966189453 usec for pid 29988 (screen) It's not only screen, i saw sh and su also, but in the last hour only screen. A vmstat -i and the same 5 seconds later: interrupt total rate irq1: atkbd0 1 0 irq13: npx01 0 irq14: ata0 410366 5 irq17: em0 20882069263 cpu0: timer158483081 2000 Total 179775518 2268 interrupt total rate irq1: atkbd0 1 0 irq13: npx01 0 irq14: ata0 410430 5 irq17: em0 20885602263 cpu0: timer158505514 2000 Total 179801548 2268 Is this an interrupt storm? I know that there is a FAQ entry about the negative time issue, but it seems this is more a bad workaround I guess. The system was running without problems for 3 months or so and as I said the problem suddenly appeared yesterday. Any hints on whats wrong here? Thanks in advance, Frank ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: calcru: negative time (Interrupt Storm on cpu0: timer)
J. Buck Caldwell wrote: Only time I've ever seen this problem is running on a VMWARE virtual server. This is not a VMware system. kern.timecounter.hardware is set to ACPI-fast. Frank ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: calcru: negative time (Interrupt Storm on cpu0: timer)
On Tue, Feb 14, 2006 at 12:09:34AM +0100 I heard the voice of Frank Steinborn, and lo! it spake thus: cpu0: timer158483081 2000 That's not a storm, that's normal. -- Matthew Fuller (MF4839) | [EMAIL PROTECTED] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
