From owner-freebsd-current Wed May 23 18:10:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.hub.org (SHW39-29.accesscable.net [24.138.39.29]) by hub.freebsd.org (Postfix) with ESMTP id 90D1537B423; Wed, 23 May 2001 18:10:10 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by mobile.hub.org (8.11.3/8.11.1) with ESMTP id f4O1A9738862; Wed, 23 May 2001 22:10:09 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: mobile.hub.org: scrappy owned process doing -bs Date: Wed, 23 May 2001 22:10:09 -0300 (ADT) From: The Hermit Hacker To: John Baldwin Cc: Subject: RE: Tonights panic: free_newdirblk+0x73: movl %eax,0x10(%e In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Okay, running a new buildworld right now ... give it a half hour or so :) On Wed, 23 May 2001, John Baldwin wrote: > Looks like %edx is 0x2 then. In other post, the faulting va was 0x11 > with the same instruction, meaning that %edx is 0x1. So it looks like > it isn't a NULL pointer dereference. It may be related to the VM > stuff in that it may be that a buffer is being manipulated somewhere > without Giant being held while being manipulated with Giant being held > somewhere else? Or it could be a softupdates bug. :-P Is this an SMP > machine? Ah, yes it is. Next time you see this, can you display > 'show pcpu' for each CPU (show pcpu does the current cpu, show cpu > displays the info on CPU ). Okay, this is no problem ... > Also, can you get a backtrace of each process that is running? trace > on x86 can take the pid of a process to get a backtrace of as a > parameter, and the show pcpu commands should show you what process was > executing on the other CPU (including its pid). Oops ... neat, now it just locked up solid and ctl-alt-esc doesn't even get me to debugger :( ah well, will try and recreate the error and report back ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message