Interesting 14e4:4321

Interesting 14e4:4321

[Rafał Miłecki]

Swen has found 14e4:4321 in his WRT160N version 1.1. This is quite
rare and interesting so I wanted to post all info about it :)

I'm attaching lspci and dmesg.

I find it interesting because it seems to be SSB SOC with standard
cores: CC, FastEthernet, USB, MIPS, etc. Plus there is PCI bridge with
14e4:4321 card connected, which is SSB-based one with (the most
interesting) 80211.

Unfortunately this is one another BCM4321 with DMA not working. I
really need to focus on this after fixing LP-PHY and adding BCMA.

-- 
Rafa?
-------------- next part --------------
# lspci -tvnn //kernel 2.4
-[0000:00]-+-00.0  Broadcom Corporation Sentry5 Chipcommon I/O Controller [14e4:0800]
          +-01.0  Broadcom Corporation Sentry5 Ethernet Controller [14e4:4713]
          +-02.0  Broadcom Corporation Sentry5 Ethernet Controller [14e4:4713]
          +-03.0  Broadcom Corporation Sentry5 USB Controller [14e4:4715]
          +-04.0-[01]--+-00.0  Broadcom Corporation BCM4704 PCI to SB Bridge [14e4:4704]
          |            \-01.0  Broadcom Corporation BCM4306 802.11a Wireless LAN Controller [14e4:4321]
          +-05.0  Broadcom Corporation BCM3302 Sentry5 MIPS32 CPU [14e4:0816]
          +-06.0  Broadcom Corporation BCM47xx V.92 56k modem [14e4:4712]
          +-07.0  Broadcom Corporation Sentry5 Crypto Accelerator [14e4:4718]
          \-08.0  Broadcom Corporation Sentry5 DDR/SDR RAM Controller [14e4:080f]


# lspci -tvnn //kernel 2.6
-[0000:00]---00.0  Broadcom Corporation BCM4704 PCI to SB Bridge [14e4:4704]


# lspci -tvnn //kernel 2.6 with nvram cardbus=0
root at OpenWrt:/# lspci -tvnn
-[0000:00]-+-00.0  Broadcom Corporation BCM4704 PCI to SB Bridge [14e4:4704]
          \-01.0  Broadcom Corporation BCM4306 802.11a Wireless LAN Controller [14e4:4321]


# lspci -vnn //kernel 2.4
00:00.0 FLASH memory [0501]: Broadcom Corporation Sentry5 Chipcommon I/O Controller [14e4:0800] (rev 09)
       Flags: fast devsel, IRQ 3
       Memory at 18000000 (32-bit, non-prefetchable) [disabled] [size=4K]
       Memory at 1fc00000 (32-bit, non-prefetchable) [disabled] [size=4M]
       Memory at 1c000000 (32-bit, non-prefetchable) [disabled] [size=32M]
       Memory at 1a000000 (32-bit, non-prefetchable) [disabled] [size=32M]
       Expansion ROM at <unassigned> [disabled] [size=2K]

00:01.0 Ethernet controller [0200]: Broadcom Corporation Sentry5 Ethernet Controller [14e4:4713] (rev 09)
       Flags: bus master, fast devsel, latency 64, IRQ 4
       Memory at 18001000 (32-bit, non-prefetchable) [disabled] [size=4K]
       Expansion ROM at <unassigned> [disabled] [size=2K]

00:02.0 Ethernet controller [0200]: Broadcom Corporation Sentry5 Ethernet Controller [14e4:4713] (rev 09)
       Flags: bus master, fast devsel, latency 64, IRQ 5
       Memory at 18002000 (32-bit, non-prefetchable) [disabled] [size=4K]
       Expansion ROM at <unassigned> [disabled] [size=2K]

00:03.0 USB Controller [0c03]: Broadcom Corporation Sentry5 USB Controller [14e4:4715] (rev 09) (prog-if 10 [OHCI])
       Flags: fast devsel, IRQ 6
       Memory at 18003000 (32-bit, non-prefetchable) [disabled] [size=4K]
       Expansion ROM at <unassigned> [disabled] [size=2K]

