On Tue, Sep 08, 2015 at 08:02:45PM +0200, Christian Weisgerber wrote:
> Mark Kettenis:
> 
> > Does the bsd kernel from the same snapshot blow up as well?
> 
> Yes.
> 
> booting hd0a:bsd.i386: 7520308+2015344+189444+0+1069056 
> [72+411072+405023]=0xb155c4
> entry point at 0x2000d4 [7205c766, 34000004, 24448b12, de60a304]
> 
> [ using 816580 bytes of bsd ELF symbol table ]
> Copyright (c) 1982, 1986, 1989, 1991, 1993
>         The Regents of the University of California.  All rights reserved.
> Copyright (c) 1995-2015 OpenBSD. All rights reserved.  http://www.OpenBSD.org
> 
> OpenBSD 5.8-current (GENERIC) #1156: Mon Sep  7 07:02:35 MDT 2015
>     [email protected]:/usr/src/sys/arch/i386/compile/GENERIC
> cpu0: Genuine Intel(R) CPU @ 1.00GHz ("GenuineIntel" 686-class) 1.01 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,PBE,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,LAHF,PERF,SENSOR
> real mem  = 1073086464 (1023MB)
> avail mem = 1040211968 (992MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: date 20/21/15, BIOS32 rev. 0 @ 0xfac40
> mpbios0 at bios0: Intel MP Specification 1.4
> cpu0 at mainbus0: apid 0 (boot processor)
> mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
> cpu0: apic clock running at 100MHz
> cpu0: mwait min=64, max=64, C-substates=0.2.2.0.2.0.3, IBE
> cpu at mainbus0: not configured
> mpbios0: bus 0 is type PCI   
> mpbios0: bus 64 is type ISA   
> ioapic0 at mainbus0: apid 0 pa 0xfec00000, version 20, 24 pins
> uvm_fault(0xd0b6c5e0, 0xd0d7e000, 0, 4) -> d
> kernel: page fault trap, code=0
> Stopped at      __kernel_bss_end+0x130c40:      cmpl    $0x49435024,%eax
> ddb> 
>

That address and instruction seem bogus. When did it last work?

This seems awfully similar to the other bug we fixed in Calgary a couple
months back; I'm wondering if there is another similar issue. I looked last
time and didn't see anything but may have missed something.
 
> -- 
> Christian "naddy" Weisgerber                          [email protected]
> 

Reply via email to