Date: Sat, 14 Jul 2001 09:14:01 +0930 From: Greg Lehey <grog@FreeBSD.org> To: Joey Garcia <bear@buug.homeip.net>, Irwan Hadi <irwanhadi@phxby.com> Cc: questions@freebsd.org, FreeBSD-Questions <freebsd-questions@freebsd.org> Subject: Re: What are these strange microuptime messages? Message-ID: <20010714091400.E99931@wantadilla.lemis.com> In-Reply-To: <20010712203442.F27066-100000@localhost>; from bear@buug.homeip.net on Thu, Jul 12, 2001 at 08:36:28PM -0700 References: <20010712223515.B3783@phxby.com> <20010712215026.M77873-100000@localhost> <20010712203442.F27066-100000@localhost> <01b701c10b4e$9c3d4420$3200a8c0@Home> <20010712222011.A3367@phxby.com> <20010713121013.X45037@wantadilla.lemis.com> <20010712203442.F27066-100000@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, 12 July 2001 at 20:36:28 -0700, Joey Garcia wrote: > > On Fri, 13 Jul 2001, Greg Lehey wrote: > >>> Jul 10 20:03:02 buug /kernel: microuptime() went backwards (1458654.943789 -> 1458654.-694440653) >> >> Something has gone wrong. >> >> Greg > > Any idea what it might be? Well, yes, but it would help to know what you're running. I get really frustrated with these "something has gone wrong, what's causing it?" messages. On Thursday, 12 July 2001 at 22:20:11 -0600, Irwan Hadi wrote: > On Thu, Jul 12, 2001 at 09:54:50PM -0600, Ryan Masse wrote: > >> i don't have a solution nor a reason why, but that happens all the time on >> one of my boxes when its running setiathome. > > I also got the same problem, on a freeBSD 4.3 release, on an AMD Athlon 1.2 > Ghz, 640 M Memory (512 MB PC 133 CAS 3 Mushkin with Nanya Chips, and 128 M PC > 133 CAS 2 Rev 2 Mushkin), and 40 GB Maxtor 7200 RPM. The motherboard is the > newest Asus Ali Magik 1. > On that computer I'm doing nothing, and the computer is still in burn test > (although its already 20 days). I just turn on the computer after I installed > freeBSD there, and leave it alone. > Is it because memory problem, or because AMD, or what? Now this is the kind of message I like. Read on. On Thursday, 12 July 2001 at 21:52:03 -0700, Joey Garcia wrote: > On Thu, 12 Jul 2001, Irwan Hadi wrote: >> On Thu, Jul 12, 2001 at 10:29:10PM -0600, Ryan Masse wrote: >> >>> i am too running 4.3-RELEASE on an older AMD K62-400 system. >>> setiathome is a console based program.. i don;t have X installed on this box >> >> Problem can be from AMD based processor ? >> Does anyone using AMD based processor has the same problem also ? My take on this issue is that it's a bug. We haven't investigated it enough, but it seems to happen mainly (but not always) with AMD processors. I suspect that it's the motherboard or BIOS, not the processor, which tickles the bug. In early versions of the SMPng support, it occurred on all processors, which makes me think it's a bug. In all cases I've seen (with the exception of the early SMPng stuff), you can fix it by disabling APM. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010714091400.E99931>