Re: 2.6.22-41 and bcm43xx



On 12/08/07, Jesus Jr M Salvo <jesus.m.salvo@xxxxxxxxx> wrote:
With the new kernel ( 2.6.22.1-41 x86_64 ), I started getting these
error messages during bootup ( which I did not receive in previous
kernels such as 2.6.21-1.3228:

bcm43xx-phy0 debug: Adding Interface type 2
ssb: Switching to PCI-E core, index 3
ssb: Switching to IEEE 802.11 core, index 1
bcm43xx-phy0 debug: Loading firmware version 371.1061 (2006-10-04 21:02:04)
ssb: Switching to ChipCommon core, index 0
ssb: Switching to IEEE 802.11 core, index 1
bcm43xx-phy0 debug: Radio turned on
bcm43xx-phy0 debug: Radio enabled by hardware
bcm43xx-phy0 debug: bbatt(11) >= size of LO array

Call Trace:
[<ffffffff881f2abf>] :bcm43xx_mac80211:bcm43xx_get_lo_g_ctl+0x65/0xa8
[<ffffffff881f2b38>] :bcm43xx_mac80211:bcm43xx_lo_g_ctl_current+0x36/0x3b
[<ffffffff881f2c1c>] :bcm43xx_mac80211:bcm43xx_lo_g_adjust+0x9/0x15
[<ffffffff881ed25f>] :bcm43xx_mac80211:bcm43xx_phy_init_pctl+0x338/0x6a6
[<ffffffff881e7af4>] :bcm43xx_mac80211:bcm43xx_phy_read+0x5c/0x63
[<ffffffff881f052c>] :bcm43xx_mac80211:bcm43xx_phy_initg+0xc85/0xd0a
[<ffffffff881f0d5f>] :bcm43xx_mac80211:bcm43xx_phy_init+0x582/0x5a7
[<ffffffff881e4cce>] :bcm43xx_mac80211:bcm43xx_chip_init+0x68c/0x9a3
[<ffffffff881e526d>] :bcm43xx_mac80211:bcm43xx_wireless_core_init+0x288/0x73e
[<ffffffff881e62bb>] :bcm43xx_mac80211:bcm43xx_add_interface+0x5f/0xf4
[<ffffffff881b16e4>] :mac80211:ieee80211_open+0x21d/0x34d
[<ffffffff8124354d>] wext_handle_ioctl+0x354/0x39d
[<ffffffff811df4af>] dev_open+0x2f/0x6e
[<ffffffff811dd677>] dev_change_flags+0x5a/0x118
[<ffffffff8122180f>] devinet_ioctl+0x235/0x597
[<ffffffff8124adde>] do_page_fault+0x476/0x7b4
[<ffffffff811d3053>] sock_ioctl+0x1c8/0x1e5
[<ffffffff8109e807>] do_ioctl+0x2b/0xb6
[<ffffffff8109ead5>] vfs_ioctl+0x243/0x25c
[<ffffffff8109eb47>] sys_ioctl+0x59/0x7a
[<ffffffff81009cd5>] tracesys+0xd5/0xda

bcm43xx-phy0 debug: Chip initialized
bcm43xx-phy0 debug: 32-bit DMA initialized
bcm43xx-phy0 debug: Wireless interface started
ADDRCONF(NETDEV_UP): wlan0: link is not ready


Any ideas ?


Forgot to mention my actual card. From lspci -vv:

03:00.0 Network controller: Broadcom Corporation BCM4310 UART (rev 01)
Subsystem: Hewlett-Packard Company Unknown device 1361
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: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 19
Region 0: Memory at b3200000 (32-bit, non-prefetchable) [size=16K]
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-
Capabilities: [58] Message Signalled Interrupts: Mask- 64bit-
Queue=0/0 Enable-
Address: 00000000 Data: 0000
Capabilities: [d0] Express Legacy Endpoint IRQ 0
Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag+
Device: Latency L0s <4us, L1 unlimited
Device: AtnBtn- AtnInd- PwrInd-
Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s, Port 0
Link: Latency L0s <4us, L1 <64us
Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch-
Link: Speed 2.5Gb/s, Width x1
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Virtual Channel

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list



Relevant Pages

  • Re: 2.6.22-41 and bcm43xx
    ... bcm43xx-phy0 debug: Adding Interface type 2 ... ssb: Switching to IEEE 802.11 core, ...
    (Fedora)
  • Re: 2.6.22-41 and bcm43xx
    ... bcm43xx-phy0 debug: Adding Interface type 2 ... ssb: Switching to IEEE 802.11 core, ...
    (Fedora)
  • Re: 2.6.22-41 and bcm43xx
    ... bcm43xx-phy0 debug: Adding Interface type 2 ... ssb: Switching to IEEE 802.11 core, ...
    (Fedora)
  • 2.6.22-41 and bcm43xx
    ... bcm43xx-phy0 debug: Adding Interface type 2 ... ssb: Switching to IEEE 802.11 core, ...
    (Fedora)
  • Re: Need help with own PXE/bootloader and SDI images
    ... If the problem is in NT Loader, switching to serial debug may show some good ... that SDI is loaded in memory where it is expected. ... reallocate the ...
    (microsoft.public.windowsxp.embedded)