Date: Tue, 7 Mar 2000 10:25:55 +0100 From: Dave Boers <djb@relativity.student.utwente.nl> To: Vallo Kallaste <vallo@matti.ee> Cc: Arun Sharma <adsharma@sharmas.dhs.org>, freebsd-current@freebsd.org Subject: Re: current lockups Message-ID: <20000307102555.A29469@relativity.student.utwente.nl> In-Reply-To: <20000307084530.A27113@myhakas.matti.ee>; from vallo@matti.ee on Tue, Mar 07, 2000 at 08:45:30AM %2B0200 References: <20000304235010.B10778@sharmas.dhs.org> <20000306202718.A26973@relativity.student.utwente.nl> <20000307084530.A27113@myhakas.matti.ee>
next in thread | previous in thread | raw e-mail | index | archive | help
It is rumoured that Vallo Kallaste had the courage to say: > I had a lockup yesterday while stress-testing new SMP machine. Tyan > motherboard with Intel GX chipset, 256MB of memory, one 20GB IBM UDMA66 > disk, but running at UDMA33. All power management disabled completely in > the BIOS. I was doing massive parallel compiling of GENERIC kernels. > Let the machine doing this overnight and on the morning the console had > about 20 'microuptime() went backwards' messages, I was able to switch > vty's but not login, machine responded to pings, no disk activity. I'm > using ata driver and only one unusual kernel option HZ=1000. Your symptoms are not the same as mine. In my case the lockups are complete. No switching of vt's, no pings, nothing at all. I never saw any "microuptime() went backwards" messages either. But then again, I never had the machine lockup on the console; I was usually logged in over the network or working in X. Regards, Dave Boers. -- Dave Boers < djb @ relativity . student . utwente . nl > Don't let your schooling interfere with your education. (Mark Twain) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000307102555.A29469>