From owner-freebsd-alpha@FreeBSD.ORG Tue Jan 27 17:16:04 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 75CE216A4CF for ; Tue, 27 Jan 2004 17:16:04 -0800 (PST) Received: from smtp1.sea.theriver.com (smtp1.sea.theriver.com [216.39.128.16]) by mx1.FreeBSD.org (Postfix) with SMTP id 1AA2043D60 for ; Tue, 27 Jan 2004 17:15:56 -0800 (PST) (envelope-from tponsford@theriver.com) Received: (qmail 18704 invoked from network); 28 Jan 2004 01:15:52 -0000 Received: from az-ben-pm3-2-30.ppp.theriver.com (HELO theriver.com) (tponsford@206.25.50.30) by smtp1.sea.theriver.com with SMTP; 28 Jan 2004 01:15:52 -0000 Message-ID: <4015BB97.70209@theriver.com> Date: Mon, 26 Jan 2004 18:15:03 -0700 From: Tom Ponsford User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5a) Gecko/20030808 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andrew Gallatin References: <4011B6F6.5040306@theriver.com> <40143372.8090207@theriver.com> <16407.1903.816168.318651@grasshopper.cs.duke.edu> In-Reply-To: <16407.1903.816168.318651@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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 01:16:04 -0000 Hi All, Andrew Gallatin wrote: > > It DOES NOT boot: > > > > FreeBSD 4.xx MP kernel -machine check as it probes PCI/EISA bus > > Interesting. FreeBSD 4 never supported MP on alpha. Maybe I got it confused with either the 5.x sources, or maybe even the Netbsd source, but I could have sworn there was a options SMP in the config file for 4.x. Either way it didn't boot smp > > > > Here are some things to do/try. > > 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 will build a new 5.2 debug kernel though: ####################################### FreeBSD/alpha SRM disk boot, Revision 1.2 (root@tomzbox10.tomznet.lan, Tue Oct 29 02:44:25 MST 2002) Memory 262144 k Loading /boot/defaults/loader.conf /boot/kernel/kernel data=0x44bc70+0x672c0 syms=[0x8+0x5ee90+0x8+0x48e16] Hit {Enter} to boot immediatly, or any other key for command prompt. Booting [/boot/kernel/kernel]... Entering /boot/kernel/kernel at 0xfffffc000033e580... sio1: gdb debugging port Copyright (c) 1992-2002 The FreeBSD Project Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992,1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Wed Nov 6 11:12:40 MST 2002 root@tomzbox.10.tomznet.lan:/usr/obj/usr/src/sys/TOMZBOX10 Preloaded elf kernel "/boot/kernel/kernel" at 0xfffffc000085e000. DEC AlphaServer 2100A 4/275, 274MHZ 8192 byte page size, 4 processors. CPU: EV45 (21064A) major=6 minor=2 OSF PAL rev: 0x4000c0002012d real memory = 266264576 (260024K bytes) avail memory = 250675200 (244800K bytes) Initializing GEOMetry subsystem t20: using interupt type 1 on pci bus 0 t20: pci0 on pcib0 eisab0: at device 2.0 on pci0 isa0: on eisab0 pcib1: at device 3.0 on pci0 pci2: on pcib1 unexpected machine check: mces = 0x1 vector = 0x660 param = 0xfffffc0000006000 pc = 0xfffffc000064b888 ra = 0xfffffc000064b83c curproc= 0xfffffc000075fd50 pid = 0, comm = swapper stopped at t2_pcib_read_config=0x3e8: or zero,s3,v0 db> trace t2_pcib_read_config() at t2_pcib_read_config+0x3e8 pcib_read_config() at pcib_read_config+0xcc pci_read_device() at pci_read_device+0xb4 pci_add_children() at pci_add_children+0xf8 pci_attach() at pci_attach+0xd8 device_probe_and_attach() at device_probe_and_attach+0xc8 bus_generic_attach() at bus_generic_attach+0x28 pcib_attach() at pcib_attach+0x68 device_probe_and_attach() at _device_probe_and_attach+0xc8 bus_generic_attach() at bus_generic_attach+0x28 pci_attach() at pci_attach+0xe4 device_probe_and_attach() at device_probe_and_attach+0xc8 bus_generic_attach() at bus_generic_attach+0x28 device_probe_and_attach() at device_probe_and_attaxh+0xc8 bus_generic_attach() at bus_generic-attach+0x28 t2_attach() at t2_attach+0x6c device_probe_and-attach() at device_probe_and_attach+0xc8 root_bus_configure() at root_bus_configure+0x38 configure() at configure+0x40 mi_startup() at mi_startup+0x144 locorestart() at locorestart+0x64 --- root of call graph --- ############################################################## 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.. > > This might not be incredibly helpful because machine checks > are not synchronous, but it may narrow things down a little bit. > 2) Disable all but CPU0 from the SRM console. There's a bitmask > you can set from SRM (I don't remember off the top of my head what it > is, but its probably set to 0xfff now). I'll try it and if that's not the right bitmap, I do have the documentation for this beast. > > Drew > Thanks for all the help!! Tom Ponsford