Topic: kernel panic when loading bcm43xx driver

The content of this topic has been archived on 12 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Page 1 of 1

Post #1

mangoo

23 Oct 2006, 22:06

When I load the bcm43xx module on ASUS WL-500g deluxe, the kernel panics (kamikaze as of 2006-10-18):

bcm43xx driver
bcm43xx: Chip ID 0x5365, rev 0x1
bcm43xx: Number of cores: 0
bcm43xx: Core 0: ID 0x800, rev 0x5, vendor 0x4243, enabled
bcm43xx: Error: No 80211 core found!
PCI: Fixing up device 0000:01:03.0
Data bus error, epc == c00e99f0, ra == c00e99d8
Oops[#1]:
Cpu 0
$ 0 : 00000000 1000dc00 00000000 c00a4000
$ 4 : c00a4000 00000004 0c080083 00080080
$ 8 : 00000007 00000080 00000004 802c0000
$12 : 802c0000 00000001 7fb04934 203a726f
$16 : 00000000 00000000 00002000 81ac8c28
$20 : 81ac8000 00000000 c00a1000 80280000
$24 : 00000000 801b3dec
$28 : 813cc000 813cdd10 810b1400 c00e99d8
Hi : 000180ff
Lo : f74e3800
epc : c00e99f0 Not tainted
ra : c00e99d8 Status: 1000dc03 KERNEL EXL IE
Cause : 0000841c
PrId : 00029007
Modules linked in: bcm43xx ipt_ULOG ipt_recent tun ohci_hcd uhci_hcd ieee80211softmac ieee80211 ieee80211_crypt
Process modprobe (pid: 1287, threadinfo=813cc000, task=803cac00)
Stack : 7fb04934 203a726f 00000400 810b1400 81ac8c28 810b1448 c0100010 00000000
c00a1000 80280000 81ac8d56 81ac8d5c 810b1448 c00ebb50 81ac8000 00000000
81ac8c28 810b1448 c010bc68 00000000 c00a1000 80280000 000003bc c00ebd0c
00000000 81854000 7fb04920 00000001 8011de58 203a726f 810b1400 c010b810
ffffffed c010b83c 8011df3c 8011df00 8011de28 80280000 00000000 801b3dec
...
Call Trace: [<c0100010>] [<c00ebb50>] [<c00ebd0c>] [<8011de58>] [<8011df3c>] [<8011df00>] [<8011de28>] [<801b3dec>] [<801389ec>]

Code: 8e630014 8e620120 00622021 <8c820ffc> 3043fff0 0002bc02 3055000f 0003a102 24020800
Data bus error, epc == 80189984, ra == 801765dc
Oops[#2]:
Cpu 0
$ 0 : 00000000 1000d801 ffffffff c0050010
$ 4 : 8113ea00 813cdb60 813cdb60 00000040
$ 8 : 2634e240 386d4a80 2634e240 00000700
$12 : 802c0000 802bfaa0 802bfa90 80279a20
$16 : 8113ea00 00000000 8113ead0 00000002
$20 : 813cdb60 00000000 813cdb60 80280000
$24 : 00000001 00000007
$28 : 813cc000 813cd9f0 810b1400 801765dc
Hi : 00000007
Lo : 00000004
epc : 80189984 Not tainted
ra : 801765dc Status: 1000d803 KERNEL EXL IE
Cause : 0000041c
PrId : 00029007
Modules linked in: bcm43xx ipt_ULOG ipt_recent tun ohci_hcd uhci_hcd ieee80211softmac ieee80211 ieee80211_crypt
Process modprobe (pid: 1287, threadinfo=813cc000, task=803cac00)
Stack : 813cdba0 81e0f2e0 8189f6f0 802d0000 00000001 00000000 00000001 00000000
8113ead0 00000002 813cda18 813cda18 00000000 802c0000 00000020 00000000
00000020 802c0000 802c0000 802c0000 81f4de00 04000000 00000001 00000002
813cdb08 00000000 802bf7dc 00000002 38343163 31303030 813cda68 813cda68
00000000 802c0000 c1c912b6 00000000 00000000 802c0000 802c0000 802c0000
...
Call Trace: [<801765dc>] [<8004d56c>] [<800333ec>] [<8004d684>] [<800334d0>] [<8000aa6c>] [<8000aa74>] [<8002d868>] [<80001ea4>]

Code: 8e430004 2402ffff 00a0b021 <8c700004> 1602000c 32100037 8c820000 8c4500dc 10a00003
Kernel panic - not syncing: Aiee, killing interrupt handler!

It loads fine during the boot though, the panic is when I remove the driver and insert it again:

ieee80211: 802.11 data/management/control stack, git-1.1.7
ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
bcm43xx driver
PCI: Enabling device 0000:00:00.0 (0000 -> 0002)
bcm43xx: Chip ID 0x5365, rev 0x1
bcm43xx: Number of cores: 0
bcm43xx: Core 0: ID 0x800, rev 0x5, vendor 0x4243, enabled
bcm43xx: Error: No 80211 core found!
PCI: Enabling device 0000:01:03.0 (0000 -> 0002)
PCI: Fixing up device 0000:01:03.0
bcm43xx: Chip ID 0x4306, rev 0x3
bcm43xx: Number of cores: 5
bcm43xx: Core 0: ID 0x800, rev 0x4, vendor 0x4243, enabled
bcm43xx: Core 1: ID 0x812, rev 0x5, vendor 0x4243, disabled
bcm43xx: Core 2: ID 0x80d, rev 0x2, vendor 0x4243, enabled
bcm43xx: Core 3: ID 0x807, rev 0x2, vendor 0x4243, disabled
bcm43xx: Core 4: ID 0x804, rev 0x9, vendor 0x4243, enabled
bcm43xx: PHY connected
bcm43xx: Detected PHY: Version: 2, Type 2, Revision 2
bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2)
bcm43xx: Radio turned off
bcm43xx: Radio turned off

Any clues?

Post #2

floe

2 Nov 2006, 09:25

I have a similar error: bcm43xx is built into the kernel and during boot, the core is detected correctly:

<6>bcm43xx driver
<4>PCI: Enabling device 0000:01:02.0 (0000 -> 0002)
<4>PCI: Fixing up device 0000:01:02.0
<7>PCI: Setting latency timer of device 0000:01:02.0 to 64
<6>bcm43xx: Chip ID 0x4306, rev 0x3
<6>bcm43xx: Number of cores: 5
<6>bcm43xx: Core 0: ID 0x800, rev 0x4, vendor 0x4243, enabled
<6>bcm43xx: Core 1: ID 0x812, rev 0x5, vendor 0x4243, disabled
<6>bcm43xx: Core 2: ID 0x80d, rev 0x2, vendor 0x4243, enabled
<6>bcm43xx: Core 3: ID 0x807, rev 0x2, vendor 0x4243, disabled
<6>bcm43xx: Core 4: ID 0x804, rev 0x9, vendor 0x4243, enabled
<6>bcm43xx: PHY connected
<6>bcm43xx: Detected PHY: Version: 2, Type 2, Revision 2
<6>bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2)
<6>bcm43xx: Radio turned off
<6>bcm43xx: Radio turned off

