Re: calcru() warnings...
Poul-Henning Kamp wrote: I still hear reports of sporadic calcru() warnings. If any of you see these, could you try to see if they correlate to the uptime of the machine in question ? Should they start or stop when a machine has been running a while? I see neither (negative calcru notices in dmesg start at boot time and didn't stop until the box had a kernel panic last Saturday evening, after about two weeks uptime). FWIW, the messages started occurring when I switched from a pre-signal to post-signal change kernel and world. Is this SMP ? Yes. FreeBSD buty.wanadoo.nl 4.0-CURRENT FreeBSD 4.0-CURRENT #25: Thu Nov 11 02:41:49 CET 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/BUTY i386 It's an ASUS P2B-DS, BIOS rev. 1010, which I also upgraded (from 1009 - broken statclock!) in that timeframe... -- Niels. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: calcru() warnings...
On Wed, 24 Nov 1999, Poul-Henning Kamp wrote: I still hear reports of sporadic calcru() warnings. If any of you see these, could you try to see if they correlate to the uptime of the machine in question ? Since I replaced a September 15 -current with October 14 -current, I get lots of these within 24 or 48 hours of booting. Setting kern.timecounter.method to 1 does stop them. SMP, two PII-400's. Annelise To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
calcru() warnings...
I still hear reports of sporadic calcru() warnings. If any of you see these, could you try to see if they correlate to the uptime of the machine in question ? -- 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
Re: calcru() warnings...
Hi, At 8:00 pm +0100 24/11/99, Poul-Henning Kamp wrote: I still hear reports of sporadic calcru() warnings. If any of you see these, could you try to see if they correlate to the uptime of the machine in question ? Nov 23 00:03:35 bludnok /kernel: [boot] Nov 24 09:02:06 bludnok /kernel: calcru: negative time of -4660895 usec for pid 76002 (cc) Ie up just under 9 hours. Building world at the time. This box is running SMP, full details on request. -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: calcru() warnings...
I got a few calcru() warnings on a dual Pentium-III Xeon system. It had been up for around 9 or 10 days or so; I've since rebooted it. Specific configuration available if you need it. louie To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: calcru() warnings...
Poul-Henning Kamp wrote: I still hear reports of sporadic calcru() warnings. If any of you see these, could you try to see if they correlate to the uptime of the machine in question ? Should they start or stop when a machine has been running a while? I see neither (negative calcru notices in dmesg start at boot time and didn't stop until the box had a kernel panic last Saturday evening, after about two weeks uptime). FWIW, the messages started occurring when I switched from a pre-signal to post-signal change kernel and world. -- Niels. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: calcru() warnings...
On 24-Nov-99 Poul-Henning Kamp wrote: I still hear reports of sporadic calcru() warnings. If any of you see these, could you try to see if they correlate to the uptime of the machine in question ? I have had them for Seti@Home occasionally. The system hadn't been up for more than 24 hours. Its a dual PII-350. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: calcru() warnings...
On Thu, Nov 25, 1999 at 10:38:56AM +1030, Daniel O'Connor [EMAIL PROTECTED] wrote: On 24-Nov-99 Poul-Henning Kamp wrote: I still hear reports of sporadic calcru() warnings. If any of you see these, could you try to see if they correlate to the uptime of the machine in question ? I have had them for Seti@Home occasionally. The system hadn't been up for more than 24 hours. Its a dual PII-350. Same here, running setiathome means that I can find such processes after a day or so: 4 ?? DL -2341043:-35.26 (bufdaemon) The ``calcru'' messages aren't strictly necessary, such things happen without them also. Dual PIII-500, two seti processes. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: calcru() warnings...
Is this SMP ? In message [EMAIL PROTECTED], N writes: Poul-Henning Kamp wrote: I still hear reports of sporadic calcru() warnings. If any of you see these, could you try to see if they correlate to the uptime of the machine in question ? Should they start or stop when a machine has been running a while? I see neither (negative calcru notices in dmesg start at boot time and didn't stop until the box had a kernel panic last Saturday evening, after about two weeks uptime). FWIW, the messages started occurring when I switched from a pre-signal to post-signal change kernel and world. -- Niels. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- 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