00:04.0 PCI bridge [0604]: Broadcom Corporation Sentry5 PCI Bridge [14e4:0804] (rev 09) (prog-if 00 [Normal decode])
       Flags: 66MHz, user-definable features, ?? devsel
       Memory at 18004000 (32-bit, non-prefetchable) [disabled] [size=4K]
       Memory at 08000000 (32-bit, non-prefetchable) [disabled] [size=128M]
       Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
       I/O behind bridge: 00000000-00000fff
       Memory behind bridge: 00000000-000fffff
       Prefetchable memory behind bridge: 00000000-000fffff
       Expansion ROM at <unassigned> [disabled] [size=2K]

00:05.0 MIPS [0b30]: Broadcom Corporation BCM3302 Sentry5 MIPS32 CPU [14e4:0816] (rev 09)
       Flags: fast devsel, IRQ 2
       Memory at 18005000 (32-bit, non-prefetchable) [disabled] [size=4K]
       Expansion ROM at <unassigned> [disabled] [size=2K]

00:06.0 Modem [0703]: Broadcom Corporation BCM47xx V.92 56k modem [14e4:4712] (rev 09) (prog-if 00 [Generic])
       Flags: fast devsel, IRQ 2
       Memory at 18006000 (32-bit, non-prefetchable) [disabled] [size=4K]
       Expansion ROM at <unassigned> [disabled] [size=2K]

00:07.0 Network and computing encryption device [1000]: Broadcom Corporation Sentry5 Crypto Accelerator [14e4:4718] (rev 09)
       Flags: fast devsel, IRQ 2
       Memory at 18007000 (32-bit, non-prefetchable) [disabled] [size=4K]
       Expansion ROM at <unassigned> [disabled] [size=2K]

00:08.0 RAM memory [0500]: Broadcom Corporation Sentry5 DDR/SDR RAM Controller [14e4:080f] (rev 09)
       Flags: fast devsel, IRQ 3
       Memory at 18008000 (32-bit, non-prefetchable) [disabled] [size=4K]
       Memory at <unassigned> (32-bit, non-prefetchable) [disabled] [size=128M]
       Memory at 10000000 (32-bit, non-prefetchable) [disabled] [size=128M]
       Memory at 80000000 (32-bit, non-prefetchable) [disabled] [size=512M]
       Expansion ROM at <unassigned> [disabled] [size=2K]

01:00.0 Host bridge [0600]: Broadcom Corporation BCM4704 PCI to SB Bridge [14e4:4704] (rev 09)
       Subsystem: Broadcom Corporation BCM4704 PCI to SB Bridge [14e4:4704]
       Flags: bus master, fast devsel, latency 64, IRQ 2
       Memory at 40000000 (32-bit, non-prefetchable) [size=8K]
       Memory at <unassigned> (32-bit, prefetchable) [size=128M]

01:01.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11a Wireless LAN Controller [14e4:4321] (rev 03)
       Subsystem: Broadcom Corporation BCM4306 802.11a Wireless LAN Controller [14e4:4321]
       Flags: bus master, fast devsel, latency 64, IRQ 2
       Memory at 40004000 (32-bit, non-prefetchable) [size=16K]
-------------- next part --------------
# dmesg | grep ssb //kernel 2.6 with nvram cardbus=0
ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x03, vendor 0x4243)
ssb: Core 1 found: Fast Ethernet (cc 0x806, rev 0x06, vendor 0x4243)
ssb: Core 2 found: Fast Ethernet (cc 0x806, rev 0x06, vendor 0x4243)
ssb: Core 3 found: USB 1.1 Hostdev (cc 0x808, rev 0x03, vendor 0x4243)
ssb: Core 4 found: PCI (cc 0x804, rev 0x08, vendor 0x4243)
ssb: Core 5 found: MIPS 3302 (cc 0x816, rev 0x03, vendor 0x4243)
ssb: Core 6 found: V90 (cc 0x807, rev 0x02, vendor 0x4243)
ssb: Core 7 found: IPSEC (cc 0x80B, rev 0x00, vendor 0x4243)
ssb: Core 8 found: MEMC SDRAM (cc 0x80F, rev 0x02, vendor 0x4243)
ssb: chipcommon status is 0x0
ssb: Initializing MIPS core...
ssb: set_irq: core 0x0806, irq 4 => 4
ssb: set_irq: core 0x0806, irq 5 => 5
ssb: set_irq: core 0x0808, irq 6 => 2
ssb: set_irq: core 0x0804, irq 2 => 6
ssb: after irq reconfiguration
ssb: core 0x0800, irq : 2(S)  3* 4  5  6  D  I
ssb: core 0x0806, irq : 2(S)  3  4* 5  6  D  I
ssb: core 0x0806, irq : 2(S)  3  4  5* 6  D  I
ssb: core 0x0808, irq : 2(S)* 3  4  5  6  D  I
ssb: core 0x0804, irq : 2(S)  3  4  5  6* D  I
ssb: core 0x0816, irq : 2(S)* 3  4  5  6  D  I
ssb: core 0x0807, irq : 2(S)* 3  4  5  6  D  I
ssb: core 0x080b, irq : 2(S)* 3  4  5  6  D  I
ssb: core 0x080f, irq : 2(S)  3  4  5  6  D  I*
ssb: Sonics Silicon Backplane found at address 0x18000000
ssb: PCIcore in host mode found
ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x13, vendor 0x4243)
ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x0C, vendor 0x4243)
ssb: Core 2 found: PCI-E (cc 0x820, rev 0x04, vendor 0x4243)
ssb: Core 3 found: PCI (cc 0x804, rev 0x0D, vendor 0x4243)
ssb: Core 4 found: USB 1.1 Host (cc 0x817, rev 0x04, vendor 0x4243)
ssb: chipcommon status is 0x0
ssb: SPROM offset is 0x1000
ssb: WARNING: Invalid SPROM CRC (corrupt SPROM)
ssb: SPROM revision 0 detected.
ssb: Unsupported SPROM revision 0 detected. Will extract v1
ssb: Sonics Silicon Backplane found on PCI device 0000:00:01.0

