wl12xx borked after one up/down cycle
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Saucy |
Fix Released
|
Medium
|
Unassigned | ||
Trusty |
Fix Released
|
Medium
|
Unassigned |
Bug Description
SRU:
Impact: wifi on the Pandaboard is not working after doing one "up/down cycle". This can either be a "ifconfig wlan0 up && ifconfig wlan0 down", or something else that triggers firmware booting inside wl12xx
This is wlan output after a cold boot:
wlcore: firmware booted (Rev 6.3.10.0.133)
wlan0: authenticate with a0:f3:c1:46:2c:e4
wlan0: send auth to a0:f3:c1:46:2c:e4 (try 1/3)
wlan0: authenticated
wlan0: associate with a0:f3:c1:46:2c:e4 (try 1/3)
wlan0: RX AssocResp from a0:f3:c1:46:2c:e4 (capab=0x431 status=0 aid=2)
wlan0: associated
cfg80211: Calling CRDA for country: DE
cfg80211: Regulatory domain changed to country: DE
cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
cfg80211: (2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A, 2000 mBm)
cfg80211: (5150000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm)
cfg80211: (5250000 KHz - 5350000 KHz @ 40000 KHz), (N/A, 2000 mBm)
cfg80211: (5470000 KHz - 5725000 KHz @ 40000 KHz), (N/A, 2698 mBm)
cfg80211: (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm)
wlcore: Association completed.
while this is what happens after a warm reboot or after an ifdown/ifup cycle:
wlcore: down
wlcore: ERROR timeout waiting for the hardware to complete initialization
wlcore: ERROR timeout waiting for the hardware to complete initialization
wlcore: ERROR timeout waiting for the hardware to complete initialization
wlcore: ERROR firmware boot failed despite 3 retries
Both S and T are affected, but:
* patches 1 and 2 are a prerequisite and are required for S only (since T already has them)
* patches 3 and 4 are the real fix, and ATM are queued in tmlind's omap-for-
Fix: apply the attached patches and recompile
Test case: boot the patched kernel, check that wifi is on, reboot the board and check again that wifi availability
--
tags: | added: patch |
Changed in linux (Ubuntu Saucy): | |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Trusty): | |
importance: | Undecided → Medium |
tags: | added: saucy trusty |
Changed in linux (Ubuntu Saucy): | |
status: | New → Confirmed |
Changed in linux (Ubuntu Trusty): | |
status: | Incomplete → Confirmed |
tags: |
added: verification-done-saucy removed: verification-needed-saucy |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1258174
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.