From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 14:46:21 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 59FD616A4CE for ; Sun, 4 Jan 2004 14:46:21 -0800 (PST) Received: from email02.aon.at (WARSL402PIP7.highway.telekom.at [195.3.96.94]) by mx1.FreeBSD.org (Postfix) with SMTP id 7AFCD43D45 for ; Sun, 4 Jan 2004 14:46:18 -0800 (PST) (envelope-from shoesoft@gmx.net) Received: (qmail 395536 invoked from network); 4 Jan 2004 22:46:17 -0000 Received: from m093p028.dipool.highway.telekom.at (HELO ?62.46.1.156?) ([62.46.1.156]) (envelope-sender ) by qmail2rs.highway.telekom.at (qmail-ldap-1.03) with SMTP for ; 4 Jan 2004 22:46:17 -0000 From: Stefan Ehmann To: Don Lewis In-Reply-To: <200401042224.i04MOP7E009799@gw.catspoiler.org> References: <200401042224.i04MOP7E009799@gw.catspoiler.org> Content-Type: text/plain Message-Id: <1073256379.801.24.camel@shoeserv.freebsd> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Sun, 04 Jan 2004 23:46:20 +0100 Content-Transfer-Encoding: 7bit cc: current@FreeBSD.org Subject: Re: page fault panic tracked down (selwakeuppri()) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Jan 2004 22:46:21 -0000 On Sun, 2004-01-04 at 23:24, Don Lewis wrote: > On 4 Jan, Stefan Ehmann wrote: > > I took out the debug options because it was just too slow. Put back > > INVARIANTS (but no WITNESS) now and speed is nice again. > > This problem is more likely to be caught by INVARIANTS than WITNESS. > > > Applied your suggested changes which resulted in a panic. No > > assertations were triggered though. > > Bummer! Updated to plain (= no patches/hacks) again, also put in the DEBUG_VFS_LOCKS. For the first time I got a backtrace that ended in the soundcard module - So maybe this is the right direction (on the other hand this might be some newly introduced error) panic: bad bufsize #0 doadump () at /usr/src/sys/kern/kern_shutdown.c:240 #1 0xc04e5198 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:372 #2 0xc04e5527 in panic () at /usr/src/sys/kern/kern_shutdown.c:550 #3 0xc07ec648 in feed_vchan_s16 () from /boot/kernel/snd_pcm.ko #4 0xc07e2c6d in sndbuf_feed () from /boot/kernel/snd_pcm.ko #5 0xc07e3225 in chn_wrfeed () from /boot/kernel/snd_pcm.ko #6 0xc07e327c in chn_wrintr () from /boot/kernel/snd_pcm.ko #7 0xc07e3990 in chn_intr () from /boot/kernel/snd_pcm.ko #8 0xc07fca2f in csa_intr () from /boot/kernel/snd_csa.ko #9 0xc07fb724 in csa_intr () from /boot/kernel/snd_csa.ko #10 0xc04d1692 in ithread_loop (arg=0xc1737b00) at /usr/src/sys/kern/kern_intr.c:544 #11 0xc04d0684 in fork_exit (callout=0xc04d1500 , arg=0x0, frame=0x0) at /usr/src/sys/kern/kern_fork.c:796 Nearly all other panics (I put a collection of ~20 backtraces on http://stud4.tuwien.ac.at/~e0125637/fbsd/ if it's of any interest) ended up in file system code.