Re: i386-current bsd.rd fails on net6501

2015-09-09 Thread Mike Larkin
On Tue, Sep 08, 2015 at 10:23:57PM +0200, Christian Weisgerber wrote: > Mark Kettenis: > > > > ioapic0 at mainbus0: apid 0 pa 0xfec0, version 20, 24 pins > > > uvm_fault(0xd0b6c5e0, 0xd0d7e000, 0, 4) -> d > > > kernel: page fault trap, code=0 > > > Stopped at __kernel_bss_end+0x130c40:

Re: i386-current bsd.rd fails on net6501

2015-09-08 Thread Mike Larkin
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,

Re: i386-current bsd.rd fails on net6501

2015-09-08 Thread Mark Kettenis
> Date: Tue, 8 Sep 2015 20:02:45 +0200 > From: Christian Weisgerber > > 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

Re: i386-current bsd.rd fails on net6501

2015-09-08 Thread Christian Weisgerber
Mark Kettenis: > > ioapic0 at mainbus0: apid 0 pa 0xfec0, 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> > > no trace?

Re: i386-current bsd.rd fails on net6501

2015-09-08 Thread Mark Kettenis
> Date: Tue, 8 Sep 2015 12:03:28 -0700 > From: Mike Larkin > > 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:

Re: i386-current bsd.rd fails on net6501

2015-09-08 Thread Mike Larkin
On Tue, Sep 08, 2015 at 09:34:04PM +0200, Mark Kettenis wrote: > > Date: Tue, 8 Sep 2015 12:03:28 -0700 > > From: Mike Larkin > > > > On Tue, Sep 08, 2015 at 08:02:45PM +0200, Christian Weisgerber wrote: > > > Mark Kettenis: > > > > > > > Does the bsd kernel from the same

Re: i386-current bsd.rd fails on net6501

2015-09-08 Thread Christian Weisgerber
Mike Larkin: > 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; And that may very well be the last time I tried i386 on that machine. -- Christian "naddy" Weisgerber

i386-current bsd.rd fails on net6501

2015-09-08 Thread Christian Weisgerber
When I try to boot bsd.rd from the Sep 7 i386 snapshot on my Soekris net6501, it blows up. boot> boot bsd.rd booting hd0a:bsd.rd: 3176316+1310736+2057216+0+425984 [72+247696+238008]=0x71eb2c entry point at 0x2000d4 [7205c766, 3404, 24448b12, e568a304] Copyright (c) 1982, 1986, 1989, 1991,

Re: i386-current bsd.rd fails on net6501

2015-09-08 Thread Mark Kettenis
> Date: Tue, 8 Sep 2015 18:28:12 +0200 > From: Christian Weisgerber > > When I try to boot bsd.rd from the Sep 7 i386 snapshot on my Soekris > net6501, it blows up. > > boot> boot bsd.rd > booting hd0a:bsd.rd: 3176316+1310736+2057216+0+425984 > [72+247696+238008]=0x71eb2c >

Re: i386-current bsd.rd fails on net6501

2015-09-08 Thread Andre Smagin
On Tue, 8 Sep 2015 18:28:12 +0200 Christian Weisgerber wrote: > When I try to boot bsd.rd from the Sep 7 i386 snapshot on my Soekris > net6501, it blows up. > uvm_fault(0xd08627d8, 0xd0a68000, 0, 4) -> d > fatal page fault (6) in supervisor mode > trap type 6 code 11 eip

Re: i386-current bsd.rd fails on net6501

2015-09-08 Thread Christian Weisgerber
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, 3404, 24448b12, de60a304] [ using 816580 bytes of bsd ELF symbol table ] Copyright (c)