However, as soon as I tried "ifconfig eth2 up", the ifconfig process hung and dmesg produced:

<1>Data bus error, epc == 8012c654, ra == 8012f67c
<4>Oops[#1]:
<4>Cpu 0
<4>$ 0   : 00000000 1000f000 00000001 00010003
<4>$ 4   : 00010000 00000000 0c040083 00040080
<4>$ 8   : 00000009 00000080 00000004 00000000
<4>$12   : 00401043 00705aac 00000001 00000010
<4>$16   : 8037c000 8037cc28 00000000 00000000
<4>$20   : 00000000 8037cd5c 80290000 00008914
<4>$24   : 00000000 80220000                  
<4>$28   : 80afc000 80afdd78 7ff63c68 8012f67c
<4>Hi    : 0029dfff
<4>Lo    : bcfd4527
<4>epc   : 8012c654     Not tainted
<4>ra    : 8012f67c Status: 1000f003    KERNEL EXL IE 
<4>Cause : 0000001c
<4>PrId  : 00024000
<4>Modules linked in: videodev v4l2_common usb_storage sd_mod scsi_mod usblp ohci_hcd vfat fat ext3 jbd ext2 nls_utf8 nl
s_iso8859_15 nls_iso8859_1 nls_cp850 nls_cp437 usbcore nls_base
<4>Process ifconfig (pid: 1203, threadinfo=80afc000, task=80ef2030)
<4>Stack : 000200d2 80ef2030 8028a394 80ef2030 8000925c 00000010 00000002 80055484
<4>        80abe000 802fff20 8030f7c0 80f121e4 8037c000 00000000 80290000 00000000
<4>        80afde30 00000000 00000000 8017d214 10383433 1000001e 2aaad47c 2abd9fc4
<4>        8037c000 00001002 00001043 8017f38c 80018d5c 00000000 8028a360 8083de34
<4>        ffffff82 00000000 80afde20 8037c000 801d3e78 801d3ce8 00008913 00000000
<4>        ...
<4>Call Trace: [<8000925c>]  [<80055484>]  [<8017d214>]  [<8017f38c>]  [<80018d5c>]  [<801d3e78>]  [<801d3ce8>]  [<8017fdb4>]  [<801d56ac>]  [<801702fc>]  [<80170318>]  [<8008ef50>]  [<8008f2a8>]  [<800334d0>]  [<8008f320>]  [<80012bc0>]  [<80012bc0>] 
<4>
<4>Code: 3c040001  34830003  00451021 <8c420f98> 00431024  00441026  03e00008  2c420001  27bdffe8 
<1>Data bus error, epc == 80150f7c, ra == 80151dcc
<4>Oops[#2]:
<4>Cpu 0
<4>$ 0   : 00000000 1000f001 00000080 ffffffff
<4>$ 4   : 00000107 802e8180 00000040 00000088
<4>$ 8   : 00000000 00000000 00000000 00000001
<4>$12   : 80e9ec90 00000006 80e9ed94 00000000
<4>$16   : 802e8180 00001388 802e80e8 802e8180
<4>$20   : 802e80e8 8036dec0 00000040 00000088
<4>$24   : 00000000 801510e4                  
<4>$28   : 8036c000 8036de30 80290000 80151dcc
<4>Hi    : 00000028
<4>Lo    : d4fdc480
<4>epc   : 80150f7c     Not tainted
<4>ra    : 80151dcc Status: 1000f003    KERNEL EXL IE 
<4>Cause : 0000001c
<4>PrId  : 00024000
<4>Modules linked in: videodev v4l2_common usb_storage sd_mod scsi_mod usblp ohci_hcd vfat fat ext3 jbd ext2 nls_utf8 nl
s_iso8859_15 nls_iso8859_1 nls_cp850 nls_cp437 usbcore nls_base
<4>Process kblockd/0 (pid: 6, threadinfo=8036c000, task=80360810)
<4>Stack : 802e8180 00000000 80c0eaf4 8038c880 802e80e8 800e50d4 802e8180 0000024b
<4>        80c0fee8 8038c880 802e80e8 ffffffff 00000000 00000000 00000000 8015033c
<4>        1000c000 00000000 00000000 00000001 00001388 80c25690 00000000 00000000
<4>        80027998 00000000 00000000 00000000 00000000 00000000 80c0eaf4 1000f001
<4>        800e7df4 8033be70 fffffffc 00000000 1000c000 1000c001 8032b580 1000f001
<4>        ...
<4>Call Trace: [<800e50d4>]  [<8015033c>]  [<80027998>]  [<800e7df4>]  [<800e7e8c>]  [<800400dc>]  [<800402a0>]  [<80027930>]  [<8021a7f4>]  [<80040168>]  [<80044aa0>]  [<8000b1cc>]  [<8000b1bc>] 
<4>
<4>Code: 3c028022  8c420550  00441021 <90420000> 03e00008  304200ff  3c028022  8c420550  00441021

Looks to me like it's basically the same error. On my router with rev. 5373, though, this didn't produce a kernel panic, just the oops above. Unfortunately, now all ifconfig/iwconfig calls hang and can't be terminated.

The really weird thing is that I already had the bcm43xx driver up and running with an earlier revision around 4700 or so.. However, at that point, I wasn't yet using the IDE controller, which shares an IRQ with the wireless controller. I just noticed that in my case, the two oopses occured in separate processes, namely ifconfig and kblockd. This might be an indicator that there's really some kind of interrupt sharing issue.

Can you do a cat /proc/interrupts and lspci, just for comparision?

Florian

Post #3

mangoo

2 Nov 2006, 12:06

# lspci -vvv
00:00.0 FLASH memory: Broadcom Corporation Sentry5 Chipcommon I/O Controller (rev 01)
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin ? routed to IRQ 3
Region 0: Memory at 18000000 (32-bit, non-prefetchable) [size=4K]
[virtual] Expansion ROM at 18007000 [disabled] [size=2K]

00:01.0 Ethernet controller: Broadcom Corporation Sentry5 Ethernet Controller (rev 01)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64
Interrupt: pin A routed to IRQ 4
Region 0: Memory at 18001000 (32-bit, non-prefetchable) [size=4K]
[virtual] Expansion ROM at 18007800 [disabled] [size=2K]

00:02.0 Network and computing encryption device: Broadcom Corporation Sentry5 Crypto Accelerator (rev 01)
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin B routed to IRQ 5
Region 0: Memory at 18002000 (32-bit, non-prefetchable) [disabled] [size=4K]
[virtual] Expansion ROM at 18008000 [disabled] [size=2K]

00:03.0 USB Controller: Broadcom Corporation Sentry5 USB Controller (rev 01) (prog-if 10 [OHCI])
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64
Interrupt: pin C routed to IRQ 6
Region 0: Memory at 18003000 (32-bit, non-prefetchable) [size=4K]
[virtual] Expansion ROM at 18008800 [disabled] [size=2K]

00:04.0 MIPS: Broadcom Corporation Sentry5 PCI Bridge (rev 01)
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin D routed to IRQ 2
Region 0: Memory at 18004000 (32-bit, non-prefetchable) [disabled] [size=4K]
[virtual] Expansion ROM at 18009000 [disabled] [size=2K]

00:05.0 MIPS: Broadcom Corporation BCM3302 Sentry5 MIPS32 CPU (rev 01)
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin E routed to IRQ 2
Region 0: Memory at 18005000 (32-bit, non-prefetchable) [disabled] [size=4K]
[virtual] Expansion ROM at 18009800 [disabled] [size=2K]

00:06.0 RAM memory: Broadcom Corporation Sentry5 DDR/SDR RAM Controller (rev 01)
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin ? routed to IRQ 3
Region 0: Memory at 18006000 (32-bit, non-prefetchable) [disabled] [size=4K]
[virtual] Expansion ROM at 1800a000 [disabled] [size=2K]

01:00.0 Host bridge: Broadcom Corporation BCM5365P Sentry5 Host Bridge
Subsystem: Broadcom Corporation BCM5365P Sentry5 Host Bridge
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
Latency: 64
Interrupt: pin A routed to IRQ 2
Region 1: Memory at <unassigned> (32-bit, prefetchable)

01:02.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 61) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 22
Interrupt: pin A routed to IRQ 2
Region 4: I/O ports at 0100 [size=32]
Capabilities: [80] Power Management version 2
Flags: PMEClk+ DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

01:02.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 61) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 22
Interrupt: pin B routed to IRQ 2
Region 4: I/O ports at 0120 [size=32]
Capabilities: [80] Power Management version 2
Flags: PMEClk+ DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

