Skip to contentSkip to conversation

2.6.17-rc1: bcm43xx problems with BCM4306 on x86_64

DISCUSSION Rafael J. Wysocki 1 participant 2 messages Apr 7, 2006 1 message not in the archive

lore
Share & tools
lore
#0 lore raw

Hi,

I've just tried the version of the driver included in 2.6.17-rc1 on an x86_64 box (Asus L5D) with a built-in PCI BCM4306 adapter (Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03)), and unfortunately it doesn't seem to work.

The driver loads and seems to initialize the adapter, but that's all, apparently.

First, I compiled the driver with DMA and PIO support, but it hanged my box solid when I tried "iwconfig eth1 essid on" on it. On the next boot I noticed it caused the following messages to appear in dmesg:

nommu_map_single: overflow 58ee7010+2404 of device mask 3fffffff
nommu_map_single: overflow 53669010+2404 of device mask 3fffffff
nommu_map_single: overflow 50180010+2404 of device mask 3fffffff

and so on, down to 455aa010. Then I thought the adapter might be unable to DMA for some reason and compiled it with PIO support only. It did not hang the box any more, but I couldn't make it work.

It causes the following messages to appear in dmesg:

bcm43xx: set security called
bcm43xx:    .level = 0
bcm43xx:    .enabled = 0
bcm43xx:    .encrypt = 0
bcm43xx: PHY connected
bcm43xx: Radio turned on
bcm43xx: Chip initialized
bcm43xx: PIO initialized
bcm43xx: 80211 cores initialized
bcm43xx: Keys cleared
ADDRCONF(NETDEV_UP): eth1: link is not ready
bcm43xx: FATAL ERROR: BCM43xx_IRQ_XMIT_ERROR
bcm43xx: FATAL ERROR: BCM43xx_IRQ_XMIT_ERROR
bcm43xx: FATAL ERROR: BCM43xx_IRQ_XMIT_ERROR
bcm43xx: ASSERTION FAILED (0) at: drivers/net/wireless/bcm43xx/bcm43xx_pio.c:167:parse_cookie()
bcm43xx: ASSERTION FAILED (packetindex >= 0 && packetindex < BCM43xx_PIO_MAXTXPACKETS) at: drivers/net/wireless/bcm43xx/bcm43xx_

pio.c:170:parse_cookie()
bcm43xx: ASSERTION FAILED (queue) at: drivers/net/wireless/bcm43xx/bcm43xx_pio.c:482:bcm43xx_pio_handle_xmitstatus()
bcm43xx: FATAL ERROR: BCM43xx_IRQ_XMIT_ERROR
bcm43xx: FATAL ERROR: BCM43xx_IRQ_XMIT_ERROR
bcm43xx: FATAL ERROR: BCM43xx_IRQ_XMIT_ERROR
bcm43xx: ASSERTION FAILED (0) at: drivers/net/wireless/bcm43xx/bcm43xx_pio.c:167:parse_cookie()
bcm43xx: ASSERTION FAILED (packetindex >= 0 && packetindex < BCM43xx_PIO_MAXTXPACKETS) at: drivers/net/wireless/bcm43xx/bcm43xx_ pio.c:170:parse_cookie()
bcm43xx: ASSERTION FAILED (queue) at: drivers/net/wireless/bcm43xx/bcm43xx_pio.c:482:bcm43xx_pio_handle_xmitstatus()

and so on.

I used fwcutter 004 to extract the firmvare from the Windows file delivered with the machine (BCMWL5.SYS).

If you need/want any more information from me, please let me know.

Greetings,
Rafael

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

#2 lore raw
Quoted 13 lines · Michael Buesch
Quoted 12 lines · Rafael J. Wysocki

I've just tried the version of the driver included in 2.6.17-rc1 on an x86_64 box (Asus L5D) with a built-in PCI BCM4306 adapter (Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03)), and unfortunately it doesn't seem to work.

The driver loads and seems to initialize the adapter, but that's all, apparently.

First, I compiled the driver with DMA and PIO support, but it hanged my box solid when I tried "iwconfig eth1 essid on" on it. On the next boot I noticed it caused the following messages to appear in dmesg:

Quoted 5 lines
Quoted 3 lines

nommu_map_single: overflow 58ee7010+2404 of device mask 3fffffff
nommu_map_single: overflow 53669010+2404 of device mask 3fffffff
nommu_map_single: overflow 50180010+2404 of device mask 3fffffff

You should probably report that to the x86_64 people.

I'll try -mm first and report if this still happens there.

Quoted 5 lines
Quoted 3 lines

and so on, down to 455aa010. Then I thought the adapter might be unable to DMA for some reason and compiled it with PIO support only. It did not hang the box any more, but I couldn't make it work.

PIO does not work, yet. Give me some other few weeks, please.

Oops. Sorry for the noice then. ;-)

Greetings,
Rafael