From owner-freebsd-alpha@FreeBSD.ORG Wed Jan 28 05:51:12 2004 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 15C4516A4CE for ; Wed, 28 Jan 2004 05:51:12 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3BD043D31 for ; Wed, 28 Jan 2004 05:51:10 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id i0SDp95P020986 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 28 Jan 2004 08:51:10 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id i0SDp3Wh013043; Wed, 28 Jan 2004 08:51:03 -0500 (EST) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16407.48711.708178.207673@grasshopper.cs.duke.edu> Date: Wed, 28 Jan 2004 08:51:03 -0500 (EST) To: Tom Ponsford In-Reply-To: <4015BB97.70209@theriver.com> References: <4011B6F6.5040306@theriver.com> <40143372.8090207@theriver.com> <16407.1903.816168.318651@grasshopper.cs.duke.edu> <4015BB97.70209@theriver.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: freebsd-alpha@freebsd.org Subject: Re: Same problem, new year 2100A machine check X-BeenThere: freebsd-alpha@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Alpha List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jan 2004 13:51:12 -0000 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). > I will build a new 5.2 debug kernel though: That would be best. > > I'll have to dig up an alpha that I can spare thats not running on my VMS lan, > so It might be a week or two before I can get a new 5.2 backtrace.. I'm in no rush. <..> > Thanks for all the help!! > No problem.. But I haven't been much help at all. 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... Drew