Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 31 Mar 2005 17:16:52 -0500
From:      John Baldwin <jhb@FreeBSD.org>
To:        freebsd-hackers@FreeBSD.org
Cc:        William Michael Grim <wgrim@siue.edu>
Subject:   Re: 4BSD Scheduler Problem on 5.3
Message-ID:  <200503311716.52034.jhb@FreeBSD.org>
In-Reply-To: <20050331203826.GA31110@siue.dnsalias.net>
References:  <20050331203826.GA31110@siue.dnsalias.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 31 March 2005 03:38 pm, William Michael Grim wrote:
> Hello.
>
> I keep having kernel panics every couple weeks on my system.  It occurs in
> the sched_switch() function.  There are several other statements in the
> backtrace involving "??"; what are those?
>
> I have attached the dump output and system info to this email.  Any
> feedback would be helpful.
>
> Thanks so much for your help.

The real trace ends with Xint0x80_syscall().  The rest after that is garbage 
memory.  Your real problem is in exit1() or ttywakeup().  Since ttywakeup() 
doesn't call exit1() (AFAIK), the exit1() frame is probably bogus (gdb 
doesn't grok trapframes maybe?) and the real bug is a NULL pointer deref in 
ttywakeup().  Perhaps it's a bug in the ptc driver?  (ptcopen is in the 
trace).  What is the ptc driver anyway?

-- 
John Baldwin <jhb@FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve"  =  http://www.FreeBSD.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200503311716.52034.jhb>