So, trying to get a massively overpowered HP box up with 7.3 amd64 version up and running. I can't tell at the moment, but it looks like the installer kernel is having issues with >32GB of RAM in this box. Are we using the i386 kernel on amd64 installs? Sean
On Fri, Oct 15, 2010 at 09:04:53AM -0700, Sean Bruno wrote:> So, trying to get a massively overpowered HP box up with 7.3 amd64 > version up and running. > > I can't tell at the moment, but it looks like the installer kernel is > having issues with >32GB of RAM in this box. > > Are we using the i386 kernel on amd64 installs?If you booted a FreeBSD image that has "amd64" in the ISO name, then the kernel is actually 64-bit (amd64). The only i386 piece would be the bootloader. There's probably someone here who can help with the issue you describe, as there's occasional posts here and there from people who experience issues/problems when using very large amounts of RAM. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
on 15/10/2010 19:04 Sean Bruno said the following:> So, trying to get a massively overpowered HP box up with 7.3 amd64 > version up and running. > > I can't tell at the moment, but it looks like the installer kernel is > having issues with >32GB of RAM in this box. > > Are we using the i386 kernel on amd64 installs?Is there anything else peculiar about this system besides RAM? Because 32GB+ do not impress actually :) -- Andriy Gapon
On Tuesday, October 19, 2010 1:16:07 am Andriy Gapon wrote:> on 19/10/2010 06:11 Wilkinson, Alex said the following: > > Will it work something like http://freshmeat.net/projects/mcelog/ ? > > jhb has a port of this, yes.The relevant bits are at http://www.FreeBSD.org/~jhb/mcelog/ I should probably make this into a port, but I really need to e-mail the mcelog folks about integrating the patches into their tree. -- John Baldwin
On Thu, 2010-10-21 at 05:48 -0700, Andriy Gapon wrote:> on 20/10/2010 21:28 Sean Bruno said the following: > > I guess, I could replace the kernel on the CD and have them reburn it? > > That should work. > BTW, here I described "yet another" way of building custom recovery/installation > CDs that I use: > http://wiki.freebsd.org/AvgLiveCD >Before I get started on this, it looks like something else is going on. Here is a panic + trace on the latest 9-current snap shot. "hammer time" indeed. Suggestions are welcome! http://people.freebsd.org/~sbruno/9-current-panic.png http://people.freebsd.org/~sbruno/9-current-trace-panic.png Sean
On Thu, Oct 21, 2010 at 09:50:03AM -0700, Sean Bruno wrote:> On Thu, 2010-10-21 at 05:48 -0700, Andriy Gapon wrote: > > on 20/10/2010 21:28 Sean Bruno said the following: > > > I guess, I could replace the kernel on the CD and have them reburn it? > > > > That should work. > > BTW, here I described "yet another" way of building custom recovery/installation > > CDs that I use: > > http://wiki.freebsd.org/AvgLiveCD > > > > Before I get started on this, it looks like something else is going on. > > Here is a panic + trace on the latest 9-current snap shot. "hammer > time" indeed. > > Suggestions are welcome! > > > http://people.freebsd.org/~sbruno/9-current-panic.png > > http://people.freebsd.org/~sbruno/9-current-trace-panic.pngIt feels like msgbufp variable has absurd value. Can you arrange to get the output of verbose boot, esp. the SMAP lines ? Also, you could add printfs near amd64/amd64/machdep.c:1517 /* Map the message buffer. */ msgbufp = (struct msgbuf *)PHYS_TO_DMAP(phys_avail[pa_indx]); to show the values of all participants, i.e. msgbufp, pa_indx and phys_avail[pa_indx]. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20101021/10a63f68/attachment.pgp