[DragonFlyBSD - Bug #2408] Fatal trap 12: page fault Stopped at bsd4_setrunqueue on Pentium 4

[Alex Hornung via Redmine <bugtracker-admin@xxxxxxxxxxxxxxxxxxxxx>]

Issue #2408 has been updated by Alex Hornung.

File usched_package.patch added

Please try the attached patch and report the result of a boot verbose with that patch.

Cheers,
Alex
----------------------------------------
Bug #2408: Fatal trap 12: page fault Stopped at bsd4_setrunqueue on Pentium 4
http://bugs.dragonflybsd.org/issues/2408

Author: David Shao
Status: New
Priority: Normal
Assignee: 
Category: 
Target version: 


On a Pentium 4 Asus P4B266 motherboard using
set hw.apic_io_enable=0
some commit between
26dd35c9bbbbeffac40d091e7df63b02e7e2f078 rtld: Perform reloc before filtree dependency object init
and
b148267406ef2d0543d5d87d15c283b2d314516f kernel - Attempt to fix i386 wire_count panic (98)
produces a panic on boot:

Mounting root from ufs:/dev/serno/WD-WCAL75015619.s1a
DMA space used: 232k, remaining available: 16384k

Fatal trap 12: page fault while in kernel mode
cpuid = 0; lapic.id = 00000000
fault virtual address = 0xc
fault code            = supervisor read, page not present
instruction pointer   = 0x8 :0xc03dacaf
stack pointer         = 0x10:0xc0f4cd08
frame pointer         = 0x10:0xc0f4cd44
code segment          = base 0x0, limit 0xfffff, type 0x1b
                      = DPL 0, pres 1, def32 1, gran 1
processor eflags      = interrupt enabled, resume, IOPL = 0
current process       = 0 (swapper)
current thread        = pri 12 (CRIT)
 <- SMP: XXX
kernel: type 12 trap, code = 0

CPU0 stopping CPUs: 0x00000000
 stopped
Stopped at   bsd4_setrunqueue+0x1df: andl   0xc(%eax),%ecx

db> trace
bsd4_setrunqueue(c308b1d8,c05ed5d,c04a24c,e8,0) at bsd4_setrunqueue+0x1df 0xc03dacaf
start_forked_proc(c093bae0,cd6da460,c0f4cd98,c03a9a10,0) at start_forked_proc+0x90 0xc03c0e7b
kick_init(0,f48c00,f48c00,f59000,f59000) at kick_init+0x1b 0xc03a9915
mi_startup(f48000,0,0,0,0) at mi_startup+0x89 0xc03a9a10
begin() at begin+0x42 0xc016a7db


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account