Interesting 14e4:4321

[Larry Finger]

On 05/06/2011 03:40 PM, Rafa? Mi?ecki wrote:
> Swen has found 14e4:4321 in his WRT160N version 1.1. This is quite
> rare and interesting so I wanted to post all info about it :)
>
> I'm attaching lspci and dmesg.
>
> I find it interesting because it seems to be SSB SOC with standard
> cores: CC, FastEthernet, USB, MIPS, etc. Plus there is PCI bridge with
> 14e4:4321 card connected, which is SSB-based one with (the most
> interesting) 80211.
>
> Unfortunately this is one another BCM4321 with DMA not working. I
> really need to focus on this after fixing LP-PHY and adding BCMA.

 From the attachments:

01:01.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11a Wireless 
LAN Controller [14e4:4321] (rev 03)
        Subsystem: Broadcom Corporation BCM4306 802.11a Wireless LAN Controller 
[14e4:4321]
        Flags: bus master, fast devsel, latency 64, IRQ 2
        Memory at 40004000 (32-bit, non-prefetchable) [size=16K]

Is this really a 5G-only card? Everything I could see about the WRT160N seemed 
to say that the routers are 802.11b/g/n.

In addition, we really needed more BCM43XX confusion. Is a BCM4306 an 802.11b/g 
with a 14e4:4320 chip, or this one?

Broadcom is really easy to hate!

Larry

Interesting 14e4:4321

[Hauke Mehrtens]

On 05/06/2011 10:40 PM, Rafa? Mi?ecki wrote:
> Swen has found 14e4:4321 in his WRT160N version 1.1. This is quite
> rare and interesting so I wanted to post all info about it :)
> 
> I'm attaching lspci and dmesg.
> 
> I find it interesting because it seems to be SSB SOC with standard
> cores: CC, FastEthernet, USB, MIPS, etc. Plus there is PCI bridge with
> 14e4:4321 card connected, which is SSB-based one with (the most
> interesting) 80211.
> 
> Unfortunately this is one another BCM4321 with DMA not working. I
> really need to focus on this after fixing LP-PHY and adding BCMA.
> 
Hi Rafa?,

RealOpty reported the same DMA error in the OpenWrt channel and it is
nice that you are working on this. He was using a Netgear WNR834B V2.
Here is his dmesg output: http://paste.ubuntu.com/599979/

We already fixed some of the problems with these devices but have not
investigated into the DMA errors.

The cardbus attribute in the nvram seams to be set wrong for some
devices we added a workaround for it for the Netgear WNR834B V2. [0] It
would be nice to get the nvram content ( nvram show ) to also detect
this device and activate the workaround for it.

The SPROM is not stored on the pci card but in the nvram on the flash
chip of the device. This is now correctly read out in OpenWrt and we
will send some patches to mainline soon. [1] [2]

Hauke

