Re: calcru / microuptime problem
I have had these problems ever since upgrading to -current about a month ago. The kernel very regularly spews out messages like: Mar 13 14:23:39 gemini /kernel: calcru: negative time of -2663631 usec for pid 568 (sshd2) or a message that "microuptime() went backwards'. I have noticed that these messages usually coincide with moderate to heavy disk IO. I do not have the dmesg or kernel config here with me right now, but I believe I can provide most of the usefull information. The system is an ASUS P2B-DS running ROM revision 1009. It has 2 Pentium II - 400Mhz CPUs, and is running with 'device apm flags 0x20' to get the stat-clock (this was needed in FreeBSD-3.x, I have not yet tried without it. I am also running vinum across 3 disks, one Ultra-2-wide SCSI, and 2 IDE (each on their own bus). Furthermore I am running xntpd to keep my clock in sync. Any suggestions? Remove the flags on the apm device and update to at least the 1011 BIOS. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: calcru / microuptime problem
On Mon, 13 Mar 2000, David E. Cross wrote: I have had these problems ever since upgrading to -current about a month ago. The kernel very regularly spews out messages like: Mar 13 14:23:39 gemini /kernel: calcru: negative time of -2663631 usec for pid 568 (sshd2) I know you've probably already tried this, but I'll say it just in case: try setting the kern.timecounter.method sysctl to 1 and see if that works around the problem. Kelly -- Kelly Yancey - [EMAIL PROTECTED] - Richmond, VA Analyst / E-business Development, Bell Industries http://www.bellind.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSDhttp://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: calcru / microuptime problem
In message [EMAIL PROTECTED], "David E. Cross" writes: I have had these problems ever since upgrading to -current about a month ago. The kernel very regularly spews out messages like: Mar 13 14:23:39 gemini /kernel: calcru: negative time of -2663631 usec for pid 568 (sshd2) Disable APM in your bios and remove apm from your config. -- 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 / microuptime problem
In message [EMAIL PROTECTED], "David E. Cross" writes: I have had these problems ever since upgrading to -current about a month ago. The kernel very regularly spews out messages like: Mar 13 14:23:39 gemini /kernel: calcru: negative time of -2663631 usec for pid 568 (sshd2) Disable APM in your bios and remove apm from your config. This isn't the fix for this problem, and especially not on this board. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: calcru / microuptime problem
On Mon, Mar 13, 2000 at 09:00:26PM +0100, Poul-Henning Kamp [EMAIL PROTECTED] wrote: In message [EMAIL PROTECTED], "David E. Cross" writes: I have had these problems ever since upgrading to -current about a month ago. The kernel very regularly spews out messages like: Mar 13 14:23:39 gemini /kernel: calcru: negative time of -2663631 usec for pid 568 (sshd2) Disable APM in your bios and remove apm from your config. The 'microuptime() went backwards' happened to me also lately, week or so ago. Tyan mobo with GX chipset, power management disabled completely in the BIOS, no apm in kernel. Two PIII-550, one 20GB IBM disk (ATA). Same symptoms as above, heavy disk I/O, I was stress-testing the machine, except the machine hung for some unknown reason: I was able to switch vty's and ping the machine but not login, no disk I/O. I'm waiting for two 36GB IBM SCSI disks, which should arrive soon, then the next round without ATA is what I'm planning. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: calcru / microuptime problem
On 14-Mar-00 Vallo Kallaste wrote: in the BIOS, no apm in kernel. Two PIII-550, one 20GB IBM disk (ATA). Same symptoms as above, heavy disk I/O, I was stress-testing the machine, except the machine hung for some unknown reason: I was able to switch vty's and ping the machine but not login, no disk I/O. I'm waiting for two 36GB IBM SCSI disks, which should arrive soon, then the next round without ATA is what I'm planning. Do you have the latest BIOS rev? --- 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 / microuptime problem
On Tue, Mar 14, 2000 at 04:40:43PM +1030, Daniel O'Connor [EMAIL PROTECTED] wrote: On 14-Mar-00 Vallo Kallaste wrote: in the BIOS, no apm in kernel. Two PIII-550, one 20GB IBM disk (ATA). Same symptoms as above, heavy disk I/O, I was stress-testing the machine, except the machine hung for some unknown reason: I was able to switch vty's and ping the machine but not login, no disk I/O. I'm waiting for two 36GB IBM SCSI disks, which should arrive soon, then the next round without ATA is what I'm planning. Do you have the latest BIOS rev? You mean for Tyan mobo? No, it's version 1.16b nongraphical AMIBIOS which come with board. I'm having exactly same board but with SCSI only configuration for my workstation which works without any problem for half a year now. Also SMP, two PIII-500. When the new disks arrive, well, I can try the new BIOS also. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: calcru / microuptime problem
On 14-Mar-00 Vallo Kallaste wrote: You mean for Tyan mobo? No, it's version 1.16b nongraphical AMIBIOS which come with board. I'm having exactly same board but with SCSI only configuration for my workstation which works without any problem for half a year now. Also SMP, two PIII-500. When the new disks arrive, well, I can try the new BIOS also. Worth a shot I suppose.. Other people seem to recommend it anyway 8-) --- 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
