From owner-freebsd-current@FreeBSD.ORG Fri Jul 18 10:36:18 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 56997106564A for ; Fri, 18 Jul 2008 10:36:18 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.159]) by mx1.freebsd.org (Postfix) with ESMTP id C93A98FC14 for ; Fri, 18 Jul 2008 10:36:17 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so170336fgb.35 for ; Fri, 18 Jul 2008 03:36:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=JOuhRR3TvNkvtLnQljSBc7ja1EgLwyWzWwQ7We+2pIw=; b=vQ8TnXDH+CayNt0HHBWNzHwB2pBZHtW1FzGB0FdPTjG0C+WlHOxeuiQsr3KA+PParz /IN2r3AqFDJXW7NRlW88106ltHMjrqwspL/Faip6u2LX3TgV36HR0DgfaGahFS4hNeRE 5MnmRnrsf3Ky/37C2MjP6xy/wnMDCiwQkKFV4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=ldBHBdxif18q6GXUqvd9apgU5AIEYkQDfu9jAhBHoJ6Oma8jg6Ue5LznTvukrzyOqx 9Or5CKRV0kIo+n0z0TxKczHetibFNVYq1W0LGvzIA+g0hbfT8k19PzBy6xoHLSXo3ZJk u4ZwWGxjbQ+0TTyDK3T+o9BU1udb1V3xW1/bg= Received: by 10.86.98.14 with SMTP id v14mr64142fgb.74.1216377376614; Fri, 18 Jul 2008 03:36:16 -0700 (PDT) Received: by 10.86.51.1 with HTTP; Fri, 18 Jul 2008 03:36:16 -0700 (PDT) Message-ID: <7d6fde3d0807180336h61f13a73pcc433be16a732c7e@mail.gmail.com> Date: Fri, 18 Jul 2008 03:36:16 -0700 From: "Garrett Cooper" To: "Edward Ruggeri" In-Reply-To: <919383240807172100j35e1c796q513fa34d83f8e8e0@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <919383240807172100j35e1c796q513fa34d83f8e8e0@mail.gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: 7.0 CURRENT kernel's ath driver causes page fault, kernel panic (debugging kernel) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Fri, 18 Jul 2008 10:36:18 -0000 On Thu, Jul 17, 2008 at 9:00 PM, Edward Ruggeri wrote: > Hi, > > I am getting a kernel panic (page fault) caused by the FreeBSD > kernel's ath driver shortly after I begin using the internet. I use > FreeBSD 7.0 CURRENT. I used cvs a few days ago to update the source > tree (7/10/08) and rebuilt the world as well as the kernel (just got a > brand new computer). There is very little software installed (ports > only, also built 7/10/08), and no data. But let me describe the > configuration and problem. > > I have recently purchased a Lenovo ThinkPad, with a ThinkPad 11a/b/g > Wi-Fi wireless LAN Mini-PCIe card (Lenovo part #41W1685). My Lenovo > representative claims this uses a Atheros Ar5006ex chipset (she's not > an expert, though), but FreeBSD's dmesg detects an Atheros 5212 > chipset. The Linux oriented thinkwiki.org claims this card may use > either chipset. I don't know who to trust; maybe someone knows the > answer, but Google hasn't seemed to clear things up. In particular, > from dmesg: Some notes: 1. *blinks*... I hope you mean 8-CURRENT, not 7-CURRENT. 7 hasn't been CURRENT for some months now (~6 months IIRC). 2. pciconf -lv might help with the PCI ID info. Then someone might be able to tie your card back to the appropriate chipset. 3. KDB, DDB, WITNESS and INVARIANTS support compiled into the kernel would be extremely helpful, if not required to debug your issue. As for the actual debug process, there's a spot in the dev handbook about it (http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html), but when I tried debugging my issue with NTFS and SMB I didn't really find it helpful to be honest... You may also have to compile without SMP and with the 4BSD scheduler just to see whether or not it's an issue reproducible with the ULE scheduler, the driver, or something else... Hopefully this gets you started on the right path... -Garrett