[0]:
https://dev.openwrt.org/browser/trunk/target/linux/brcm47xx/patches-2.6.37/980-wnr834b_no_cardbus_invariant.patch
[1]:
https://dev.openwrt.org/browser/trunk/target/linux/brcm47xx/patches-2.6.37/031-ssb-add-callback-for-sprom.patch
[2]:
https://dev.openwrt.org/browser/trunk/target/linux/brcm47xx/patches-2.6.37/033-bcm47xx-register-fallback-callback.patch

Interesting 14e4:4321

[Rafał Miłecki]

W dniu 6 maja 2011 23:28 u?ytkownik Larry Finger
<Larry.Finger@lwfinger.net> napisa?:
> On 05/06/2011 03:40 PM, Rafa? Mi?ecki wrote:
>>
>> Swen has found 14e4:4321 in his WRT160N version 1.1. This is quite
>> rare and interesting so I wanted to post all info about it :)
>>
>> I'm attaching lspci and dmesg.
>>
>> I find it interesting because it seems to be SSB SOC with standard
>> cores: CC, FastEthernet, USB, MIPS, etc. Plus there is PCI bridge with
>> 14e4:4321 card connected, which is SSB-based one with (the most
>> interesting) 80211.
>>
>> Unfortunately this is one another BCM4321 with DMA not working. I
>> really need to focus on this after fixing LP-PHY and adding BCMA.
>
> From the attachments:
>
> 01:01.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11a
> Wireless LAN Controller [14e4:4321] (rev 03)
> ? ? ? Subsystem: Broadcom Corporation BCM4306 802.11a Wireless LAN
> Controller [14e4:4321]
> ? ? ? Flags: bus master, fast devsel, latency 64, IRQ 2
> ? ? ? Memory at 40004000 (32-bit, non-prefetchable) [size=16K]
>
> Is this really a 5G-only card? Everything I could see about the WRT160N
> seemed to say that the routers are 802.11b/g/n.
>
> In addition, we really needed more BCM43XX confusion. Is a BCM4306 an
> 802.11b/g with a 14e4:4320 chip, or this one?
>
> Broadcom is really easy to hate!

It's some ooooold description from 2006 or so, so I'm sure it's
incorrect. I've no idea about 14e4:4320.

-- 
Rafa?

Interesting 14e4:4321

[Rafał Miłecki]

W dniu 6 maja 2011 23:36 u?ytkownik Hauke Mehrtens <hauke@hauke-m.de> napisa?:
> On 05/06/2011 10:40 PM, Rafa? Mi?ecki wrote:
>> Swen has found 14e4:4321 in his WRT160N version 1.1. This is quite
>> rare and interesting so I wanted to post all info about it :)
>>
>> I'm attaching lspci and dmesg.
>>
>> I find it interesting because it seems to be SSB SOC with standard
>> cores: CC, FastEthernet, USB, MIPS, etc. Plus there is PCI bridge with
>> 14e4:4321 card connected, which is SSB-based one with (the most
>> interesting) 80211.
>>
>> Unfortunately this is one another BCM4321 with DMA not working. I
>> really need to focus on this after fixing LP-PHY and adding BCMA.
>>
> Hi Rafa?,
>
> RealOpty reported the same DMA error in the OpenWrt channel and it is
> nice that you are working on this. He was using a Netgear WNR834B V2.
> Here is his dmesg output: http://paste.ubuntu.com/599979/

It's nice to see my ssb check for 0x0F90 is working :)


> We already fixed some of the problems with these devices but have not
> investigated into the DMA errors.

Fortunately some Polish user sent me his already-replaced BCM4321
card. So I can reproduce DMA problems locally.


> The cardbus attribute in the nvram seams to be set wrong for some
> devices we added a workaround for it for the Netgear WNR834B V2. [0] It
> would be nice to get the nvram content ( nvram show ) to also detect
> this device and activate the workaround for it.

Swen: could you provide "nvram show" from your device for Hauke, please?


> The SPROM is not stored on the pci card but in the nvram on the flash
> chip of the device. This is now correctly read out in OpenWrt and we
> will send some patches to mainline soon. [1] [2]

Swen already updated his OpenWRT trunk and he got SPROM fallback working :)

-- 
Rafa?

Interesting 14e4:4321

[Jonas Gorski]

2011/5/6 Hauke Mehrtens <hauke@hauke-m.de>:
> On 05/06/2011 10:40 PM, Rafa? Mi?ecki wrote:
>> Swen has found 14e4:4321 in his WRT160N version 1.1. This is quite
>> rare and interesting so I wanted to post all info about it :)

