From owner-freebsd-alpha Thu Jun 7 14:52:32 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id D439B37B403; Thu, 7 Jun 2001 14:52:25 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f57Lpg137854; Thu, 7 Jun 2001 14:51:42 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <15135.58016.753596.764419@grasshopper.cs.duke.edu> Date: Thu, 07 Jun 2001 14:51:48 -0700 (PDT) From: John Baldwin To: Andrew Gallatin Subject: RE: Wow, have I got a stack for you! Cc: alfred@FreeBSD.org, freebsd-alpha@FreeBSD.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 07-Jun-01 Andrew Gallatin wrote: > > > panic: blockable sleep lock (sleep mutex) Giant @ ../../vm/vm_fault.c:213 > cpuid = 0; panic > Stopped at Debugger+0x34: zapnot v0,#0xf,a0 > db> tr > Debugger() at Debugger+0x34 > panic() at panic+0x178 > witness_lock() at witness_lock+0x240 > vm_fault() at vm_fault+0x108 > trap() at trap+0xfc8 > XentMM() at XentMM+0x2c > --- memory management fault (from ipl 7) --- > hardclock() at hardclock+0x308 (kgdb) l *hardclock+0x308 0xfffffc00003b6248 is in hardclock (../../kern/kern_clock.c:213). 213 mtx_lock_spin(&callout_lock); Cute, ok. Is that possibly missing a frame? > handleclock() at handleclock+0x22c > alpha_clock_interrupt() at alpha_clock_interrupt+0x68 > interrupt() at interrupt+0xb8 > XentInt() at XentInt+0x28 > --- interrupt (from ipl 0) --- > siocntxwait() at siocntxwait+0x50 > siocnclose() at siocnclose+0x30 > siocnputc() at siocnputc+0x98 > cnputc() at cnputc+0x4c > putchar() at putchar+0xf4 > kvprintf() at kvprintf+0xcc > printf() at printf+0xac Now this is the first trap with a NULL pointer deref, right? > printtrap() at printtrap+0x100 > trap() at trap+0x1214 > XentMM() at XentMM+0x2c > --- memory management fault --- > vm_fault1() at vm_fault1+0x1d8 (kgdb) l *vm_fault1+0x1d8 0xfffffc00005707f8 is in vm_fault1 (../../vm/vm_object.h:198). 197 mtx_assert(VM_OBJECT_MTX(object), MA_OWNED); 198 object->paging_in_progress += i; Ok, this is the same exact panic I've been getting on the SMP system. The vm_map_lookup() is somehow returning a fs.first_object of NULL. :( Well, possibly. I've got a bunch of extra assertions in my SMP kernel but it hasn't hit them yet. It just had it's own nested panic deal off somewhere else. *sigh* > vm_fault() at vm_fault+0x204 > trap() at trap+0xfc8 > XentMM() at XentMM+0x2c > --- memory management fault --- > pmap_insert_entry() at pmap_insert_entry+0x6c (kgdb) l *pmap_insert_entry+0x6c 0xfffffc00005b532c is in pmap_insert_entry (../../alpha/alpha/pmap.c:1769). 1769 TAILQ_INSERT_TAIL(&m->md.pv_list, pv, pv_list); ? *shrug* -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message