01:02.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 63) (prog-if 20 [EHCI])
Subsystem: VIA Technologies, Inc. USB 2.0
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 22, Cache Line Size: 32 bytes
Interrupt: pin C routed to IRQ 2
Region 0: Memory at 40000000 (32-bit, non-prefetchable) [size=256]
Capabilities: [80] Power Management version 2
Flags: PMEClk+ DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

01:03.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03)
Subsystem: Broadcom Corporation Unknown device 120f
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64
Interrupt: pin A routed to IRQ 2
Region 0: Memory at 40002000 (32-bit, non-prefetchable) [size=8K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=2 PME-

# cat /proc/interrupts
CPU0
2: 92317031 MIPS ehci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb3
3: 233 MIPS serial
4: 1135128 MIPS eth0
6: 0 MIPS ohci_hcd:usb4
7: 57251982 MIPS timer

ERR: 0

# ifconfig eth1 up
Segmentation fault

And it's a kernel panic (revision 5371).

Post #4

floe

2 Nov 2006, 19:59

I opened a ticket: https://dev.openwrt.org/ticket/901
On your router, the wireless device shares IRQ 2 with the USB controller, so it might be an IRQ sharing issue as well. On my router, the block device had crashed, too, so this also fits the picture. I'll try a kernel without IDE next, in your case temporarily disabling the USB stuff might help or at least give more clues.

Post #5

mangoo

2 Nov 2006, 20:14

I boot from a USB-stick, so disabling it is not an option

Post #6

floe

2 Nov 2006, 20:16

Update: I added a ksymoops output to the ticket. Maybe you could do the same..

Post #7

mangoo

2 Nov 2006, 20:29

ksymoops on a 2.6 kernel?

Post #8

floe

2 Nov 2006, 21:05

Yes, it's just not part of the kernel anymore, it's a separate package - the distro of your build system will most likely have it ready (Gentoo had, in my case).

Post #9

mangoo

2 Nov 2006, 22:13

Indeed, here's some learning from Documentation/Changes:

Ksymoops
--------

If the unthinkable happens and your kernel oopses, you may need the
ksymoops tool to decode it, but in most cases you don't.
In the 2.6 kernel it is generally preferred to build the kernel with
CONFIG_KALLSYMS so that it produces readable dumps that can be used as-is
(this also produces better output than ksymoops).
If for some reason your kernel is not build with CONFIG_KALLSYMS and
you have no way to rebuild and reproduce the Oops with that option, then
you can still decode that Oops with ksymoops.

Post #10

floe

2 Nov 2006, 22:33

Aah.. all right, thanks for the hint. Will remember that for the next kernel I build..

Post #11

floe

2 Nov 2006, 23:54

I tried a new kernel without IDE and with CONFIG_KALLSYMS. Oops again.. here's the output:

<1>Data bus error, epc == 8012d834, ra == 8013085c
<4>Oops[#1]:
<4>Cpu 0
<4>$ 0   : 00000000 1000b000 00000001 00010003
<4>$ 4   : 00010000 00000000 0c040083 00040080
<4>$ 8   : 00000009 00000080 00000004 00000000
<4>$12   : 00401043 00705aac 00000001 00000010
<4>$16   : 80396000 80396c28 00000000 00000000
<4>$20   : 00000000 80396d5c 802b0000 00008914
<4>$24   : 00000000 80220000                  
<4>$28   : 80e9c000 80e9dd78 7fd57c68 8013085c
<4>Hi    : 0029dfff
<4>Lo    : bcfd4527
<4>epc   : 8012d834 bcm43xx_core_enabled+0x14/0x28     Not tainted
<4>ra    : 8013085c bcm43xx_init_board+0x19c/0xedc
<4>Status: 1000b003    KERNEL EXL IE 
<4>Cause : 0000001c
<4>PrId  : 00024000
<4>Modules linked in: videodev v4l2_common usb_storage sd_mod scsi_mod usblp ohci_hcd vfat fat ext3 jbd ext2 nls_utf8 nl
s_iso8859_15 nls_iso8859_1 nls_cp850 nls_cp437 usbcore nls_base
<4>Process ifconfig (pid: 721, threadinfo=80e9c000, task=80c14420)
<4>Stack : 000200d2 80c14420 802a4214 80c14420 8000927c 00000010 00000002 800565d4
<4>        80ad0000 8031a260 80329a00 80e7e1e4 80396000 00000000 802b0000 00000000
<4>        80e9de30 00000000 00000000 8017d0f4 10353832 1000001e 8003d9dc fffffff0
<4>        80396000 00001002 00001043 8017f26c 80018d5c 00000000 802a41e0 80e7990c
<4>        ffffff82 00000000 80e9de20 80396000 801d3d58 801d3bc8 00008913 00000000
<4>        ...
<4>Call Trace:
<4> [<8000927c>] ret_from_irq+0x0/0x10
<4> [<800565d4>] __alloc_pages+0x60/0x2e8
<4> [<8017d0f4>] dev_open+0xd8/0x1c0
<4> [<8003d9dc>] sys_setuid+0x0/0x118
<4> [<8017f26c>] dev_change_flags+0x74/0x154
<4> [<80018d5c>] r4k_flush_icache_page+0x28/0x34
<4> [<801d3d58>] devinet_ioctl+0x2fc/0x884
<4> [<801d3bc8>] devinet_ioctl+0x16c/0x884
<4> [<8017fc94>] dev_ioctl+0x380/0x600
<4> [<801d558c>] inet_ioctl+0xc8/0xfc
<4> [<801701dc>] sock_ioctl+0x220/0x264
<4> [<801701f8>] sock_ioctl+0x23c/0x264
<4> [<800900a0>] do_ioctl+0x30/0x78
<4> [<8016f2fc>] sock_alloc_fd+0x28/0x60
<4> [<800903f8>] vfs_ioctl+0x310/0x338
<4> [<8016f4fc>] sock_map_fd+0x30/0x78
<4> [<8017096c>] sock_create+0x10/0x1c
<4> [<80090470>] sys_ioctl+0x50/0x90
<4> [<80012d00>] stack_done+0x20/0x3c
<4> [<80012d00>] stack_done+0x20/0x3c
<4>
<4>
<4>Code: 3c040001  34830003  00451021 <8c420f98> 00431024  00441026  03e00008  2c420001  27bdffe8

So it seems that my previous assumption about IRQ sharing wasn't correct.. this time, bcm43xx should have had the interrupt all by itself.

Now I'm going to get some sleep Hope you (or somebody else) can get something useful out of this.

Good night everybody,
Florian

(Last edited by floe on 3 Nov 2006, 00:10)

Post #12

MMCM

8 Nov 2006, 11:42

Any progress with this problem?
I tried bcm43xx on my WL-500gx yesterday, and had the same effect :-(

Did anybody try the 2.6.18 kernel with updated bcm43xx code?
See http://forum.openwrt.org/viewtopic.php?id=7010
https://dev.openwrt.org/ticket/893

Post #13

MMCM

23 Nov 2006, 00:30

Update: First (and last?) tests with 2.6.18

see http://forum.openwrt.org/viewtopic.php?pid=37643#p37643

Post #14

floe

29 Nov 2006, 17:52

*bump*

From the ticket:

florian wrote:

We will wait for the new SSB code that will be pushed later.

Just curious if there are any new developments on the SSB stuff..

Floe

The discussion might have continued from here.

Page 1 of 1