Date: Mon, 12 Aug 2013 22:25:48 -0700 From: Adrian Chadd <adrian@freebsd.org> To: sbruno@freebsd.org Cc: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: i386 panic Message-ID: <CAJ-VmokUOn6FvHbK5c2EBC=6TWqJmN-Ok0tweyuRW0Gp%2B2D4aA@mail.gmail.com> In-Reply-To: <1376368405.1474.2.camel@localhost> References: <1376336582.1469.9.camel@localhost> <CAEFD3DD-B324-4401-8CEA-BA3220D61C0F@samsco.org> <1376368405.1474.2.camel@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
... bug peter. And alfred. Alfred broke this stuff. :) -adrian On 12 August 2013 21:33, Sean Bruno <sean_bruno@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_bruno@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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmokUOn6FvHbK5c2EBC=6TWqJmN-Ok0tweyuRW0Gp%2B2D4aA>