I didn't know BCM4321s identifying as 14e4:4321 are that seldom - the
mini-PCI card in my D-Link DSL-2741B (which is a BCM6358) also does
that.

>> Unfortunately this is one another BCM4321 with DMA not working. I
>> really need to focus on this after fixing LP-PHY and adding BCMA.

Same here, dma is a no go (I have to use pio).

> The SPROM is not stored on the pci card but in the nvram on the flash
> chip of the device. This is now correctly read out in OpenWrt and we
> will send some patches to mainline soon. [1] [2]

Same for the one in my BCM6358 - perhaps SPROM-less devices default to
their chip-id as the PCI device id (just wildly guessing)? I also have
a second BCM6358 with a BCM4322; same there (no SPROM, DMA doesn't
work, and it identifies as 14e4:4322).

Regards
Jonas

P.S: I also get these 0x0F90 clear failures ;)

Interesting 14e4:4321

[Rafał Miłecki]

W dniu 6 maja 2011 23:56 u?ytkownik Jonas Gorski
<jonas.gorski@gmail.com> napisa?:
> 2011/5/6 Hauke Mehrtens <hauke@hauke-m.de>:
>> On 05/06/2011 10:40 PM, Rafa? Mi?ecki wrote:
>>> Swen has found 14e4:4321 in his WRT160N version 1.1. This is quite
>>> rare and interesting so I wanted to post all info about it :)
>
> I didn't know BCM4321s identifying as 14e4:4321 are that seldom - the
> mini-PCI card in my D-Link DSL-2741B (which is a BCM6358) also does
> that.

Well, maybe they are well-known in OpeWRT community :) I believe we
didn't have any reporters here. Unfortunately OpenWRT guys don't
report their problems, fixes too often.


>>> Unfortunately this is one another BCM4321 with DMA not working. I
>>> really need to focus on this after fixing LP-PHY and adding BCMA.
>
> Same here, dma is a no go (I have to use pio).
>
>> The SPROM is not stored on the pci card but in the nvram on the flash
>> chip of the device. This is now correctly read out in OpenWrt and we
>> will send some patches to mainline soon. [1] [2]
>
> Same for the one in my BCM6358 - perhaps SPROM-less devices default to
> their chip-id as the PCI device id (just wildly guessing)? I also have
> a second BCM6358 with a BCM4322; same there (no SPROM, DMA doesn't
> work, and it identifies as 14e4:4322).

Ouch, I didn't know DMA errors also happen for BCM4322. My 14e4:432b
one was working fine. Maybe this is Mini PCI vs. Mini PCIe? Do you
know if your cards are PCI or PCIe?

-- 
Rafa?

Interesting 14e4:4321

[Larry Finger]

On 05/06/2011 04:48 PM, Rafa? Mi?ecki wrote:
>> Broadcom is really easy to hate!
>
> It's some ooooold description from 2006 or so, so I'm sure it's
> incorrect. I've no idea about 14e4:4320.

The BCM4306 (14e4:4320) devices are the oldest 802.11b/g units. That is the one 
where early revs use b43legacy and the newer ones use b43.

Larry

Interesting 14e4:4321

[Jonas Gorski]

2011/5/7 Rafa? Mi?ecki <zajec5@gmail.com>:
> W dniu 6 maja 2011 23:56 u?ytkownik Jonas Gorski
> <jonas.gorski@gmail.com> napisa?:
>> 2011/5/6 Hauke Mehrtens <hauke@hauke-m.de>:
>>> On 05/06/2011 10:40 PM, Rafa? Mi?ecki wrote:
>>>> Swen has found 14e4:4321 in his WRT160N version 1.1. This is quite
>>>> rare and interesting so I wanted to post all info about it :)
>>
>> I didn't know BCM4321s identifying as 14e4:4321 are that seldom - the
>> mini-PCI card in my D-Link DSL-2741B (which is a BCM6358) also does
>> that.
>
> Well, maybe they are well-known in OpeWRT community :) I believe we
> didn't have any reporters here. Unfortunately OpenWRT guys don't
> report their problems, fixes too often.

Well, since this is my only BCM4321, is assumed this is "normal" ;-)

