Date: Sat, 30 Sep 2000 19:56:25 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: freebsd-alpha@freebsd.org Cc: dfr@nlsystems.com Subject: size problems with INVARIANTS/DIAGNOSTIC -current kernels Message-ID: <14806.26688.509296.391897@grasshopper.cs.duke.edu>
next in thread | raw e-mail | index | archive | help
With an INVARIANTS/DIAGNOSTIC kernel, my -current machines are locking up (or halting) at boot with a stack that looks like the following: malloc resource_create resource_set_string hints_load mi_startup (discovered with printfs) At the point it hangs, there should be a trap the first time malloc touches kmemusage (kup->ku_indx = indx;, line 203 of kern_malloc.c). I assume this is happening the first time the kernel touches mapped (not kseg) memory. Rather than taking a trap & doing the normal vm magic, the machine just sits there. It sometimes will eventually halt. When it does, I see >>>e pc PC psr: 0 ( PC) FFFFFC00006960F8 >>>e ra gpr: 1A ( R26) FFFFFC00005E1F4C The RA maps to XentMM: (gdb) l *0xFFFFFC00005E1F4C 0xfffffc00005e1f4c is in XentMM (../../alpha/alpha/exception.s:94). 89 PALVECT(XentMM) /* setup frame, save registers */ 90 91 /* a0, a1, & a2 already set up */ 92 ldiq a3, ALPHA_KENTRY_MM 93 mov sp, a4 ; .loc 1 __LINE__ 94 CALL(trap) 95 96 jmp zero, exception_return 97 END(XentMM) The PC is off in the data segment (doesn't map to anything in the kernel text). trap is 0xfffffc00005f4460 Hmmm.... After more debugging, I'm fairly sure this is a size issue. A much smaller kernel (all unneeded devs, IPv6, etc, stripped out but with INVARIANTS/DIAGNOSTIC options), boots just fine. I need some help here.. Thanks, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14806.26688.509296.391897>