Subject: Re: panic: setrunqueue
To: None <email@example.com>
From: Julio M. Merino Vidal <firstname.lastname@example.org>
Date: 02/13/2006 14:08:32
On Monday 13 February 2006 11:53, Pavel Cahyna wrote:
> On Sun, Feb 12, 2006 at 10:51:10PM +0100, Julio M. Merino Vidal wrote:
> Setrunqueue is not the right panic message - this looks like a second
> panic when ddb attempted to sync filesystems. Look at the backtrace, how
> ddb was called recursively.
Yes, that's true. The first 'sync' did indeed fail. But as I was under
X (as usual) I couldn't see the original panic message...
> The real panic happens here. What is the original panic message?
> > #35 0xc021e4b6 in uvmspace_free (vm=0xcc864d28)
> > at /usr/src/sys/uvm/uvm_map.c:3802
> > #36 0xc024a3df in exit1 (l=0xcca0b9d4, rv=0)
> > at /usr/src/sys/kern/kern_exit.c:341
> > #37 0xc024a19b in sys_exit (l=0xcca0b9d4, v=0xcba2ff64,
> > retval=0xcba2ff5c) at /usr/src/sys/kern/kern_exit.c:176
> > #38 0xc02cd94b in syscall_plain (frame=0xcba2ffa8)
> > at /usr/src/sys/arch/i386/i386/syscall.c:160
Julio M. Merino Vidal <email@example.com>
The Julipedia - http://julipedia.blogspot.com/