#927: Total hang on loading ath_pci (0.9.2) on mips-be platform
-----------------------------------+----------------------------------------
Reporter: [EMAIL PROTECTED] | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: madwifi: driver | Version:
Keywords: | Patch_attached: 0
-----------------------------------+----------------------------------------
Hi, I am building my own firmware image for a Netgear DG834GT router. This
is
based on the Broadcom BCM6348 (mips-be), and has an atheros minipci card
in it.
Unfortunately the latest (0.9.2) drivers lock the machine up completely
as soon as I load ath_pci.
Details of the card:
{{{
vendor:0x168c
device:0x0013
subsystem_vendor:0x168c
subsystem_device:0x2051
There are no markings on minipci card itself.
}}}
Loading the 0.9.2 modules reports:
{{{
wlan: 0.8.4.2 (0.9.2)
wlan: mac acl policy registered
ath_hal: module license 'Proprietary' taints kernel.
ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413,
REGOPS_FUNC)
ath_rate_amrr: 0.1 (0.9.2)
ath_pci: 0.9.4.5 (0.9.2)
PCI: Enabling device 0000:00:01.0 (0000 -> 0002)
ath_attach: devid 0x13
}}}
At this point, the machine locks - no oops or anything. I enabled as many
kernel debug options as possible, but.. nothing.
I then added tracing and found its the call to: ath_hal_attach() which
hangs. So I
enabled the HAL debug. This shows the following:
{{{
ath_hal_reg_read(16388)
READ 0x4004 => 0x100
WRITE 0x4004 <= 0x100
ath_hal_reg_read(16400)
READ 0x4010 => 0x14000100
ath_hal_reg_read(32772)
READ 0x8004 => 0x0
WRITE 0x8004 <= 0x0
ath_hal_reg_read(16416)
READ 0x4020 => 0x79000000
ath_hal_reg_read(16388)
READ 0x4004 => 0x100
WRITE 0x4004 <= 0x100
ath_hal_reg_read(16400)
READ 0x4010 => 0x14000100
ath_hal_reg_read(32772)
READ 0x8004 => 0x0
WRITE 0x8004 <= 0x0
ath_hal_reg_read(12)
READ 0xc => 0x0
WRITE 0x4000 <= 0x13
ath_hal_reg_read(16384)
READ 0x4000 => 0x0
}}}
it then does:
{{{
ath_hal_reg_read(16384)
READ 0x4000 => 0x0
usleep()
}}}
loads of times - looks like some kind of polling wait
for something to initialise to me.
Finally, it does:
{{{
READ 0x4000 => 0x0
ath_hal_reg_read(32772)
}}}
At this point, it hangs.
The machine actually comes with drivers which seem /very/ similar to the
madwifi
ones, however, it also contains a module, ath_rate_atheros.ko, which makes
me think
they are basing it on an internal atheros codebase. These drivers actually
work ok,
so I could use them instead, but where's the fun in that? :)
Loading the /Netgear/ drivers reports:
{{{
wlan: 0.8.4.2 (Atheros/multi-bss)
wlan: mac acl policy registered
ath_hal: module license 'Proprietary' taints kernel.
ath_hal: 0.9.14.25 (AR5212, RF5111, RF5112, RF2413)
ath_rate_atheros: Version 2.0.1
ath_pci: 0.9.4.5 (Atheros/multi-bss) (0.1.1)
PCI: Enabling device 0000:00:01.0 (0000 -> 0002)
wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps
24Mbps 36Mbps 48Mbps 54Mbps
wifi0: turboG rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
wifi0: mac 7.9 phy 4.5 radio 5.6
wifi0: Use hw queue 1 for WME_AC_BE traffic
wifi0: Use hw queue 0 for WME_AC_BK traffic
wifi0: Use hw queue 2 for WME_AC_VI traffic
wifi0: Use hw queue 3 for WME_AC_VO traffic
wifi0: Use hw queue 8 for CAB traffic
wifi0: Use hw queue 9 for beacons
wifi0: Atheros 5212: mem=0x8000000, irq=32
}}}
Is there anything else I can do to provide more information to help with
debugging?
--
Ticket URL: <http://madwifi.org/ticket/927>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets
