Date: Tue, 7 Mar 2000 08:45:30 +0200 From: Vallo Kallaste <vallo@matti.ee> To: Dave Boers <djb@relativity.student.utwente.nl> Cc: Arun Sharma <adsharma@sharmas.dhs.org>, freebsd-current@freebsd.org Subject: Re: current lockups Message-ID: <20000307084530.A27113@myhakas.matti.ee> In-Reply-To: <20000306202718.A26973@relativity.student.utwente.nl>; from Dave Boers on Mon, Mar 06, 2000 at 08:27:18PM %2B0100 References: <20000304235010.B10778@sharmas.dhs.org> <20000306202718.A26973@relativity.student.utwente.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Mar 06, 2000 at 08:27:18PM +0100, Dave Boers <djb@relativity.student.utwente.nl> wrote: > I'm interested in the fix, of course :-) But where to start looking? I've > had three lockups so far (none before january 2000) but I didn't find > anything that reliably triggered it. 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. -- Vallo Kallaste vallo@matti.ee 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?20000307084530.A27113>