From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 31 23:07:01 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B67516A4CE for ; Thu, 31 Mar 2005 23:07:01 +0000 (GMT) Received: from mail22.sea5.speakeasy.net (mail22.sea5.speakeasy.net [69.17.117.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2AABF43D45 for ; Thu, 31 Mar 2005 23:07:01 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 14773 invoked from network); 31 Mar 2005 23:07:01 -0000 Received: from server.baldwin.cx ([216.27.160.63]) (envelope-sender )AES256-SHA encrypted SMTP for ; 31 Mar 2005 23:06:59 -0000 Received: from [10.50.41.231] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j2VN6iQU028069; Thu, 31 Mar 2005 18:06:54 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-hackers@FreeBSD.org Date: Thu, 31 Mar 2005 17:16:52 -0500 User-Agent: KMail/1.6.2 References: <20050331203826.GA31110@siue.dnsalias.net> In-Reply-To: <20050331203826.GA31110@siue.dnsalias.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Message-Id: <200503311716.52034.jhb@FreeBSD.org> X-Spam-Status: No, score=-102.8 required=4.2 tests=ALL_TRUSTED, USER_IN_WHITELIST autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx cc: William Michael Grim Subject: Re: 4BSD Scheduler Problem on 5.3 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 23:07:01 -0000 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 <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org