>> Same for the one in my BCM6358 - perhaps SPROM-less devices default to
>> their chip-id as the PCI device id (just wildly guessing)? I also have
>> a second BCM6358 with a BCM4322; same there (no SPROM, DMA doesn't
>> work, and it identifies as 14e4:4322).
>
> Ouch, I didn't know DMA errors also happen for BCM4322. My 14e4:432b
> one was working fine. Maybe this is Mini PCI vs. Mini PCIe? Do you
> know if your cards are PCI or PCIe?

The BCM4322 is directly soldered onto the board, but AFAIK BCM6358
only supports PCI, not PCIe, so it should be a PCI one. The BCM4321
definitely is.

I didn't test whether the BCM4322 actually works with PIO mode, and
the device currently serves as my DSL modem with its stock firmware
(so I can't test it).

Regards
Jonas

Interesting 14e4:4321

[Rafał Miłecki]

Swen, really, include ML in your "to". It's second time.


---------- Wiadomo?? przekazana dalej ----------
Od: Swen Weiland <swen.weiland@googlemail.com>
Data: 7 maja 2011 11:14
Temat: Re: Fwd: Interesting 14e4:4321
Do: Rafa? Mi?ecki <zajec5@gmail.com>
DW: Hauke Mehrtens <hauke@hauke-m.de>



Today I did some more detailed testing an I have to clarify what works
and what not.

The device does not work with DMA (currently), PIO mode is required.
With PIO mode:
"iwlist wlan0 scan" works and networks are reported.
Signal strength in the report does not work.
It is always:
?Quality=70/70 ?Signal level=0 dBm


Associate with with AP seems to work but no data transfer

b43-phy1: Broadcom 4321 WLAN found (core revision 12)
b43-phy1 debug: Found PHY: Analog 5, Type 4, Revision 2
b43-phy1 debug: Found Radio: Manuf 0x17F, Version 0x2055, Revision 4
ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
Registered led device: b43-phy1::tx
Registered led device: b43-phy1::rx
Broadcom 43xx driver loaded [ Features: PNL, GPIO LED Mask: 0x000f,
Firmware-ID: FW13 ]
b43-phy1: Loading firmware version 410.2160 (2007-05-26 15:32:10)
b43-phy1 debug: Chip initialized
b43-phy1 debug: PIO initialized
b43-phy1 debug: QoS enabled
b43-phy1 debug: Wireless interface started
b43-phy1 debug: Adding Interface type 2
wlan0: authenticate with 68:7f:74:06:b8:e8 (try 1)
wlan0: authenticated
wlan0: associate with 68:7f:74:06:b8:e8 (try 1)
wlan0: RX AssocResp from 68:7f:74:06:b8:e8 (capab=0x401 status=0 aid=1)
wlan0: associated
ieee80211 phy1: wlan0: No probe response from AP 68:7f:74:06:b8:e8
after 500ms, disconnecting.


Managed mode can be set and the AP is visible.
Connecting to it is not possible and the device stops working with:

b43-phy1: Loading firmware version 410.2160 (2007-05-26 15:32:10)
b43-phy1 debug: Chip initialized
b43-phy1 debug: PIO initialized
b43-phy1 debug: QoS enabled
b43-phy1 debug: Wireless interface started
device wlan0 entered promiscuous mode
b43-phy1 debug: Adding Interface type 3
br-lan: port 2(wlan0) entering forwarding state
br-lan: port 2(wlan0) entering forwarding state
b43-phy1 debug: Set beacon interval to 100
b43-phy1 debug: Updated beacon template at 0x68
b43-phy1 debug: Updated beacon template at 0x468
device wlan0 left promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
br-lan: port 2(wlan0) entering forwarding state
NOHZ: local_softirq_pending 08
NOHZ: local_softirq_pending 08
NOHZ: local_softirq_pending 08
NOHZ: local_softirq_pending 08
NOHZ: local_softirq_pending 08
NOHZ: local_softirq_pending 08
NOHZ: local_softirq_pending 08
NOHZ: local_softirq_pending 08
NOHZ: local_softirq_pending 08
NOHZ: local_softirq_pending 08


--
Mit freundlichen Gr??en
Swen Weiland

Interesting 14e4:4321

[Michael Büsch]

On Sat, 2011-05-07 at 00:14 +0200, Rafa? Mi?ecki wrote: 
> Unfortunately OpenWRT guys don't
> report their problems, fixes too often.

Well, I think we're pretty fast in pushing patches upstream.
And if you care about OpenWRT's bugreports, there's the bugzilla.

-- 
Greetings Michael.