On Sun, Jan 11, 2009 at 1:40 PM, Tom Cosgrove <tom.cosgr...@arches-consulting.com> wrote: > This appears to be fixed in -current/the latest snapshot. > > Can you try a version >= the following (which fixed exactly the same > problem on my laptop): > > OpenBSD 4.4-current (GENERIC.MP) #32: Fri Jan 9 10:34:10 MST 2009 > t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP > cpu0: Intel(R) Atom(TM) CPU N270 @ 1.60GHz ("GenuineIntel" 686-class) 1.60 > GHz > cpu0: > FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,EST,TM2,xTPR > real mem = 1060163584 (1011MB) > avail mem = 1016823808 (969MB) > mainbus0 at root > > > Thanks > > Tom > >>>> Barry Commander 9-Jan-09 14:59 >>> >> >> Hi >> This is the first problem I've had with OpenBSD, I think I've attached all >> relevant information but if i've neglected anything please let me know. >> I'm getting the following panic at boot time with the latest snapshot dated >> 1/9/09 >> >> uvm_fault(0xd08084a0, 0x12e3e000, 0, 3) -> e >> kernel: page fault trap, code=0 >> Stopped at apic_vectorset+0x50: movl %esi,apic_maxlevel(,%eax,4) >> apic_vectorset(d128fb00,0,ff,0,0) at apic_vectorset+0x50 >> ioapic_enable(d08084a0,0,d0961fa0,d034bc99,d08bd540) at ioapic_enable+0x8f >> cpu_configure(d08bd540,1,3,0,2) at cpu_configure+0x42 >> main(0,0,0,0,0) at main+0x399 >> ddb> trace >> apic_vectorset(d128fb00,0,ff,0,0) at apic_vectorset+0x50 >> ioapic_enable(d08084a0,0,d0961fa0,d034bc99,d08bd540) at ioapic_enable+0x8f >> cpu_configure(d08bd540,1,3,0,2) at cpu_configure+0x42 >> main(0,0,0,0,0) at main+0x399 > > Greetings, The issue was fixed, at least for me it was. I'm still having issues with my re(4) nic causing a panic, but I need to produce the error again (which I can), and use sendbug(1), which I was correctly chastised for not using...
Just have to read up on how to send a proper bug report... :) regards, Bryan