Re: panic on 08 jan 2009 snapshot. **update**

2009-01-09 Thread Bryan
On Fri, Jan 9, 2009 at 9:16 PM, Bryan bra...@gmail.com wrote:
 Greetings,

 previous snapshots were able to boot with no issues.  I'm using
 GENERIC.MP, and the panic occurs when using GENERIC.SP.

 here is the panic message: (typed)
 dmesg output

 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
 uvm_fault(0xd080c660, 0x12e52000, 0, 3) - e
 kernel: page fault trap, code=0
 stopped at   apic_vectorset+0x50:  movl 
 %esi,apic_maxlevel(,%eax,4)
 apic_vectorset(d3f1d800,0,ff,0,0) at apic_vectorset+0x50
 ioapic_enable(d080c660,0,d0965fa0,d034d1a3,d08c1720) at ioapic_enable+0x8f
 cpu_configure(d08c1720,1,3,0,2) at cpu_configure+0x42
 main(0,0,0,0,0) at main+0x3a7


 I do not have my pci serial port card yet (comes in Tuesday..., so I
 took screenshots of the dmesg, PS and TRACE.

 here is the *typed* output of trace:

 ddb(0)trace
 apic_vectorset(d3f1d800,0,ff,0,0) at apic_vectorset+0x50
 ioapic_enable(d080c660,0,d0965fa0,d034d1a3,d08c1720) at ioapic_enable+0x8f
 cpu_configure(d08c1720,1,3,0,2) at cpu_configure+


 ps output can be found here:  (until I get my serial port card, this
 is the best I can do.)
 http://picasaweb.google.com/lh/photo/l7IN31cOVXa1y8yn74aA8w?feat=directlink

 link to the dmesg, ps, and trace can be found in this album:

 http://picasaweb.google.com/brakeb/CrashUsing08jan2009Snapshot?feat=directlink


 please advise.  I originally thought that this panic was due to the
 re(4) that was not reset.
 I can reproduce this. I first received this error right after I did
 the 08 jan 2009 snapshot.  I did mention this earlier to the list, and
 was told by theo that the 06 jan snapshot would fix this, and it did
 seem to fix this, and I was able to even use re(4).

 To reproduce the re(4) error, I can boot into Vista, shutdown, and
 boot into OpenBSD.

 After the panic, I hold the power button for 4 seconds, and then boot
 back up.  the error goes away, as you can see at the bottom of picture
 number 4.  but it still panics, now on something else.  I am unable to
 get to a login, so I can't do patches.  I can wait for snapshots.

 I apologize for the stream of consciousness, I just want to make
 sure that any questions that anyone might have are answered...

 Regards,
 Bryan Brake


Greetings,

One other thing I found. Don't know if it means anything, but when I
rebooted and enabled verbose output, the system panics shortly after
it scans pcic2:

typed as seen:

 probing for pcic0
 probing for pcic0 failed
 probing for pcic1
 probing for pcic1 failed
 probing for pcic2
 probing for pcic2 failed
uvm_fault(0xd080c660, 0x12e52000, 0, 3) - e
kernel: page fault trap, code=0
stopped at   apic_vectorset+0x50:  movl %esi,apic_maxlevel(,%eax,4)
apic_vectorset(d3f1d800,0,ff,0,0) at apic_vectorset+0x50
ioapic_enable(d080c660,0,d0965fa0,d034d1a3,d08c1720) at ioapic_enable+0x8f
cpu_configure(d08c1720,1,3,0,2) at cpu_configure+0x42
main(0,0,0,0,0) at main+0x3a7


Regards,
Bryan Brake



Re: panic on 08 jan 2009 snapshot. **update**

2009-01-09 Thread jared r r spiegel
On Fri, Jan 09, 2009 at 09:26:00PM -0800, Bryan wrote:
 On Fri, Jan 9, 2009 at 9:16 PM, Bryan bra...@gmail.com wrote:
  Greetings,
 
  previous snapshots were able to boot with no issues.  I'm using
  GENERIC.MP, and the panic occurs when using GENERIC.SP.

  be sure to sendbug(1) this if you have not yet; remember a few
  times sendbug in this situation that being specifically requested.

  some devs don't read m...@.

-- 

  jared