Re: kernel panic with greater that 8 GB of memory

From: Scott Long <scottl_at_freebsd.org>
Date: Tue, 30 Nov 2004 06:04:56 -0700
Steve Kargl wrote:
> On Mon, Nov 29, 2004 at 01:13:41PM -0800, Steve Kargl wrote:
> 
>>kmem_suballoc: bad status return of 3
>>panic: kmem_suballoc
>>cpuid = 0
>>KDB: stack backtrace:
>>kdb_backtrace() at kdb_backtrace+0x37
>>panic() at painc+0x1d1
>>kmem_suballoc() at kmem_suballoc+0x93
>>kmeminit() at kmeminit+0x16d
>>mi_startuup() at mi_startup+0xb6
>>btext90 at btext+0x2c
>>KDB: enter: panic
>>[thread pid 0 tid 0]
>>
>>This is a Tyan K8S Pro motherboard with 16 GB of PC2700
>>Cosair ECC memory.  The BIOS was flashed to the latest
>>available from Tyan.  The scheduler is 4BSD.  There are
>>no ATA devices in the system and no ATA subsystem in
>>the kernel.  This a SCSI only box.   World and kernel
>>were rebuilt today with CFLAGS=-O -pipe and
>>COPTFLAGS=-O -pipe.
>>
>>If I set hw.physmem="#G" n /boot/loader.conf where # is
>>less than or equal to 8 the box boots up (see dmesg below).
>>If # > 8, then we have the above panic.
>>
>>Any ideas where to look for the a fix?
>>
> 
> 
> (dmesg snipped)
> (CC'd to -current because the may impact any system with >8 GB of ram)
> 
> As a data point, I've downloaded, burned, and booted the netbsd/amd64
> ISO image.  Netbsd's dmesg shows that netbsd correctly finds 16 GB
> of memory on the system.  
> 

I fixed this on i386 a few months ago, and I applied a similar fix to
amd64 on the advice of Peter Wemm.  Go beat him up on this one =-)

Scott
Received on Tue Nov 30 2004 - 12:04:31 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:23 UTC