Ulrich Spoerlein
2008-May-14 15:58 UTC
RELENG_6 regression: panic: vm_fault on nofault entry, addr: c8000000
Hi,
there's a regression going from 6.2 to 6.3, where it will panic upon
booting the kernel within vm_fault. This problem has been discussed
before, but I'm seeing it reliably on a RELENG_6 checkout from 5th of
May.
It affects multiple (but identical) systems, here's an verbose boot
leading to the panic. Please note that 6.2 was running fine on these
machines, they also boot "normally" if I disable ACPI (but this is not
really an option).
SMAP type=01 base=0000000000000000 len=000000000009d800
SMAP type=02 base=000000000009d800 len=0000000000002800
SMAP type=02 base=00000000000ce000 len=0000000000002000
SMAP type=02 base=00000000000e4000 len=000000000001c000
SMAP type=01 base=0000000000100000 len=00000000cfe60000
SMAP type=03 base=00000000cff60000 len=0000000000009000
SMAP type=04 base=00000000cff69000 len=0000000000017000
SMAP type=02 base=00000000cff80000 len=0000000000080000
SMAP type=02 base=00000000e0000000 len=0000000010000000
SMAP type=02 base=00000000fec00000 len=0000000000010000
SMAP type=02 base=00000000fee00000 len=0000000000001000
SMAP type=02 base=00000000ff000000 len=0000000001000000
SMAP type=01 base=0000000100000000 len=0000000030000000
786432K of memory above 4GB ignored
Copyright (c) 1992-2008 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 6.3-20080505-SNAP #0: Mon May 5 11:42:32 UTC 2008
root@fbsdbuild.1822direkt.com:/usr/obj/usr/src/sys/GENERIC
Preloaded elf kernel "/boot/kernel/kernel" at 0xc1051000.
Preloaded mfs_root "/boot/mfsroot" at 0xc10511e8.
Preloaded elf module "/boot/modules/acpi.ko" at 0xc105122c.
MP Configuration Table version 1.4 found at 0xc009dd71
Table 'FACP' at 0xcff68e48
Table 'APIC' at 0xcff68ebc
MADT: Found table at 0xcff68ebc
APIC: Using the MADT enumerator.
MADT: Found CPU APIC ID 0 ACPI ID 0: enabled
MADT: Found CPU APIC ID 4 ACPI ID 1: enabled
MADT: Found CPU APIC ID 2 ACPI ID 2: enabled
MADT: Found CPU APIC ID 6 ACPI ID 3: enabled
ACPI APIC Table: <PTLTD APIC >
Calibrating clock(s) ... i8254 clock: 1193204 Hz
CLK_USE_I8254_CALIBRATION not specified - using default frequency
Timecounter "i8254" frequency 1193182 Hz quality 0
Calibrating TSC clock ... TSC clock: 3000122064 Hz
CPU: Intel(R) Xeon(TM) CPU 3.00GHz (3000.12-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0xf64 Stepping = 4
Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
Features2=0xe4bd<SSE3,RSVD2,MON,DS_CPL,VMX,EST,CNXT-ID,CX16,xTPR,PDCM>
AMD Features=0x20100000<NX,LM>
AMD Features2=0x1<LAHF>
Cores per package: 2
Logical CPUs per core: 2
real memory = 3489005568 (3327 MB)
Physical memory chunk(s):
0x0000000000001000 - 0x000000000009cfff, 638976 bytes (156 pages)
0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages)
0x0000000001425000 - 0x00000000cc488fff, 3406184448 bytes (831588 pages)
avail memory = 3405979648 (3248 MB)
bios32: Found BIOS32 Service Directory header at 0xc00f5960
bios32: Entry = 0xfd520 (c00fd520) Rev = 0 Len = 1
pcibios: PCI BIOS entry at 0xfd520+0x247
pnpbios: Found PnP BIOS data at 0xc00f59e0
pnpbios: Entry = f0000:af28 Rev = 1.0
Other BIOS signatures found:
APIC: CPU 0 has ACPI ID 0
MADT: Found IO APIC ID 8, Interrupt 0 at 0xfec00000
ioapic0: Routing external 8259A's -> intpin 0
MADT: Found IO APIC ID 9, Interrupt 24 at 0xfec80000
lapic0: Routing NMI -> LINT1
lapic0: LINT1 trigger: edge
lapic0: LINT1 polarity: high
lapic4: Routing NMI -> LINT1
lapic4: LINT1 trigger: edge
lapic4: LINT1 polarity: high
lapic2: Routing NMI -> LINT1
lapic2: LINT1 trigger: edge
lapic2: LINT1 polarity: high
lapic6: Routing NMI -> LINT1
lapic6: LINT1 trigger: edge
lapic6: LINT1 polarity: high
MADT: Interrupt override: source 0, irq 2
ioapic0: Routing IRQ 0 -> intpin 2
MADT: Interrupt override: source 9, irq 9
ioapic0: intpin 9 trigger: level
ioapic0 <Version 2.0> irqs 0-23 on motherboard
ioapic1 <Version 2.0> irqs 24-47 on motherboard
cpu0 BSP:
ID: 0x00000000 VER: 0x00050014 LDR: 0xff000000 DFR: 0xffffffff
lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff
timer: 0x000100ef therm: 0x00000200 err: 0x00010000 pcm: 0x00010000
ath_rate: version 1.2 <SampleRate bit-rate selection algorithm>
wlan: <802.11 Link Layer>
null: <null device, zero device>
random: <entropy source, Software, Yarrow>
nfslock: pseudo-device
io: <I/O>
kbd: new array size 4
kbd1 at kbdmux0
mem: <memory>
Pentium Pro MTRR support enabled
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
rr232x: RocketRAID 232x controller driver v1.02 (May 5 2008 11:42:16)
hptrr: HPT RocketRAID controller driver v1.1 (May 5 2008 11:42:14)
npx0: INT 16 interface
acpi0: <PTLTD RSDT> on motherboard
ioapic0: routing intpin 9 (ISA IRQ 9) to vector 48
acpi0: [MPSAFE]
pci_open(1): mode 1 addr port (0x0cf8) is 0x80008058
pci_open(1a): mode1res=0x80000000 (0x80000000)
pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=25d88086)
pcibios: BIOS version 2.10
AcpiOsDerivePciId: \_SB_.PCI0.LPC0.PIRX -> bus 0 dev 31 func 0
AcpiOsDerivePciId: \_SB_.PCI0.LPC0.PIRY -> bus 0 dev 31 func 0
acpi0: Power Button (fixed)
acpi0: wakeup code va 0xdca93000 pa 0x9c000
AcpiOsDerivePciId: \_SB_.PCI0.LPC0.REGS -> bus 0 dev 31 func 0
ACPI timer: 1/0 1/0 1/0 1/0 1/0 1/0 1/0 1/0 1/0 1/0 -> 10
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
pci_link0: Index IRQ Rtd Ref IRQs
Initial Probe 0 7 N 0 3 4 5 6 7 10 11 14 15
Validation 0 7 N 0 3 4 5 6 7 10 11 14 15
After Disable 0 255 N 0 3 4 5 6 7 10 11 14 15
pci_link1: Index IRQ Rtd Ref IRQs
Initial Probe 0 5 N 0 3 4 5 6 7 10 11 14 15
Validation 0 5 N 0 3 4 5 6 7 10 11 14 15
After Disable 0 255 N 0 3 4 5 6 7 10 11 14 15
pci_link2: Index IRQ Rtd Ref IRQs
Initial Probe 0 11 N 0 3 4 5 6 7 10 11 14 15
Validation 0 11 N 0 3 4 5 6 7 10 11 14 15
After Disable 0 255 N 0 3 4 5 6 7 10 11 14 15
pci_link3: Index IRQ Rtd Ref IRQs
Initial Probe 0 10 N 0 3 4 5 6 7 10 11 14 15
Validation 0 10 N 0 3 4 5 6 7 10 11 14 15
After Disable 0 255 N 0 3 4 5 6 7 10 11 14 15
pci_link4: Index IRQ Rtd Ref IRQs
Initial Probe 0 255 N 0 3 4 5 6 7 10 11 14 15
Validation 0 255 N 0 3 4 5 6 7 10 11 14 15
After Disable 0 255 N 0 3 4 5 6 7 10 11 14 15
pci_link5: Index IRQ Rtd Ref IRQs
Initial Probe 0 255 N 0 4 5 6 7 10 11 14 15
Validation 0 255 N 0 4 5 6 7 10 11 14 15
After Disable 0 255 N 0 4 5 6 7 10 11 14 15
pci_link6: Index IRQ Rtd Ref IRQs
Initial Probe 0 255 N 0 3 4 5 6 7 10 11 14 15
Validation 0 255 N 0 3 4 5 6 7 10 11 14 15
After Disable 0 255 N 0 3 4 5 6 7 10 11 14 15
pci_link7: Index IRQ Rtd Ref IRQs
Initial Probe 0 255 N 0 4 5 6 7 10 11 14 15
Validation 0 255 N 0 4 5 6 7 10 11 14 15
After Disable 0 255 N 0 4 5 6 7 10 11 14 15
cpu0: <ACPI CPU> on acpi0
panic: vm_fault: fault on nofault entry, addr: c8000000
Uptime: 1s
Automatic reboot in 15 seconds - press a key on the console to abort
--> Press a key on the console to reboot,
--> or switch off the system now.
Rebooting...
What to do?
Uli
Gavin Atkinson
2008-May-14 18:21 UTC
RELENG_6 regression: panic: vm_fault on nofault entry, addr: c8000000
On Wed, 2008-05-14 at 17:32 +0200, Ulrich Spoerlein wrote:> Hi, > > there's a regression going from 6.2 to 6.3, where it will panic upon > booting the kernel within vm_fault. This problem has been discussed > before, but I'm seeing it reliably on a RELENG_6 checkout from 5th of > May. > > It affects multiple (but identical) systems, here's an verbose boot > leading to the panic. Please note that 6.2 was running fine on these > machines, they also boot "normally" if I disable ACPI (but this is not > really an option).[snip dmesg output]> What to do?If you don't get any suggestions from people as to what it may be, and you have a system you can afford to reboot a few times, the easiest thing to do is to take the system back to 6.2, and then update your source to a date midway between 6.2 and 6.3 and see if that crashes. Use this in your supfile: *default tag=RELENG_6 *default date=2007.07.01.00.00.00 (For reference, 6.2 was released on 2007.01.15, with 6.3 on 2008.01.18)>From then, go half way again either forwards or backwards, to narrowdown the window when the problem was introduced - with only eight kernel recompiles you should be able to narrow it down to a one-day window, and looking at the spec of the machine you should be able to do that in a morning :). Once you've got it down to a window of a couple of days or less, give csup the "-L 2" option, and it'll give you a list of files changed between dates. Obviously this is dependant on you being able to take one of the affected machines down for a few hours, but if you can, this may well be the quickest way of establishing when the problem was introduced. Out of interest, what type of hardware is this? Gavin
Seemingly Similar Threads
- Xorg nvidia-driver GT 650M cause system reboot on my MacBook Retina 9.1RC1
- Problem detecting Sil3124 SATA controllers off of Sandy Bridge northbridge-connected PCIe slots
- ACPI Error: No handler for Region [POWS] (0xffffff000994f380) [IPMI] on Cisco UCS C200 M2
- Can't get if_txp(4) to attach to a 3CR990B-TXM NIC
- strange deadlock and magic resurrection with RELENG_6