Re: i386 panic
You need to enable PAE in the kernel to access that memory. I could be wrong. On Mon, Aug 12, 2013 at 3:43 PM, Sean Bruno sean_br...@yahoo.com wrote: http://people.freebsd.org/~sbruno/10_i386_vmfault.txt I can never tell if stuff like this is because I'm not nerfing the system RAM correctly or if this is i386 bit-rot. I set hw.physmem=2g in loader.conf to try and get the system to boot, but I don't think I did it right? Sean ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: i386 panic
Yah, I don't want to access the RAM, I just want the ridiculous box to boot. I'm content, for this test settting, to nerf myself to 4G rams. Sean On Mon, 2013-08-12 at 17:59 -0400, Super Bisquit wrote: You need to enable PAE in the kernel to access that memory. I could be wrong. On Mon, Aug 12, 2013 at 3:43 PM, Sean Bruno sean_br...@yahoo.com wrote: http://people.freebsd.org/~sbruno/10_i386_vmfault.txt I can never tell if stuff like this is because I'm not nerfing the system RAM correctly or if this is i386 bit-rot. I set hw.physmem=2g in loader.conf to try and get the system to boot, but I don't think I did it right? Sean signature.asc Description: This is a digitally signed message part
Re: i386 panic
On Mon, 2013-08-12 at 12:43 -0700, Sean Bruno wrote: http://people.freebsd.org/~sbruno/10_i386_vmfault.txt I can never tell if stuff like this is because I'm not nerfing the system RAM correctly or if this is i386 bit-rot. I set hw.physmem=2g in loader.conf to try and get the system to boot, but I don't think I did it right? Sean The 9.2RC images seem to do the same thing when nerfed to 2G of ram. So, this doesn't appear to be a new regression. stable/7 seems to be happy enough to boot up PAE i386 on it, so I think the previous suggestion of using PAE is the correct one. signature.asc Description: This is a digitally signed message part
Re: i386 panic
Download the source and build the PAE kernel. Do the build world. On Mon, Aug 12, 2013 at 7:02 PM, Sean Bruno sean_br...@yahoo.com wrote: On Mon, 2013-08-12 at 12:43 -0700, Sean Bruno wrote: http://people.freebsd.org/~sbruno/10_i386_vmfault.txt I can never tell if stuff like this is because I'm not nerfing the system RAM correctly or if this is i386 bit-rot. I set hw.physmem=2g in loader.conf to try and get the system to boot, but I don't think I did it right? Sean The 9.2RC images seem to do the same thing when nerfed to 2G of ram. So, this doesn't appear to be a new regression. stable/7 seems to be happy enough to boot up PAE i386 on it, so I think the previous suggestion of using PAE is the correct one. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: i386 panic
On Aug 12, 2013, at 1:43 PM, Sean Bruno sean_br...@yahoo.com wrote: http://people.freebsd.org/~sbruno/10_i386_vmfault.txt I can never tell if stuff like this is because I'm not nerfing the system RAM correctly or if this is i386 bit-rot. I set hw.physmem=2g in loader.conf to try and get the system to boot, but I don't think I did it right? That shouldn't happen. Maybe you've run out of kmem? It's limited to only like 400MB on i386. Or maybe you've blown out a data structure with all of those CPUs. Scott ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: i386 panic
On Mon, 2013-08-12 at 21:36 -0600, Scott Long wrote: On Aug 12, 2013, at 1:43 PM, Sean Bruno sean_br...@yahoo.com wrote: http://people.freebsd.org/~sbruno/10_i386_vmfault.txt I can never tell if stuff like this is because I'm not nerfing the system RAM correctly or if this is i386 bit-rot. I set hw.physmem=2g in loader.conf to try and get the system to boot, but I don't think I did it right? That shouldn't happen. Maybe you've run out of kmem? It's limited to only like 400MB on i386. Or maybe you've blown out a data structure with all of those CPUs. Scott Since we can still do this on stable/7 (gross), I kind of think this is a low priority regression. Not even sure where to look, nor do I really want to. :-) If someone has a clueby4 to thwack me around with, I'd appreciate it. Sean p.s. We won't be caring about this for much longer I fear over at $DAYJOB, so if someone wants to address this I can test it for a few more months. After that, we won't care about it too much. signature.asc Description: This is a digitally signed message part
Re: i386 panic
... bug peter. And alfred. Alfred broke this stuff. :) -adrian On 12 August 2013 21:33, Sean Bruno sean_br...@yahoo.com wrote: On Mon, 2013-08-12 at 21:36 -0600, Scott Long wrote: On Aug 12, 2013, at 1:43 PM, Sean Bruno sean_br...@yahoo.com wrote: http://people.freebsd.org/~sbruno/10_i386_vmfault.txt I can never tell if stuff like this is because I'm not nerfing the system RAM correctly or if this is i386 bit-rot. I set hw.physmem=2g in loader.conf to try and get the system to boot, but I don't think I did it right? That shouldn't happen. Maybe you've run out of kmem? It's limited to only like 400MB on i386. Or maybe you've blown out a data structure with all of those CPUs. Scott Since we can still do this on stable/7 (gross), I kind of think this is a low priority regression. Not even sure where to look, nor do I really want to. :-) If someone has a clueby4 to thwack me around with, I'd appreciate it. Sean p.s. We won't be caring about this for much longer I fear over at $DAYJOB, so if someone wants to address this I can test it for a few more months. After that, we won't care about it too much. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: i386 panic
On Mon, Aug 12, 2013 at 12:43:02PM -0700, Sean Bruno wrote: http://people.freebsd.org/~sbruno/10_i386_vmfault.txt I can never tell if stuff like this is because I'm not nerfing the system RAM correctly or if this is i386 bit-rot. I set hw.physmem=2g in loader.conf to try and get the system to boot, but I don't think I did it right? Sean kernel trap 12 with interrupts disabled panic: vm_fault: fault on nofault entry, addr: c9f7c000 ... calltrap() at calltrap+0x6/frame 0xc1820c9c --- trap 0xc, eip = 0xc1820d37, esp = 0xc1820ce8, ebp = 0 --- end() at 0xc1820d37 First thing is to try to identify what is the code was executing there. Try to disassemble some amount of instructions before and after the faulting %eip. pgpbg0qmz9zwC.pgp Description: PGP signature
