freebsd stable - Feb 2012 - FreeBSD 9.0-RELEASE - Trouble Booting on SPARC64 - kmem_suballoc error

Hello,

 

I hope you are well. I've been working on a Sun Blade 2000 with FreeBSD 9.0
(sparc64) installed.

 

There's trouble with /boot/loader.conf when you try to boot the install disc
(and even after the install when I try to boot up):

 

panic: kmem_suballoc: bad status return of 3
cpuid = 0
KDB: stack backtrace:
 #0 0xc079841c at ??+0
 #1 0xc04ca59c at ??+0
 #2 0xc0487f90 at ??+0
 #3 0xc0098028 at ??+0

 

So when it gives me the chance to enter a boot command, I enter the
following:

 

OK set hw.physmem=1048576000

OK boot

 

That seems to do the trick. And I've since added it to loader.conf so I
don't have to enter the command each time I boot up.

 

Please let me know if there's anything I can do as I'd like my machine
to be
able to utilize the full memory capabilities.

 

Thank you,

 

Garrett Groesbeck

garrett.groesbeck@gmail.com

On Sun, Feb 26, 2012 at 11:31 PM, Garrett R. Groesbeck
<garrett.groesbeck@gmail.com> wrote:
> I hope you are well. I've been working on a Sun Blade 2000 with FreeBSD
9.0
> (sparc64) installed.
>
(... snip ...)
>
> panic: kmem_suballoc: bad status return of 3
> cpuid = 0
> KDB: stack backtrace:
> ?#0 0xc079841c at ??+0
> ?#1 0xc04ca59c at ??+0
> ?#2 0xc0487f90 at ??+0
> ?#3 0xc0098028 at ??+0
>
(... snip ...)
>
> Please let me know if there's anything I can do as I'd like my
machine to be
> able to utilize the full memory capabilities.
Please try the following patch in sparc64/164227:

http://www.freebsd.org/cgi/query-pr.cgi?pr=sparc%2F164227&cat
> Thank you,
>
> Garrett Groesbeck
>
> garrett.groesbeck@gmail.com
Regards,
-cpghost.

-- 
Cordula's Web. http://www.cordula.ws/

On Sun, Feb 26, 2012 at 05:31:35PM -0500, Garrett R. Groesbeck
wrote:
> Hello,
> 
> I hope you are well. I've been working on a Sun Blade 2000 with FreeBSD
9.0
> (sparc64) installed.
> 
> There's trouble with /boot/loader.conf when you try to boot the install
disc
> (and even after the install when I try to boot up):
> 
> panic: kmem_suballoc: bad status return of 3
> 
> So when it gives me the chance to enter a boot command, I enter the
> following:
> 
> OK set hw.physmem=1048576000
> 
That apparently is a bug in the MI part of the VM triggered by the
highly fragment physical memory of b1k and b2k with 2 GB of RAM.
You can work around it by setting the vm.kmem_size_scale tunable to
2 without sacrificing physical memory. The latter meanwhile is also
the default set by the MD part, awaiting further clues from alc@.

Marius