From owner-freebsd-stable@FreeBSD.ORG Fri Jan 14 01:10:45 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F3C6A16A4CE for ; Fri, 14 Jan 2005 01:10:44 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id D208E43D39 for ; Fri, 14 Jan 2005 01:10:44 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 9A05772DD4; Thu, 13 Jan 2005 17:10:44 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 943DC72DCB; Thu, 13 Jan 2005 17:10:44 -0800 (PST) Date: Thu, 13 Jan 2005 17:10:44 -0800 (PST) From: Doug White To: Mitch Parks In-Reply-To: <20050104211020.M852@kuoi.asui.uidaho.edu> Message-ID: <20050113170611.V13904@carver.gumbysoft.com> References: <20050104211020.M852@kuoi.asui.uidaho.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org Subject: Re: unstable 5.3 boxes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2005 01:10:45 -0000 On Wed, 5 Jan 2005, Mitch Parks wrote: > It seems both my test and production boxes are not stable with 5.3-Release. > I'm hoping for some insight in how to make at least the production box > not crash. [...] > #7 0xe93a0018 in ?? () > #8 0xc0580010 in kvprintf (fmt=0xc7b04c60 "?6w?\v6t?\v6t?", func=0x59, > arg=0xe93ad9bc, radix=-1067875706, ap=0xc3839674 "\001") > at /usr/src/sys/kern/subr_prf.c:643 > #9 0xc058940a in selwakeuppri (sip=0x0, pri=0) > at /usr/src/sys/kern/sys_generic.c:1096 > #10 0xc0598286 in ttwakeup (tp=0xc05842e8) at /usr/src/sys/kern/tty.c:2366 Something weird is going on here. selwakeuppri() doesn't call any of the printf functions -- it calls doselwakeup() and thats it. I don't see anything in doselwakeup() that would call a printf function offhand. The null arguments in frame 9 are also odd and would certainly trip up doselwakeup() since it immediately dereferences sid. This was opening a serial device it looks like. Do you have syslog set to output to a serial terminal, or have getty enabled on ttyd*, or something plugged into any serial port, or something of that nature? The later call to ttwakeup() occurs in a block where carrier has been raised. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org