aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/lantiq/patches-4.9
diff options
context:
space:
mode:
authorMichal Cieslakiewicz <michal.cieslakiewicz@wp.pl>2018-08-27 20:24:04 +0200
committerMathias Kresin <dev@kresin.me>2018-08-28 07:21:13 +0200
commit4bff3f392bf160146edf6cf2cea25f84e7d88e18 (patch)
tree5aced28e16c8a289fbc4b22bb6baf6d7f141d361 /target/linux/lantiq/patches-4.9
parente3022727658166e736198529582a46abf2397ea4 (diff)
downloadupstream-4bff3f392bf160146edf6cf2cea25f84e7d88e18.tar.gz
upstream-4bff3f392bf160146edf6cf2cea25f84e7d88e18.tar.bz2
upstream-4bff3f392bf160146edf6cf2cea25f84e7d88e18.zip
ar71xx: WNR612v2: fix kernel panic due to wrong Wifi LED init
Netgear WNR612v2 flashed with recent OpenWrt builds suffers from kernel panic at boot during wireless chip initialization, making device unusable: ath: phy0: Ignoring endianness difference in EEPROM magic bytes. ath: phy0: Enable LNA combining CPU 0 Unable to handle kernel paging request at virtual address 1000fee1, epc == 801d08f0, ra == 801d0d90 Oops[#1]: CPU: 0 PID: 469 Comm: kmodloader Not tainted 4.9.120 #0 [ ... register dump etc ... ] Kernel panic - not syncing: Fatal exception Rebooting in 1 seconds.. This simple patch fixes above error. It keeps LED table in memory after kernel init phase for ath9k driver to operate correctly (__initdata removed). Also, another bug is fixed - correct array size is provided to function that adds platform LEDs (this device has only 1 connected to Wifi chip) preventing code from going outside array bounds. Fixes: 1f5ea4eae46e ("ar71xx: add correct named default wireless led by using platform leds") Signed-off-by: Michal Cieslakiewicz <michal.cieslakiewicz@wp.pl> [trimmed commit message] Signed-off-by: Mathias Kresin <dev@kresin.me>
Diffstat (limited to 'target/linux/lantiq/patches-4.9')
0 files changed, 0 insertions, 0 deletions