<font face="courier new,monospace">I have not tested this issue for a while now.</font><div><font face="courier new,monospace">I will set up the latest OpenWrt trunk with the old firmware and current b43 driver on a broadcom 5354</font></div>
<div><font face="courier new,monospace">and stress test it over the next few days and report back</font></div><div><font face="courier new,monospace"><br></font></div><div><font face="courier new,monospace">The more recent firmware still crashes with the b43 driver on the broadcom 5354 chip set,</font></div>
<div><font face="courier new,monospace">I tested it last week.</font></div><div><font face="courier new,monospace"><br></font></div><div><font face="courier new,monospace">cheers <br clear="all"></font><font face="'courier new', monospace">----------------------------------------------------------<br>
Chris Martin<br>m: +61 419 812 371<br>----------------------------------------------------------</font><br>
<br><br><div class="gmail_quote">2011/5/30 Rafał Miłecki <span dir="ltr"><<a href="mailto:zajec5@gmail.com">zajec5@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
W dniu 29 maja 2011 16:39 użytkownik Larry Finger<br>
<<a href="mailto:Larry.Finger@lwfinger.net">Larry.Finger@lwfinger.net</a>> napisał:<br>
<div><div></div><div class="h5">> On 05/29/2011 06:35 AM, Rafał Miłecki wrote:<br>
>><br>
>> Hey,<br>
>><br>
>> W dniu 29 maja 2011 13:20 użytkownik Hauke Mehrtens<<a href="mailto:hauke@hauke-m.de">hauke@hauke-m.de</a>><br>
>> napisał:<br>
>>><br>
>>> Hi Rafał,<br>
>>><br>
>>> I got some bug reports [0] in OpenWrt regarding a kernel panic because<br>
>>> of b43. It occurs on BCM5354 devices, when they are in AP mode.<br>
>>><br>
>>> There was also a discussion about this on this mailing list some years<br>
>>> ago. [1]<br>
>>><br>
>>> It happens after some time ( 3h to 2d ) without any load or anything not<br>
>>> normal, in station mode this panic does not occur.<br>
>>> After the error occurred the CPU usage increases to 3.0 - 5.0<br>
>>> Sometimes "b43-phy0 ERROR: MAC suspend failed" is shown in the log<br>
>>> before this panic.<br>
>>><br>
>>> Rafał could you please have a look at the issue?<br>
>>><br>
>>> ------<br>
>>> Hauke<br>
>>><br>
>>> [0]: <a href="https://dev.openwrt.org/ticket/9459" target="_blank">https://dev.openwrt.org/ticket/9459</a><br>
>>> [1]: <a href="http://permalink.gmane.org/gmane.linux.drivers.bcm54xx.devel/10682" target="_blank">http://permalink.gmane.org/gmane.linux.drivers.bcm54xx.devel/10682</a><br>
>>><br>
>>><br>
>>><br>
>>> Kernel panic:<br>
>>><br>
>>> b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)<br>
>>> b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)<br>
>>> ......<br>
>>> b43-phy0 ERROR: DMA RX buffer too small (len: 42390, buffer: 2352,<br>
>>> nr-dropped: 19)<br>
>>> b43-phy0 ERROR: DMA RX buffer too small (len: 25505, buffer: 2352,<br>
>>> nr-dropped: 11)<br>
>>> b43-phy0 ERROR: DMA RX buffer too small (len: 19022, buffer: 2352,<br>
>>> nr-dropped: 9)<br>
>>> b43-phy0 ERROR: DMA RX buffer too small (len: 4189, buffer: 2352,<br>
>>> nr-dropped: 2)<br>
>>> b43-phy0 ERROR: DMA RX buffer too small (len: 37381, buffer: 2352,<br>
>>> nr-dropped: 16)<br>
>>> skb_over_panic: text:80c9a408 len:2378 put:2378 head:80eef000<br>
>>> data:80eef040 tail:0x80eef98a end:0x80eef980 dev:<NULL><br>
>>> Kernel bug detected[#1]:<br>
>>> Cpu 0<br>
>>> $ 0 : 00000000 1000b800 0000007c 00000001<br>
>>> $ 4 : 80293498 000020ed ffffffff 000020ed<br>
>>> $ 8 : 00004000 00000000 00000001 ffffffff<br>
>>> $12 : 0000000f 80253c78 ffffffff 00000000<br>
>>> $16 : 00eef040 0000092c 80eef040 819e0740<br>
>>> $20 : 81b3cb00 0000001e a1b4a1e0 80c9f978<br>
>>> $24 : 00000002 80166250<br>
>>> $28 : 81a46000 81a47db0 00000020 801a3d24<br>
>>> Hi : 00000000<br>
>>> Lo : 00000077<br>
>>> epc : 801a3d24 0x801a3d24<br>
>>> Not tainted<br>
>>> ra : 801a3d24 0x801a3d24<br>
>>> Status: 1000b803 KERNEL EXL IE<br>
>>> Cause : 00800024<br>
>>> PrId : 00029029 (Broadcom BCM3302)<br>
>>> Modules linked in: xt_IMQ nf_nat_tftp nf_conntrack_tftp nf_nat_irc<br>
>>> nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp xt_HL xt_hl xt_MARK ipt_ECN<br>
>>> xt_CLASSIFY xt_time xt_tcpmss xt_statistic xt_mark xt_length ipt_ecn<br>
>>> xt_DSCP xt_dscp xt_string xt_layer7 ipt_MASQUERADE iptable_nat nf_nat<br>
>>> xt_CONNMARK xt_recent xt_helper xt_conntrack xt_connmark xt_connbytes<br>
>>> xt_NOTRACK iptable_raw xt_state nf_conntrack_ipv4 nf_defrag_ipv4<br>
>>> nf_conntrack pppoe pppox ipt_REJECT xt_TCPMSS ipt_LOG xt_comment<br>
>>> xt_multiport xt_mac xt_limit iptable_mangle iptable_filter ip_tables<br>
>>> xt_tcpudp x_tables ppp_async ppp_generic slhc b43legacy sch_red b43<br>
>>> sch_sfq sch_hfsc cls_fw imq mac80211 ts_fsm ts_bm ts_kmp crc_ccitt<br>
>>> cfg80211 compat_firmware_class compat arc4 aes_generic deflate ecb cbc<br>
>>> switch_robo switch_core diag<br>
>>> Process irq/5-b43 (pid: 895, threadinfo=81a46000, task=81ab45d0,<br>
>>> tls=00000000)<br>
>>> Stack : 00000000 80c9a408 0000094a 0000094a 80eef000 80eef040 80eef98a<br>
>>> 80eef980<br>
>>> 8026e09c 0000001e a1b4a1e0 80c9a408 80c17ad4 00ff0000 000000e6<br>
>>> 00010000<br>
>>> 819e2400 819e2400 80d31568 00ff0000 80c9f978 00010000 00010000<br>
>>> 819e2400<br>
>>> 00008000 00010000 81b3ca24 00010000 802ce8c0 00000000 802953b4<br>
>>> 80c872cc<br>
>>> 00010000 802ce8c0 80292f28 8001ce0c 819ea138 819ea138 80292f28<br>
>>> 8001eba0<br>
>>> ...<br>
>>> Call Trace:[<80c9a408>] 0x80c9a408<br>
>>> [<80c9a408>] 0x80c9a408<br>
>>> [<80c872cc>] 0x80c872cc<br>
>>> [<8001ce0c>] 0x8001ce0c<br>
>>> [<8001eba0>] 0x8001eba0<br>
>>> [<8001cef8>] 0x8001cef8<br>
>>> [<80190bf4>] 0x80190bf4<br>
>>> [<80c87424>] 0x80c87424<br>
>>> [<80057480>] 0x80057480<br>
>>> [<8000af98>] 0x8000af98<br>
>>> [<80057304>] 0x80057304<br>
>>> [<80057304>] 0x80057304<br>
>>> [<8003db30>] 0x8003db30<br>
>>> [<8000f86c>] 0x8000f86c<br>
>>> [<8003dab4>] 0x8003dab4<br>
>>> [<8000f85c>] 0x8000f85c<br>
>>><br>
>>><br>
>>> Code: afab001c 0c0028ff afa20020<0200000d> 08068f4a 00000000<br>
>>> 8fbf002c 01201021 03e00008<br>
>>> Disabling lock debugging due to kernel taint<br>
>>> exiting task "irq/5-b43" (895) is an active IRQ thread (irq 5)<br>
>>><br>
>>><br>
>>> Call Trace from an other report:<br>
>>><br>
>>> Jan 1 04:03:40 OpenWrt user.warn kernel: Call Trace:<br>
>>> Jan 1 04:03:40 OpenWrt user.warn kernel: [<8019bc10>] skb_put+0x74/0x90<br>
>>> Jan 1 04:03:40 OpenWrt user.warn kernel: [<8051a3e8>]<br>
>>> b43_dma_rx+0x294/0x378 [b43]<br>
>>> Jan 1 04:03:40 OpenWrt user.warn kernel: [<805072b8>]<br>
>>> b43_controller_restart+0x7a8/0x97c [b43]<br>
>>> Jan 1 04:03:40 OpenWrt user.warn kernel: Code: afab001c 0c0028c2<br>
>>> afa20020<0200000d> 08066f05 00000000 8fbf002c 01201021 03e00008<br>
>>> Jan 1 04:03:40 OpenWrt user.warn kernel: Disabling lock debugging due<br>
>>> to kernel taint<br>
>>> Jan 1 04:03:40 OpenWrt user.err kernel: exiting task "irq/5-b43" (763)<br>
>>> is an active IRQ thread (irq 5)<br>
>><br>
>> This sounds like duplicate of:<br>
>> <a href="https://bugzilla.kernel.org/show_bug.cgi?id=32042" target="_blank">https://bugzilla.kernel.org/show_bug.cgi?id=32042</a><br>
>><br>
>> Larry fixed this issue, also CC-ing stable@kernel. I believe updating<br>
>> kernel or applying c85ce65ecac078ab1a1835c87c4a6319cf74660a manually<br>
>> will help :)<br>
><br>
> This may not be the same issue as the buffer lengths in the panic message<br>
> are very large.<br>
><br>
> For the record, John Linville fixed that issue.<br>
<br>
</div></div>You're right, sorry for the false reference to fix.<br>
<br>
This is just another issue with firmware on BCM5354.<br>
<br>
--<br>
<font color="#888888">Rafał<br>
</font><div><div></div><div class="h5"><br>
_______________________________________________<br>
b43-dev mailing list<br>
<a href="mailto:b43-dev@lists.infradead.org">b43-dev@lists.infradead.org</a><br>
<a href="http://lists.infradead.org/mailman/listinfo/b43-dev" target="_blank">http://lists.infradead.org/mailman/listinfo/b43-dev</a><br>
</div></div></blockquote></div><br></div>