Jeff Blank
2008-Mar-01 20:07 UTC
7.0-STABLE amd64 kernel trap during boot-time device probe
Hello,
I posted this around 3 months ago and never received a response. the
problem still occurs with 7.0-STABLE (csup on 20080301). I possibly
incorrectly referred to it as a panic last time, when the problem was
really a trap.
The only steps I've really taken since I posted this originally were
to upgrade world/kernel due to patches a couple times and to perform
an "upgrade" install from the 7.0-RELEASE CD, none of which had any
effect.
Can anyone please help me out with this?
thank you,
Jeff
----- Forwarded message from Jeff Blank <jb000002@mr-happy.com> -----
Date: Fri, 7 Dec 2007 00:05:57 -0500
From: Jeff Blank <jb000002@mr-happy.com>
To: freebsd-stable@freebsd.org
Subject: 7.0-BETA4 amd64 panic during boot-time device probe
I've upgraded my AMD64 box from RELENG_6 (csup on Nov. 30) to RELENG_7
(csup around 01:30 UTC Dec. 7) and am getting a kernel panic when I
try to boot with seemingly any one module specified in
/boot/loader.conf (XXX_load=YES). It seems to occur near the end of
device probing, just before it detects the disks.
This panic does not happen if no modules are specified to be loaded in
/boot/loader.conf. There is also no panic if I boot without
loader.conf modules but then load the modules with kldload.
This problem was originally happening when I was attempting to go from
6-STABLE to 7.0-BETA4, and rebuilding 7.0B4 under 7.0B4 yields the
same result.
Here is console output from the panic and partial dmesg output from
the successful boot (similar up to a point, some context included). I
couldn't get my serial port to accept input at the debugger prompt,
and my keyboard (USB) can't even "Press a key on the console to
reboot" when I have a non-ddb/kdb/etc kernel, so I couldn't do
anything once I got into the debugger. Hopefully what's below has
some useful information--if not, I'll be happy to try to get it.
On the subject of the kernel debugger, I used GENERIC plus
options DDB
options DDB_NUMSYM
options GDB
options KDB
options KDB_TRACE
and set hint.sio.0.flags="0x80" in /boot/device.hints. What am I
missing to allow serial input when the debugger starts?
thanks for any help,
Jeff
=== panic ==GDB: debug ports: sio
GDB: current port: sio
KDB: debugger backends: ddb gdb
KDB: current backend: ddb
Copyright (c) 1992-2007 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 is a registered trademark of The FreeBSD Foundation.
FreeBSD 7.0-BETA4 #0: Thu Dec 6 23:35:34 EST 2007
root@crow.mr-happy.com:/usr/obj/usr/src/sys/GENERIC_DBG
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ (2211.34-MHz K8-class CPU)
Origin = "AuthenticAMD" Id = 0x20f32 Stepping = 2
Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
Features2=0x1<SSE3>
AMD Features=0xe2500800<SYSCALL,NX,MMX+,FFXSR,LM,3DNow!+,3DNow!>
AMD Features2=0x3<LAHF,CMP>
Cores per package: 2
usable memory = 1060421632 (1011 MB)
avail memory = 1021755392 (974 MB)
ACPI APIC Table: <Nvidia AWRDACPI>
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 1
ioapic0: Changing APIC ID to 2
ioapic0 <Version 1.1> irqs 0-23 on motherboard
kbd1 at kbdmux0
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
acpi0: <Nvidia AWRDACPI> on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
acpi0: reservation of 0, a0000 (3) failed
acpi0: reservation of 100000, 3fef0000 (3) failed
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0
cpu0: <ACPI CPU> on acpi0
powernow0: <Cool`n'Quiet K8> on cpu0
device_attach: powernow0 attach returned 6
cpu1: <ACPI CPU> on acpi0
powernow1: <Cool`n'Quiet K8> on cpu1
device_attach: powernow1 attach returned 6
acpi_button0: <Power Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pci0: <memory> at device 0.0 (no driver attached)
isab0: <PCI-ISA bridge> at device 1.0 on pci0
isa0: <ISA bus> on isab0
pci0: <serial bus, SMBus> at device 1.1 (no driver attached)
ohci0: <OHCI (generic) USB controller> mem 0xdc004000-0xdc004fff irq 21 at
device 2.0 on pci0
ohci0: [GIANT-LOCKED]
ohci0: [ITHREAD]
usb0: OHCI version 1.0, legacy support
usb0: SMM does not respond, resetting
usb0: <OHCI (generic) USB controller> on ohci0
usb0: USB revision 1.0
uhub0: <nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
uhub0: 10 ports with 10 removable, self powered
ehci0: <NVIDIA nForce4 USB 2.0 controller> mem 0xfeb00000-0xfeb000ff irq
22 at device 2.1 on pci0
ehci0: [GIANT-LOCKED]
ehci0: [ITHREAD]
usb1: EHCI version 1.0
usb1: companion controller, 4 ports each: usb0
usb1: <NVIDIA nForce4 USB 2.0 controller> on ehci0
usb1: USB revision 2.0
uhub1: <nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb1
uhub1: 10 ports with 10 removable, self powered
pcm0: <nVidia nForce4> port 0xdc00-0xdcff,0xe000-0xe0ff mem
0xdc003000-0xdc003fff irq 23 at device 4.0 on pci0
pcm0: [ITHREAD]
pcm0: <Avance Logic ALC850 AC97 Codec>
atapci0: <nVidia nForce CK804 UDMA133 controller> port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 6.0 on pci0
ata0: <ATA channel 0> on atapci0
ata0: [ITHREAD]
ata1: <ATA channel 1> on atapci0
ata1: [ITHREAD]
atapci1: <nVidia nForce CK804 SATA300 controller> port
0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xd800-0xd80f mem
0xdc002000-0xdc002fff irq 21 at device 7.0 on pci0
atapci1: [ITHREAD]
ata2: <ATA channel 0> on atapci1
ata2: [ITHREAD]
ata3: <ATA channel 1> on atapci1
ata3: [ITHREAD]
atapci2: <nVidia nForce CK804 SATA300 controller> port
0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xc400-0xc40f mem
0xdc001000-0xdc001fff irq 22 at device 8.0 on pci0
atapci2: [ITHREAD]
ata4: <ATA channel 0> on atapci2
ata4: [ITHREAD]
ata5: <ATA channel 1> on atapci2
ata5: [ITHREAD]
pcib1: <ACPI PCI-PCI bridge> at device 9.0 on pci0
pci5: <ACPI PCI bus> on pcib1
sio0: configured irq 18 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: configured irq 18 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: <3COM PCI FaxModem> port 0xa000-0xa007 irq 18 at device 8.0 on pci5
sio0: moving to sio4
sio4: type 16550A
sio4: [FILTER]
fwohci0: <Texas Instruments TSB43AB22/A> mem
0xdb008000-0xdb0087ff,0xdb004000-0xdb007fff irq 16 at device 11.0 on pci5
fwohci0: [FILTER]
fwohci0: OHCI version 1.10 (ROM=1)
fwohci0: No. of Isochronous channels is 4.
fwohci0: EUI64 00:11:d8:00:00:72:dc:3e
fwohci0: Phy 1394a available S400, 2 ports.
fwohci0: Link S400, max_rec 2048 bytes.
firewire0: <IEEE1394(FireWire) bus> on fwohci0
dcons_crom0: <dcons configuration ROM> on firewire0
dcons_crom0: bus_addr 0x9fe740
fwe0: <Ethernet over FireWire> on firewire0
if_fwe0: Fake Ethernet address: 02:11:d8:72:dc:3e
fwe0: Ethernet address: 02:11:d8:72:dc:3e
fwip0: <IP over FireWire> on firewire0
fwip0: Firewire address: 00:11:d8:00:00:72:dc:3e @ 0xfffe00000000, S400, maxrec
2048
sbp0: <SBP-2/SCSI over FireWire> on firewire0
fwohci0: Initiate bus reset
fwohci0: BUS reset
fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode
skc0: <Marvell Gigabit Ethernet> port 0xa400-0xa4ff mem
0xdb000000-0xdb003fff irq 17 at device 12.0 on pci5
skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9)
sk0: <Marvell Semiconductor, Inc. Yukon> on skc0
sk0: Ethernet address: 00:15:f2:1e:44:77
miibus0: <MII bus> on sk0
e1000phy0: <Marvell 88E1011 Gigabit PHY> PHY 0 on miibus0
e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto
skc0: [ITHREAD]
nfe0: <NVIDIA nForce4 CK804 MCP9 Networking Adapter> port 0xb000-0xb007
mem 0xdc000000-0xdc000fff irq 23 at device 10.0 on pci0
miibus1: <MII bus> on nfe0
e1000phy1: <Marvell 88E1111 Gigabit PHY> PHY 9 on miibus1
e1000phy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto
nfe0: Ethernet address: 00:15:f2:1e:31:0c
nfe0: [FILTER]
pcib2: <ACPI PCI-PCI bridge> at device 11.0 on pci0
pci4: <ACPI PCI bus> on pcib2
pcib3: <ACPI PCI-PCI bridge> at device 12.0 on pci0
pci3: <ACPI PCI bus> on pcib3
pcib4: <ACPI PCI-PCI bridge> at device 13.0 on pci0
pci2: <ACPI PCI bus> on pcib4
pcib5: <ACPI PCI-PCI bridge> at device 14.0 on pci0
pci1: <ACPI PCI bus> on pcib5
vgapci0: <VGA-compatible display> port 0x9000-0x90ff mem
0xd0000000-0xd7ffffff,0xd9000000-0xd900ffff irq 18 at device 0.0 on pci1
vgapci1: <VGA-compatible display> mem 0xd9010000-0xd901ffff at device 0.1
on pci1
acpi_tz0: <Thermal Zone> on acpi0
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
can't re-use a leaf (%desc)!
can't re-use a leaf (%driver)!
can't re-use a leaf (%location)!
can't re-use a leaf (%pnpinfo)!
can't re-use a leaf (%parent)!
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x90 on
acpi0
sio0: type 16550A, console
sio0: [FILTER]
ppc0: <Parallel port> port 0x378-0x37f,0x778-0x77b irq 7 drq 3 on acpi0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/16 bytes threshold
ppbus0: <Parallel port bus> on ppc0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
plip0: <PLIP network interface> on ppbus0
ppc0: [GIANT-LOCKED]
ppc0: [ITHREAD]
orm0: <ISA Option ROM> at iomem 0xd0000-0xd3fff on isa0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
ums0: <Contour Design Contour Perfit Mouse, class 0/0, rev 1.10/0.01, addr
2> on uhub0
ums0: 5 buttons and Z dir.
ukbd0: <vendor 0x0430 product 0x0005, class 0/0, rev 1.00/1.02, addr 3> on
uhub0
kbd2 at ukbd0
Timecounters tick evfirewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me)
firewire0: bus manager 0 (me)
ery 1.000 msec
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x258
fault code = supervisor read data, page not present
instruction pointer = 0x8:0xffffffff8047aa7e
stack pointer = 0x10:0xffffffffa0677b40
frame pointer = 0x10:0xffffffffa0677b60
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 23 (irq21: ohci0+)
[thread pid 23 tid 100029 ]
Stopped at 0xffffffff8047aa7e = _mtx_lock_sleep+0x4e: movl
0x258(%rcx),%esi
db>
=== end panic ==
=== no panic ==[...]
ums0: <Contour Design Contour Perfit Mouse, class 0/0, rev 1.10/0.01, addr
2> on uhub0
ums0: 5 buttons and Z dir.
ukbd0: <vendor 0x0430 product 0x0005, class 0/0, rev 1.00/1.02, addr 3> on
uhub0
kbd2 at ukbd0
Timecounters tick every 1.000 msec
firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me)
firewire0: bus manager 0 (me)
acd0: DMA limited to UDMA33, device found non-ATA66 cable
acd0: DVDR <LITE-ON DVDRW SHW-160P6S/PS08> at ata0-master UDMA33
ad4: 238475MB <HDT722525DLA380 V44OA9BA> at ata2-master SATA300
ad8: 157066MB <HDT722516DLA380 V43OA91A> at ata4-master SATA300
ad10: 157066MB <HDT722516DLA380 V43OA91A> at ata5-master SATA300
ar0: 314133MB <nVidia MediaShield RAID0 (stripe 64 KB)> status: READY
ar0: disk0 READY using ad8 at ata4-master
ar0: disk1 READY using ad10 at ata5-master
SMP: AP CPU #1 Launched!
Trying to mount root from ufs:/dev/ad4s1a
[continue successful boot]
=== end no panic ==
----- End forwarded message -----
Joe Koberg
2008-Mar-01 21:52 UTC
7.0-STABLE amd64 kernel trap during boot-time device probe
Jeff Blank wrote:> Hello, > > I posted this around 3 months ago and never received a response. the > problem still occurs with 7.0-STABLE (csup on 20080301). I possibly > incorrectly referred to it as a panic last time, when the problem was > really a trap. > >I also receive "Fatal trap 12: page fault while in kernel mode" while trying to boot a HP Proliant DL580G3 from the 7.0-RELEASE amd64 disc1 CD. I can successfully boot with the verbose boot option from the boot CD, and I installed the system and got it all setup for ZFS root. At long as I booted verbose it worked. But now I have recompiled the kernel to include SCHED_ULE and a few options and I cannot avoid the "Fatal trap 12" It is annoying to troubleshoot on this machine because the BIOS takes 5 minutes finally get around to booting the OS after a reboot. But it has an iLO management controller that I might be able to arrange access to for anyone who has the skill to find/fix the issue. Joe Koberg joe at osoft dot us> Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0x258 > fault code = supervisor read data, page not present > instruction pointer = 0x8:0xffffffff8047aa7e > stack pointer = 0x10:0xffffffffa0677b40 > frame pointer = 0x10:0xffffffffa0677b60 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 23 (irq21: ohci0+) > [thread pid 23 tid 100029 ] > Stopped at 0xffffffff8047aa7e = _mtx_lock_sleep+0x4e: movl 0x258(%rcx),%esi > db> > === end panic ==> > === no panic ==> [...] > ums0: <Contour Design Contour Perfit Mouse, class 0/0, rev 1.10/0.01, addr 2> on uhub0 > ums0: 5 buttons and Z dir. > ukbd0: <vendor 0x0430 product 0x0005, class 0/0, rev 1.00/1.02, addr 3> on uhub0 > kbd2 at ukbd0 > Timecounters tick every 1.000 msec > firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) > firewire0: bus manager 0 (me) > acd0: DMA limited to UDMA33, device found non-ATA66 cable > acd0: DVDR <LITE-ON DVDRW SHW-160P6S/PS08> at ata0-master UDMA33 > ad4: 238475MB <HDT722525DLA380 V44OA9BA> at ata2-master SATA300 > ad8: 157066MB <HDT722516DLA380 V43OA91A> at ata4-master SATA300 > ad10: 157066MB <HDT722516DLA380 V43OA91A> at ata5-master SATA300 > ar0: 314133MB <nVidia MediaShield RAID0 (stripe 64 KB)> status: READY > ar0: disk0 READY using ad8 at ata4-master > ar0: disk1 READY using ad10 at ata5-master > SMP: AP CPU #1 Launched! > Trying to mount root from ufs:/dev/ad4s1a > [continue successful boot] > === end no panic ==> > ----- End forwarded message ----- > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > >
Pete French
2008-Mar-01 22:00 UTC
7.0-STABLE amd64 kernel trap during boot-time device probe
> I also receive "Fatal trap 12: page fault while in kernel mode" while > trying to boot a HP Proliant DL580G3 from the 7.0-RELEASE amd64 disc1 CD.Does it boot with ACPI disabled ? I have an HP workstation which did the same, and got a patch for it in the end, but thius might be an utterly unrelated problem (just the fact it is an HP which is makin g me wonder). -pete.
Peter Jeremy
2008-Mar-01 22:56 UTC
7.0-STABLE amd64 kernel trap during boot-time device probe
On Sat, Mar 01, 2008 at 02:44:04PM -0500, Jeff Blank wrote:>I posted this around 3 months ago and never received a response. the >problem still occurs with 7.0-STABLE (csup on 20080301). I possibly >incorrectly referred to it as a panic last time, when the problem was >really a trap.A trap triggering a panic is still a panic.>I've upgraded my AMD64 box from RELENG_6 (csup on Nov. 30) to RELENG_7 >(csup around 01:30 UTC Dec. 7) and am getting a kernel panic when I >try to boot with seemingly any one module specified in >/boot/loader.conf (XXX_load=YES). It seems to occur near the end of >device probing, just before it detects the disks.This is likely to be when the loaded modules get probed.>Here is console output from the panic and partial dmesg output from >the successful boot (similar up to a point, some context included). I >couldn't get my serial port to accept input at the debugger prompt, >and my keyboard (USB) can't even "Press a key on the console to >reboot" when I have a non-ddb/kdb/etc kernel, so I couldn't do >anything once I got into the debugger. Hopefully what's below has >some useful information--if not, I'll be happy to try to get it.Without at least a backtrace, the only information that can be gleaned is that mtx_lock_sleep() is dereferencing a NULL pointer. This isn't much help.>options GDB >and set hint.sio.0.flags="0x80" in /boot/device.hints. What am I >missing to allow serial input when the debugger starts?This means that the serial port is expecting to talk to a remote GDB session, not a serial console. You probably want: - 'hint.sio.0.flags="0x10"' [no 'set'] in /boot/device.hints - '-Dh' in /boot.config Doing a verbose boot would probably also help. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20080301/80647663/attachment-0001.pgp