Date: Thu, 12 Jul 2012 19:43:23 -0400 From: Justin Hibbits <chmeeedalf@gmail.com> To: FreeBSD PowerPC ML <freebsd-ppc@freebsd.org> Cc: freebsd-current <freebsd-current@FreeBSD.org> Subject: panic with DEBUG_MEMGUARD on PowerPC Message-ID: <A3CD63CD-694A-48F5-B0F7-9C8923AFCB90@gmail.com>
next in thread | raw e-mail | index | archive | help
When tracking down a panic exposed by INVARIANTS, I tried setting DEBUG_MEMGUARD, so I could find the culprit that's trashing freed memory. However, this causes a panic at bootup. It shows up right after the first WARNING: WITNESS message, with the following: panic: kmem_suballoc: bad status return of 3 cpuid = 0 KDB: stack backtrace: 0xd0004ad0: at kdb_backtrace+0x4c 0xd0004b40: at panic+0x224 0xd0004ba0: at kmem_suballoc+0x8c 0xd0004bd0: at kmeminit+0x1ac 0xd0004c20: at mi_startup+0x13c 0xd0004c50: at btext+0xc0 Tracing, and printf() debugging, I see arguments to vm_map_findspace(): start: 0xD0000000, length: 4246446080, and map- >max_offset = 4026531839. Beyond that, I'm lost with tracking this down. Machine is a dual processor PowerPC G4, with 2GB RAM. Anyone have any ideas? Thanks, Justin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A3CD63CD-694A-48F5-B0F7-9C8923AFCB90>