[Bugme-new] [Bug 20962] New: ath5k / AR2413 causes machine hard lockup on ifconfig wlan0 up

bugzilla-daemon at bugzilla.kernel.org bugzilla-daemon at bugzilla.kernel.org
Fri Oct 22 17:26:04 PDT 2010


https://bugzilla.kernel.org/show_bug.cgi?id=20962

           Summary: ath5k / AR2413 causes machine hard lockup on ifconfig
                    wlan0 up
           Product: Drivers
           Version: 2.5
    Kernel Version: 2.6.36
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: blocking
          Priority: P1
         Component: network-wireless
        AssignedTo: drivers_network-wireless at kernel-bugs.osdl.org
        ReportedBy: mokuba at gmail.com
        Regression: No


When I ifconfig wlan0 up, the machine hardlocks. No mouse/kbd, no ping response
over wired ethernet.

Using the hard rfkill switch, the machine becomes responsive again, but the
interface remains down.

the error is a repeating "ath5k: phy0: too many interrupts, giving up for now"
punctuated occasionally by "

With rfkill support compiled into the kernel, with the switch back on (radios
on), it still believes the switch to be off (kill position) and I can no longer
ifconfig up the device.

Without rfkill support, I can up the device without lockup, however, the only
function I can find to work is iwlist wlan0 scanning. It can see my two APs
according to the report, but if I iwconfig wlan0 essid "Wire2" it does not find
or associate. I then specified the ap's mac address and channel, and it still
refused to associate. (Receive only, perhaps?)

attatched are lspci -vnn, dmesg of the errors during the event, iwconfig and
ifconfig of the device after the event, and kernel .config.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


More information about the Bugme-new mailing list