| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 21 May 2012 22:39:10 -0500 From: Larry Finger <Larry.Finger@...inger.net> To: wireless <linux-wireless@...r.kernel.org>, netdev <netdev@...r.kernel.org> Subject: Network kernel panics with wireless-testing 3.4-rc7 I am getting kernel panics on one of my boxes from the b43legacy driver due to a "Fatal exception in interrupt". This particular one happened 50K seconds after bootup, but it has happened nearly as soon as the network connection was completed. The hand-transcribed traceback is as follows: __nefif_schedule+0x13/0xa0 ieee80211_propagate_queue_wake+0x166/0x1c0 __ieee80211_wake_queue+0x13b/0x2d0 ? __ieee80211_wake_queue++0xc0/0x2d0 ieee80211_wake_queue_by_reason+0x45/0x70 ieee80211_wake_queue+0xb/0x10 b43legacy_dma_handle_txstatus+0x3f9/0x4b0 ? _raw_spin_unlock+0x26/0x40 b43legacy_handle_txstatus+0x64/0x90 b43legacy_handle_hwtxstatus+0x66/0x70 b43legacy_dma_rx+0x354/0x610 The offsets are for an x86_64 architecture. These crashes never happen when I use a USB device running the rtl8187 driver, thus it appears to arise in b43legacy. Any suggestions on what might cause the problem would be helpful. Sorry I don't have the register dumps, etc. The code dump at the point of the crash is as follows: ec 10 4c 89 65 f8 48 89 5d f0 49 89 fc <3c> 0f ba af 80 00 00 00 00 Larry -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists