Date: Mon, 29 Nov 2004 15:32:11 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: freebsd-amd64@freebsd.org Cc: freebsd-current@freebsd.org Subject: Re: kernel panic with greater that 8 GB of memory Message-ID: <20041129233211.GA27426@troutmask.apl.washington.edu> In-Reply-To: <20041129211341.GA26548@troutmask.apl.washington.edu> References: <20041129211341.GA26548@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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. -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041129233211.GA27426>