From owner-freebsd-current@FreeBSD.ORG Mon Jan 5 18:06:09 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 D2BF116A4F7 for ; Mon, 5 Jan 2004 18:06:09 -0800 (PST) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id B2EA643D2F for ; Mon, 5 Jan 2004 18:06:08 -0800 (PST) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.9p2/8.12.9) with ESMTP id i062607E012697; Mon, 5 Jan 2004 18:06:04 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <200401060206.i062607E012697@gw.catspoiler.org> Date: Mon, 5 Jan 2004 18:06:00 -0800 (PST) From: Don Lewis To: shoesoft@gmx.net In-Reply-To: <1073346565.2948.21.camel@shoeserv.freebsd> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii 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: Tue, 06 Jan 2004 02:06:10 -0000 On 6 Jan, Stefan Ehmann wrote: > On Mon, 2004-01-05 at 11:36, Bruce Evans wrote: >> On Sun, 4 Jan 2004, Stefan Ehmann wrote: >> >> > 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) >> The sound driver is in modules. Have you ruled out having an inconsistent >> module. > > For some reason gdb loaded debugging information for all modules except > bktr, snd_pcm and snd_csa. (I always build kernel with > MODULES_OVERRIDE). > > To work around this problem I compiled a kernel with static pcm. That > would also rule out an inconsistent module. The system is up now 6 hours > and still no panic. If this panic will only happen with csa/pcm as > module I'll be even more puzzled. > > I'm also still not sure why I got three "bad bufsize" panics in a row > all of the sudden instead of page faults. (Most of the previous kernels > were built without INVARIANTS - but at least some with). The parameters passed to feed_vchan_16() might be bad in such a way that the KASSERT is happy, but the heap still gets trashed. If you can't get the KASSERT failure without this code being in a module (or get gdb to debug the module), it might be interesting to change this KASSERT into an "if" test that prints the parameters and anything else of interest and then calls panic().