On Friday 19 February 2010 16:40:40 Larry Finger wrote:
[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
On Friday 19 February 2010 16:40:40 Larry Finger wrote:
[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
On Friday 19 February 2010 21:28:01 Stefan Wahren wrote:
@Michael: Okay, is there any method to get more reliable information
about the kernel panic (strace, ...) or a idea to faster reproduce the
kernel panic than waiting?
I think the backtrace is pretty good as-is, if you ignore the
I think the backtrace is pretty good as-is, if you ignore the
controller_restart
line. It's pretty obvious that this is an skb overflow panic caused by a
received packet. There's nothing in the trace that falsifies this, as far as I
can see.
So what if you set up another device in monitor
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
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
