On 02/19/2010 12:47 AM, Stefan Wahren wrote:
> Hi,
> 
> it's me again. The problem still exists. I had no idea to get it better
> reproduceable. Please tell me what information do you need to fix it.
> 
> Thanks in advice.
> 
> Stefan
> 
> Stefan Wahren schrieb:
>> Hi,
>>
>> i'm using OpenWRT on an ASUS WL-500gP V2 with the built-in Broadcom
>> BCM3302. After a few hours the b43 driver crashes with a skb_over_panic
>> and i need to reboot the device. The crash happend also, if there is no
>> traffic over the wireless interface. The wireless interface is
>> configured in AP mode and the encryption psk2.
>>
>> The used kernel (Linux OpenWrt 2.6.30.10 #1 Tue Feb 2 01:15:42 CET 2010
>> mips GNU/Linux) throws the following output:
>>
>> skb_over_panic: text:80c9a8e4 len:2374 put:2374 head:80e79000
>> data:80e79040 tail:0x80e79986 end:0x80e79980 dev:<NULL>
>> Kernel bug detected[#1]:
>> Cpu 0
>> $ 0   : 00000000 1000f800 00000079 00000001
>> $ 4   : 802880c0 0000271f ffffffff 0000271f
>> $ 8   : 00004000 00000000 802959b0 00000001
>> $12   : 0000000f 8022a1d0 ffffffff 7ffb537b
>> $16   : 00e79040 80e79040 00000928 80e9a9a0
>> $20   : 80d84c80 00000019 a0df7190 80ca1518
>> $24   : 00000002 80151108
>> $28   : 80ea0000 80ea1e60 0000001b 8018c2d4
>> Hi    : 00000000
>> Lo    : 00000077
>> epc   : 8018c2d4 skb_put+0x74/0x90
>>     Not tainted
>> ra    : 8018c2d4 skb_put+0x74/0x90
>> Status: 1000f803    KERNEL EXL IE
>> Cause : 00800024
>> PrId  : 00029029 (Broadcom BCM3302)
>> Modules linked in: pl2303 option ftdi_sio usb_storage usbserial ohci_hcd
>> nf_nat_
>> tftp nf_conntrack_tftp nf_nat_irc nf_conntrack_irc nf_nat_ftp
>> nf_conntrack_ftp i
>> pt_MASQUERADE iptable_nat nf_nat xt_NOTRACK iptable_raw xt_state
>> nf_conntrack_ip
>> v4 nf_defrag_ipv4 nf_conntrack ehci_hcd sd_mod pppoe pppox ipt_REJECT
>> xt_TCPMSS
>>           ipt_LOG xt_multiport xt_mac xt_limit iptable_mangle
>> iptable_filter ip_tables xt_
>>                             tcpudp x_tables ext2 ext3 jbd tun ppp_async
>> ppp_generic slhc vfat fat b43 nls_ut
>>                                     f8 nls_iso8859_15 nls_iso8859_1
>> nls_cp850 nls_cp437 usbcore scsi_mod nls_base ma
>>                                                 c80211 cfg80211
>> compat_firmware_class compat crc_ccitt arc4 aes_generic deflate
>>                                                                 ecb cbc
>> switch_robo switch_core diag
>> Process compirq/5-b43 (pid: 812, threadinfo=80ea0000, task=81f19188,
>> tls=0000000
>>            0)
>> Stack : 00000000 80c9a8e4 00000946 00000946 80e79000 80e79040 80e79986
>> 80e79980
>>         80266f84 80d84c80 00000019 80c9a8e4 80287b88 80286170 1000f800
>> ffff00fe
>>         80ea1fe0 0000f800 80d92d2c 80284000 80ca1518 7f816db4 00010000
>> 80c7f400
>>         00008000 00010000 fffffffc 802c7860 00010000 fffffffe efffffff
>> 80c87420
>>         81f19188 80c80000 80e9ee08 8001c63c 80ea0000 80ea1f18 8021db88
>> 00000000
>>         ...
>> Call Trace:
>> [<8018c2d4>] skb_put+0x74/0x90
>> [<80c9a8e4>] b43_dma_rx+0x338/0x444 [b43]
>> [<80c87420>] b43_controller_restart+0x7a0/0x974 [b43]
>>

The traceback indicates a controller restart. Does your log show any reason for
that event? That may help me understand why skb->tail is past skb->end.

Larry

_______________________________________________
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Reply via email to