From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 24 12:18:35 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C7976162; Wed, 24 Oct 2012 12:18:35 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 6181C8FC14; Wed, 24 Oct 2012 12:18:35 +0000 (UTC) Received: by mail-vb0-f54.google.com with SMTP id v11so552379vbm.13 for ; Wed, 24 Oct 2012 05:18:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=aBduQpOTp/NLh9Zf9lyofhHiqlJXuprHEsgZSkp1s3k=; b=P6h1bjch8JU00xUrIEMzQ84GqRUwkTC5N3D4Ey38gV4DCWASbAddAa2R2TICcZJT8P TUpr/DrXbLDRrYUnWjT4KfmUOhspzMv1M0NyRslp7Mz5auarisNlHmTx/LuHwSwTxpFU lfSYYivV/fCXPISB2jp37kXWwTTcPJUyoQhLO4EjpzhHncIBlkxoO/CWlmxCLqXJRzEP Yhll7h3AtRmmWPNtZvC3Vj5fi2HDgo64Ty8MkjHEPxhsXkW7sKaR9BQQ24hG8rTNOERu dvw5WrZ9tvdSAAysmG0XysJZoHqUYhDSPYwD9/iguUCU5IiefRp5ebETUWI1wDf+BIHd suJA== MIME-Version: 1.0 Received: by 10.58.247.132 with SMTP id ye4mr28982588vec.9.1351081114762; Wed, 24 Oct 2012 05:18:34 -0700 (PDT) Received: by 10.58.213.74 with HTTP; Wed, 24 Oct 2012 05:18:34 -0700 (PDT) In-Reply-To: References: <20121023230652.206fb4ea@narn.knownspace> Date: Wed, 24 Oct 2012 08:18:34 -0400 Message-ID: Subject: Re: data storage interrupt with if_ath(4) on PowerPC From: Justin Hibbits To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Oct 2012 12:18:35 -0000 On Tue, Oct 23, 2012 at 11:37 PM, Adrian Chadd wrote: > On 23 October 2012 20:06, Justin Hibbits wrote: > > With an Atheros 5416 card from Adrian Chadd in my PowerBook G4, I get a > > Data Storage Interrupt after a few minutes. It's pretty reproducible: > > > > * load if_ath/if_ath_pci > > * ifconfig wlan0 create wlandev ath0 > > * ifconfig wlan0 up > > * ifconfig wlan0 bgscan (fails with "Operation not supported") > > * ifconfig wlan0 list scan > > ... wait ... > > * ifconfig wland0 list scan (another just for good measure) > > ... wait ... > > > > After a few minutes it kernel panics. > > Ew! > Ew indeed. > > > I've attached the dcons ddb session output. Quick synopsis: It > > crashes in memcpy() crossing a page boundary. Backtrace: > > Is that actually a bad thing? What's a "data storage interrupt" ? > In this case it is a bad thing, otherwise it wouldn't panic :). Think of it as the equivalent of an x86 'page fault in kernel mode'. > > Adrian > > > fatal kernel trap: > > > > exception = 0x300 (data storage interrupt) > > virtual address = 0xd1b72000 > > srr0 = 0x5d44b4 > > srr1 = 0x9032 > > lr = 0xd1ab0fa4 > > curthread = 0x189fbc0 > > pid = 0, comm = ath0 net80211 taskq > > > > Tracing pid 0 tid 100075 td 0x189fbc0 > > 0xe21139f4: at m_pkthdr_init+0x5c > > 0xe2113a14: at ieee80211_send_probereq+0x14c > > 0xe2113a74: at ieee80211_probe_curchan+0x11c > > 0xe2113aa4: at scan_curchan+0x7c > > 0xe2113ac4: at scan_task+0x29c > > 0xe2113b14: at taskqueue_run_locked+0xd4 > > 0xe2113b44: at taskqueue_thread_loop+0x6c > > 0xe2113b64: at fork_exit+0x88 > > 0xe2113b84: at fork_trampoline+0xc > > > > The m_pkthdr_init in the backtrace is misleading, I think. > > > > I can provide any more data that's needed. > > > > > > - Justin > - Justin