Date: Wed, 28 Jan 2004 15:17:47 +0100 From: Wilko Bulte <wkb@freebie.xs4all.nl> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: freebsd-alpha@freebsd.org Subject: Re: Same problem, new year 2100A machine check Message-ID: <20040128141747.GA9813@freebie.xs4all.nl> In-Reply-To: <16407.48711.708178.207673@grasshopper.cs.duke.edu> References: <4011B6F6.5040306@theriver.com> <40143372.8090207@theriver.com> <16407.1903.816168.318651@grasshopper.cs.duke.edu> <4015BB97.70209@theriver.com> <16407.48711.708178.207673@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 28, 2004 at 08:51:03AM -0500, Andrew Gallatin wrote: > > Tom Ponsford writes: > > > > 1) Build a kernel with ddb and get a stack trace. > > > When the machine crashes and you land at the "db>" prompt, type 'tr' > > > > I think I did that once before for this list, I think it was a year or so ago. > > Here is the backtrace I posted: It was for then 5.0 current > > a smp and uniprocessor kernel did exactly the same thing. > > I seem to vaguely remember a thread like this fizzling out a long time > ago. I think the trap is happening at a slightly different place. > (well after eisab0 in the 5.0 trace). Wasn't that something todo with an extra bridgeboard or somesuch on the Cbus? I only have a faint recollection here.. > FWIW, having written the 2100 support, I think I'm free to say that > 2100 series is totally evil, and you'd be better off using it as a > boat anchor, a fish tank, or in some other non-computational capacity... Hi hi.. the things we regret having done in the past. -- Wilko Bulte wilko@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040128141747.GA9813>