From owner-freebsd-bugs@FreeBSD.ORG Mon Feb 16 04:56:59 2004 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35E4316A4CF for ; Mon, 16 Feb 2004 04:56:59 -0800 (PST) Received: from rdsnet.ro (smtp.rdsnet.ro [62.231.74.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65CA243D2F for ; Mon, 16 Feb 2004 04:56:58 -0800 (PST) (envelope-from itetcu@apropo.ro) Received: (qmail 18706 invoked from network); 16 Feb 2004 12:56:57 -0000 Received: from unknown (HELO it.buh.cameradicommercio.ro) (81.196.25.19) by mail.rdsnet.ro with SMTP; 16 Feb 2004 12:56:57 -0000 Received: from it.buh.cameradicommercio.ro (localhost.buh.cameradicommercio.ro [127.0.0.1]) by it.buh.cameradicommercio.ro (Postfix) with SMTP id 49BAD12A; Mon, 16 Feb 2004 14:58:39 +0200 (EET) Date: Mon, 16 Feb 2004 14:58:38 +0200 From: Ion-Mihai Tetcu To: Matthew Fremont Message-Id: <20040216145838.498a0ffc@it.buh.cameradicommercio.ro> In-Reply-To: <20040216010301.75740.qmail@web20024.mail.yahoo.com> References: <20040216010301.75740.qmail@web20024.mail.yahoo.com> X-Mailer: Sylpheed version 0.9.8claws (GTK+ 1.2.10; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-bugs@freebsd.org Subject: Re: 5.2-RELEASE kernel panic (page fault) in if_ath.ko X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2004 12:56:59 -0000 On Sun, 15 Feb 2004 17:03:01 -0800 (PST) Matthew Fremont wrote: > In the last 24hrs I've experienced several page fault > panics on my 5.2-RELEASE system. Panics appear to be > related to Samba and NFS traffic on a NetGear WG311 > NIC. The NIC is supported by the ath(4) driver, and a > backtrace of the crash dump suggest that the page > fault is triggered in the if_ath.ko module. > > My questions are: > > 1. Should I report this by filing a PR? As you run the -RELEASE of the development, perhaps it would be better to: 1. See the commit logs for ath, somethings might be change since 5.2.R (and I think it has) 2. Post on current with details. 3. After this, fill the PR. Also make sure you don't have any optimising options in /etc/make.conf > 2. Is "kern" the appropriate category? Yes. > 3. What information concerning my system configuration > should be included in the PR? hard to say, as I don't know what exactly is happening (e.g. panic message, etc.) dmesg of an boot -v. Ath chip model/version. pciconf -l > 4. Would it be helpful for me to try to compile a > debug version of if_ath.ko and attempt to reproduce > the problem? ANY information you can provide to a developer/maintainer is useful, as he can narrow down his search. Saving his time on searching means he has more time to debug your problem or do other work. If you don't have a debug kernel, recompile with debug options. Provide a backtrace, etc. -- IOnut Unregistered ;) FreeBSD user