Skip to contentSkip to conversation

bcm43xx scan oops!!!

DISCUSSION Jory A. Pratt 2 participants 5 messages Oct 10, 2006 1 message not in the archive

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

(gdb) list *bcm43xx_dma_handle_xmitstatus+0xbd
0x3ad is in bcm43xx_dma_handle_xmitstatus (include/asm/dma-mapping.h:91).
86 static inline void
87 dma_unmap_single(struct device *dev, dma_addr_t addr,size_t size,
88 int direction)
89 {
90 BUG_ON(!valid_dma_direction(direction));
91 dma_ops->unmap_single(dev, addr, size, direction);
92 }
93 94 #define dma_map_page(dev,page,offset,size,dir) \
95 dma_map_single((dev), page_address(page)+(offset), (size), (dir))

http://home.nctv.com/anarchy/dscape-clean.jpg

bcm43xx causes kernel oops on 4318 with latest wireless-dev git.

Jory

A message that is not in the archive (sent off-list or not yet received): [email protected]

#4 lore raw
Quoted 6 lines · Jory A. Pratt
Quoted 5 lines · Michael Buesch
Quoted 2 lines · Jory A. Pratt

http://home.nctv.com/anarchy/dscape-clean.jpg

Quoted 6 lines
Quoted 4 lines

That's hardly readable.
But which firmware are you running? v4.x by chance?

Just for completeness I just tested with v4.x firmware and still get the panic

4.x firmware won't work. Make sure to use 3.x.

I am not sure what happens.
Any chance to get a more complete oops message? I am also interrested in the start of the oops message. In particular I would like to see if this is a NULL pointer bug, machine check or something else.
The backtrace is a little big weird. So I am not sure what happens.

And, Please make _really_ sure to use 3.x firmware. ;)

Signature · 1 line
Greetings Michael.
#5 lore raw
Quoted 20 lines · Michael Buesch
Quoted 8 lines · Jory A. Pratt
Quoted 6 lines · Michael Buesch
Quoted 3 lines · Jory A. Pratt

http://home.nctv.com/anarchy/dscape-clean.jpg

Quoted 7 lines
Quoted 5 lines

That's hardly readable.
But which firmware are you running? v4.x by chance?

Just for completeness I just tested with v4.x firmware and still get the panic

4.x firmware won't work. Make sure to use 3.x.

Quoted 9 lines

I am not sure what happens.
Any chance to get a more complete oops message? I am also interrested in the start of the oops message. In particular I would like to see if this is a NULL pointer bug, machine check or something else.
The backtrace is a little big weird. So I am not sure what happens.

And, Please make _really_ sure to use 3.x firmware. ;)

alright here are two more pics for you.

http://home.nctv.com/anarchy/dscape-clean1.jpg
http://home.nctv.com/anarchy/dscape-clean2.jpg

Here is a bit of dmesg that you might find useful:

ssb: Core 0 found: cc 0800, rev 0D, vendor 4243
ssb: Core 1 found: cc 0812, rev 09, vendor 4243
ssb: Core 2 found: cc 0804, rev 0C, vendor 4243
ssb: Core 3 found: cc 080D, rev 07, vendor 4243
bcm43xx_d80211: Broadcom 4318 WLAN found
ssb: Switching to core 2
ssb: Switching to core 1
bcm43xx_d80211: PHY connected
bcm43xx_d80211: Detected PHY: Version: 3, Type 2, Revision 7
bcm43xx_d80211: Detected Radio: ID: 8205017f (Manuf: 17f Ver: 2050 Rev: 8)
bcm43xx_d80211: Radio turned off
bcm43xx_d80211: Radio turned off
wmaster0: Selected rate control algorithm 'simple'
bcm43xx_d80211: Virtual interface added (type: 0x00000002, ID: 5, MAC: 00:90:4b:f2:30:e9)
ssb: Switching to core 0
ssb: Switching to core 1
bcm43xx_d80211: PHY connected
bcm43xx_d80211: firmware revision 127, patchlevel E, date 2005-04-18 02:36:27
ssb: Switching to core 0
bcm43xx_d80211: InitVals (bcm43xx_initvalXX.fw) file-format error. Please fix your bcm43xx firmware files.
bcm43xx_d80211: core_up for active 802.11 core failed (-71)
bcm43xx_d80211: Virtual interface removed (type: 0x00000002, ID: 5, MAC: 00:90:4b:f2:30:e9)
bcm43xx_d80211: Virtual interface added (type: 0x00000002, ID: 5, MAC: 00:90:4b:f2:30:e9)
ssb: Switching to core 1
bcm43xx_d80211: firmware revision 127, patchlevel E, date 2005-04-18 02:36:27
ssb: Switching to core 0
ssb: Switching to core 1
bcm43xx_d80211: Radio turned on
bcm43xx_d80211: ASSERTION FAILED (radio_attenuation < 10) at: drivers/net/wireless/d80211/bcm43xx/bcm43xx_phy.c:1490:bcm43xx_find_lopair()
bcm43xx_d80211: ASSERTION FAILED (radio_attenuation < 10) at: drivers/net/wireless/d80211/bcm43xx/bcm43xx_phy.c:1490:bcm43xx_find_lopair()
bcm43xx_d80211: ASSERTION FAILED (radio_attenuation < 10) at: drivers/net/wireless/d80211/bcm43xx/bcm43xx_phy.c:1490:bcm43xx_find_lopair()
ssb: Switching to core 0
ssb: Switching to core 1
bcm43xx_d80211: Chip initialized
bcm43xx_d80211: 32-bit DMA initialized
bcm43xx_d80211: Keys cleared
bcm43xx_d80211: Selected 802.11 core (phytype 2)
bcm43xx_d80211: ASSERTION FAILED (radio_attenuation < 10) at: drivers/net/wireless/d80211/bcm43xx/bcm43xx_phy.c:1490:bcm43xx_find_lopair()
wmaster0: Does not support passive scan, disabled
wlan0: no IPv6 routers present