OK I completed a new non-SMP kernel (the GENERIC kernel with SMP commented out)
built using 4.6.2 and ran installkernel KERNCONF=TOMZBOX10. The newer bootblocks
and loader having been already installed.
The non-smp 5.0-CURRENT kernel chokes at the exact same point as before:
FreeBSD/alpha SRM disk boot, Revision 1.2
([EMAIL PROTECTED], 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
[EMAIL PROTECTED]:/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: <T2 Core Logic chipset>
pci0 <PCI bus> on pcib0
eisab0: <PCI-EISA bridge> at device 2.0 on pci0
isa0: <ISA bus> on eisab0
pcib1: <PCI-PCI bridge> at device 3.0 on pci0
pci2: <PCI bus> 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 <zero=0k
0,s3=0xffffffffffffffff,v0=0x7>
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 ---
This is almost identical to the SMP kernel
Anything I can do to help just ask!!
Cheers
Tom
Andrew Gallatin wrote:
Tom Ponsford writes:
> Hi All,
> > I'm getting a machine check on my new-toy: an Alphaserver 2100A 4/275 RM.
> > It boots and runs 4.6.2 fine with a single cpu. But after I supped the > current 5.0 sources from
> 10/29/2002 17:39 and did a buildworld and a Generic buildkernel, (plus > all the
> other steps in UPDATING with the exception of installing world) But after an
> installkernel, I get a machine check, just after the kernel loads and boots.
>
Can you build a non-SMP kernel and see if that boots please?
Nobody has ever run an SMP kernel on a 2100A, AFAIK. The 2100A has
problems with multiple machine checks being reported for each machine
check triggered. I wonder if you're getting a machine check for each
CPU. Hmmm..
Drew
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
