From owner-freebsd-current@FreeBSD.ORG Tue Jan 20 11:12:57 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 C400016A4CE for ; Tue, 20 Jan 2004 11:12:57 -0800 (PST) Received: from hak.cnd.mcgill.ca (hak.cnd.mcgill.ca [132.216.11.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id 66C9B43D46 for ; Tue, 20 Jan 2004 11:12:56 -0800 (PST) (envelope-from mat@hak.cnd.mcgill.ca) Received: from hak.cnd.mcgill.ca (localhost [127.0.0.1]) by hak.cnd.mcgill.ca (8.12.9/8.12.8) with ESMTP id i0KJ9ESP060470; Tue, 20 Jan 2004 14:09:14 -0500 (EST) (envelope-from mat@hak.cnd.mcgill.ca) Received: (from mat@localhost) by hak.cnd.mcgill.ca (8.12.9/8.12.8/Submit) id i0KJ9EhZ060469; Tue, 20 Jan 2004 14:09:14 -0500 (EST) Date: Tue, 20 Jan 2004 14:09:13 -0500 From: Mathew Kanner To: Eirik Oeverby Message-ID: <20040120190913.GI41883@cnd.mcgill.ca> References: <1074595017.1129.3.camel@eirik.unicore.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1074595017.1129.3.camel@eirik.unicore.no> User-Agent: Mutt/1.4.1i Organization: I speak for myself, operating in Montreal, CANADA X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.62 X-Spam-Checker-Version: SpamAssassin 2.62 (2004-01-11) on hak.cnd.mcgill.ca cc: current@freebsd.org Subject: Re: Panic with snd_cmi and snd_emu10k1 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, 20 Jan 2004 19:12:57 -0000 On Jan 20, Eirik Oeverby wrote: > Hi! > > I think I just made a mistake, checking out and compiling a > soon-after-release -CURRENT sourcetree .. With the result that both > sounddrivers I try to load cause a panic. Since I'm on my workstation > right now, I'm not able to do any kind of debugging, but I will see if > the problem is reproducable on my laptop at home. > > In the meantime, has anyone else seen this, and is this a known problem? Last night I fixed a panic that only happens when you kldload a sound driver after boot. The panic was introduced only recently (past few days). > Any hints as to what I should do next (apart from rolling back to > 5.2-RELEASE or waiting for the tree to fix itself)? Update to -current and if it panics again, send the message and a traceback. Without the panic message it's hard to even begin. --Mat -- If you optimize everything, you will always be unhappy. - Don Knuth