Activity log for bug #1258174

Date Who What changed Old value New value Message
2013-12-05 14:40:33 Paolo Pisati bug added bug
2013-12-05 14:40:56 Paolo Pisati attachment added 0001-ARM-dts-Fix-muxing-and-regulator-for-wl12xx-on-the-S.patch https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258174/+attachment/3923740/+files/0001-ARM-dts-Fix-muxing-and-regulator-for-wl12xx-on-the-S.patch
2013-12-05 14:41:11 Paolo Pisati attachment added 0002-ARM-dts-twl6030-Move-common-configuration-for-OMAP4-.patch https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258174/+attachment/3923741/+files/0002-ARM-dts-twl6030-Move-common-configuration-for-OMAP4-.patch
2013-12-05 14:41:24 Paolo Pisati attachment added 0003-ARM-dts-omap4-panda-common-Fix-pin-muxing-for-wl12xx.patch https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258174/+attachment/3923742/+files/0003-ARM-dts-omap4-panda-common-Fix-pin-muxing-for-wl12xx.patch
2013-12-05 14:41:44 Paolo Pisati attachment added 0004-ARM-dts-omap4-sdp-Fix-pin-muxing-for-wl12xx.patch https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258174/+attachment/3923743/+files/0004-ARM-dts-omap4-sdp-Fix-pin-muxing-for-wl12xx.patch
2013-12-05 14:46:17 Paolo Pisati 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 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 -- 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-v3.13/fixes-take4 (git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git) 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 --
2013-12-05 14:47:46 Paolo Pisati nominated for series Ubuntu Saucy
2013-12-05 14:47:46 Paolo Pisati nominated for series Ubuntu Trusty
2013-12-05 15:00:10 Brad Figg linux (Ubuntu): status New Incomplete
2013-12-05 16:21:23 Ubuntu Foundations Team Bug Bot tags patch
2013-12-05 16:21:24 Ubuntu Foundations Team Bug Bot bug added subscriber Joseph Salisbury
2013-12-05 17:01:08 Joseph Salisbury bug task added linux (Ubuntu Saucy)
2013-12-05 17:01:14 Joseph Salisbury bug task added linux (Ubuntu Trusty)
2013-12-05 17:01:20 Joseph Salisbury linux (Ubuntu Saucy): importance Undecided Medium
2013-12-05 17:01:22 Joseph Salisbury linux (Ubuntu Trusty): importance Undecided Medium
2013-12-05 17:01:38 Joseph Salisbury tags patch patch saucy trusty
2013-12-05 17:01:45 Joseph Salisbury linux (Ubuntu Saucy): status New Confirmed
2013-12-05 17:01:47 Joseph Salisbury linux (Ubuntu Trusty): status Incomplete Confirmed
2013-12-10 03:29:15 Launchpad Janitor linux (Ubuntu Trusty): status Confirmed Fix Released
2014-02-06 18:41:36 Brad Figg tags patch saucy trusty patch saucy trusty verification-needed-saucy
2014-02-11 16:32:50 Paolo Pisati tags patch saucy trusty verification-needed-saucy patch saucy trusty verification-done-saucy
2014-02-18 13:55:58 Launchpad Janitor linux (Ubuntu Saucy): status Confirmed Fix Released
2014-02-18 13:55:58 Launchpad Janitor cve linked 2013-4587
2014-02-18 13:55:58 Launchpad Janitor cve linked 2013-6367
2014-02-18 13:55:58 Launchpad Janitor cve linked 2013-6368
2014-02-18 13:55:58 Launchpad Janitor cve linked 2013-6376