Bug#681232: [3.2.20-3.2.21 regression] Atheros WiFi Adapter couldn't find networks gain calibration timeout
whoa, I'll see what I can do. Building the 3.4.7 kernel was my first try at building the kernel, I downloaded the bz2 file from kernel.org and followed the steps in Telemachus' post (post #5) in the following thread: http://forums.debian.net/viewtopic.php?f=16t=36525 I haven't used git before but I will give your steps a try. I definitely did not have this problem with the 3.2.20 Debian kernel build. I diff'd the 3.2.20 and 3.2.21 kernel code (from kernel.org) in net/wireless/ath and I didn't see any differences so I was surprised the issue started happening with 3.2.21. On 08/05/2012 01:37 AM, Jonathan Nieder wrote: tags 681232 + patch moreinfo quit Hi, Russ Lind wrote: For what it's worth, the 3.5-1 kernel from experimental works for me [...] I'd also built the 3.4.7 kernel from the sources at kernel.org. [...] I've read about a number of people having this issue thru the 3.3 kernels with various distros, and read the issue was supposedly fixed in the 3.4 branch. I get the impression it's an upstream issue. Maybe one of the following patches helped. v3.3-rc1~182^2~44^2~292 ath5k: Calibration re-work v3.4-rc1~177^2~108^2~108 ath5k: do not stop queues for full calibration v3.4-rc1~177^2~108^2~107 ath5k: do not re-run AGC calibration periodically What seems oddest to me is that I'm not aware of any patches from the range 3.2.20-3.2.21 that might have had this effect. Are you sure that 3.2.20 did not reproduce the bug? If you have time to try one of the following, I'd be interested: a. Please test v3.2.20 and v3.2.21 from kernel.org, following instructions from [1] or the following steps: # get the kernel history, if you don't already have it git clone \ git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git # fetch point releases: cd linux git remote add stable \ git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git git fetch stable # configure, build, test: git checkout v3.2.21 cp /boot/config-$(uname -r) .config; # current configuration scripts/config --disable DEBUG_INFO make localmodconfig; # optional: minimize configuration make deb-pkg; # optionally with -jnum for parallel build dpkg -i ../name of package; # as root reboot ... test test test ... # hopefully it reproduces the bug, so try the older kernel: cd linux git checkout v3.2.20 make deb-pkg; # maybe with -j4 dpkg -i ../name of package; # as root reboot ... test test test ... # hopefully it does not reproduce the bug b. If (a) goes well, please bisect to find which patch introduced the bug, as described at [2]: cd linux git bisect start git bisect goodsome known-good kernel git bisect bad v3.2.21 # a version halfway between is automatically checked out make deb-pkg; # maybe with -j4 dpkg -i ../name of package; # as root reboot ... test test test ... cd linux git bisect good; # if it works well git bisect bad; # if it reproduces the calibration timeouts git bisect skip; # if some other bug makes it hard to test ... rinse and repeat until it prints the first bad commit or until bored ... # at any step, to see the regression range narrowing apt-get install gitk git bisect visualize # to get a log of revs tested so far, which will let someone # else pick up where you left off git bisect log c. How does a pre-compiled 3.3 kernel from http://snapshot.debian.org do? d. Please test the three attached patches together against a 3.2.y kernel, following the directions at [3] or the following instructions: cd linux git checkout stable/linux-3.2.y git am -3sc $(ls -1 /path/to/patches/0[123]-*) make deb-pkg; # maybe with -j4 dpkg -i ../name of package; # as root reboot ... test test test ... Hope that helps, Jonathan [1] http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-kernel-org-package [2] http://kernel-handbook.alioth.debian.org/ch-bugs.html#s9.2.1 [3] http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/501e8d6b.6060...@comcast.net
Bug#681232: linux-image-3.2.0-3-amd64: Atheros WiFi Adapter couldn't find networks gain
Well, not sure anymore now. Everything seems to be working today. I built the kernel.org 3.2.21 kernel, that seems to work fine, the Debian 3.2.0-3 (3.2.21) kernel also seems to work fine. I tried both cold reboot and warm reboot, none of them failed the calibration. From my 3.2.21 build: dmesg [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.2.21 (russ@debian-f5) (gcc version 4.7.1 (Debian 4.7.1-2) ) #1 SMP Sun Aug 5 09:49:01 PDT 2012 [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.21 root=UUID=9e1f0932-58eb-4450-b269-f390869c741d ro quiet splash dmesg | grep ath5k [5.569303] ath5k :07:00.0: PCI INT A - GSI 19 (level, low) - IRQ 19 [5.569314] ath5k :07:00.0: setting latency timer to 64 [5.569390] ath5k :07:00.0: registered as 'phy0' [6.149671] Registered led device: ath5k-phy0::rx [6.149698] Registered led device: ath5k-phy0::tx [6.149712] ath5k phy0: Atheros AR5414 chip found (MAC: 0xa3, PHY: 0x61) dmesg | grep wlan0 [ 16.166850] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 28.981639] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 30.099293] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 36.523345] wlan0: authenticate with xx:xx:xx:xx:xx:xx (try 1) [ 36.524900] wlan0: authenticated [ 36.524991] wlan0: associate with xx:xx:xx:xx:xx:xx (try 1) [ 36.527755] wlan0: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x411 status=0 aid=1) [ 36.527768] wlan0: associated [ 36.530845] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready From the Debian 3.2.0-3 build: dmesg [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.2.0-3-amd64 (Debian 3.2.21-3) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-8) ) #1 SMP Thu Jun 28 09:07:26 UTC 2012 [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-3-amd64 root=UUID=9e1f0932-58eb-4450-b269-f390869c741d ro quiet splash dmesg | grep ath5k [3.687460] ath5k :07:00.0: PCI INT A - GSI 19 (level, low) - IRQ 19 [3.687485] ath5k :07:00.0: setting latency timer to 64 [3.687680] ath5k :07:00.0: registered as 'phy0' [4.268684] Registered led device: ath5k-phy0::rx [4.268714] Registered led device: ath5k-phy0::tx [4.268728] ath5k phy0: Atheros AR5414 chip found (MAC: 0xa3, PHY: 0x61) [ 1830.318376] ath5k :07:00.0: restoring config space at offset 0xf (was 0x1ff, writing 0x10b) [ 1830.318396] ath5k :07:00.0: restoring config space at offset 0x4 (was 0x4, writing 0xb024) [ 1830.318401] ath5k :07:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x8) [ 1830.318409] ath5k :07:00.0: restoring config space at offset 0x1 (was 0x10, writing 0x17) dmesg | grep wlan0 [ 17.058187] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 29.972924] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 31.192990] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 37.675556] wlan0: authenticate with xx:xx:xx:xx:xx:xx (try 1) [ 37.677071] wlan0: authenticated [ 37.677125] wlan0: associate with xx:xx:xx:xx:xx:xx (try 1) [ 37.679933] wlan0: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x411 status=0 aid=1) [ 37.679939] wlan0: associated [ 37.681506] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/501ec276.4040...@comcast.net
Bug#681232: linux-image-3.2.0-3-amd64: Atheros WiFi Adapter couldn't find networks gain
For what it's worth, the 3.5-1 kernel from experimental works for me without the pcie_aspm=force option. cat /proc/version Linux version 3.5-trunk-amd64 (Debian 3.5-1~experimental.1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Thu Aug 2 17:16:27 UTC 2012 lspci -v -xxx -s 07:00.0 07:00.0 Ethernet controller: Atheros Communications Inc. AR242x / AR542x Wireless Network Adapter (PCI-Express) (rev 01) Subsystem: AMBIT Microsystem Corp. Device 0422 Flags: bus master, fast devsel, latency 0, IRQ 19 Memory at b020 (64-bit, non-prefetchable) [size=64K] Capabilities: [40] Power Management version 2 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [60] Express Legacy Endpoint, MSI 00 Capabilities: [90] MSI-X: Enable- Count=1 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Kernel driver in use: ath5k 00: 8c 16 1c 00 07 00 10 00 01 00 00 02 08 00 00 00 10: 04 00 20 b0 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 01 50 00 00 68 14 22 04 30: 00 00 00 00 40 00 00 00 00 00 00 00 0b 01 00 00 40: 01 50 c2 01 00 00 00 00 00 00 00 00 00 00 00 00 50: 05 60 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 10 90 11 00 40 02 64 00 10 20 0a 00 11 3c 03 00 70: 48 00 11 10 00 00 00 00 c0 03 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 11 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 dmesg [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.5-trunk-amd64 (Debian 3.5-1~experimental.1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Thu Aug 2 17:16:27 UTC 2012 [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-3.5-trunk-amd64 root=UUID=9e1f0932-58eb-4450-b269-f390869c741d ro quiet splash dmesg | grep ath5k [5.348070] ath5k :07:00.0: registered as 'phy0' [6.065246] Registered led device: ath5k-phy0::rx [6.065317] Registered led device: ath5k-phy0::tx [6.065347] ath5k: phy0: Atheros AR5414 chip found (MAC: 0xa3, PHY: 0x61) dmesg | grep wlan0 [ 18.499336] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 31.154216] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 32.285974] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 38.692294] wlan0: authenticate with xx:xx:xx:xx:xx:xx [ 38.696433] wlan0: send auth to xx:xx:xx:xx:xx:xx (try 1/3) [ 38.697925] wlan0: authenticated [ 38.704030] wlan0: associate with xx:xx:xx:xx:xx:xx (try 1/3) [ 38.706491] wlan0: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x411 status=0 aid=1) [ 38.706874] wlan0: associated [ 38.707705] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready I'd also built the 3.4.7 kernel from the sources at kernel.org. This kernel worked okay for me without the pcie_aspm=force option. Not sure why I didn't try the 3.4.4 kernel that was in experimental at the time. I've read about a number of people having this issue thru the 3.3 kernels with various distros, and read the issue was supposedly fixed in the 3.4 branch. I get the impression it's an upstream issue. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/501d981b.3090...@comcast.net
Bug#681232: linux-image-3.2.0-3-amd64: Atheros WiFi Adapter couldn't find networks gain calibration timeout
I have this same issue with linux-image-3.2.0.3-amd64 (3.2.21). All previous wheezy kernels up to linux-image-3.2.0.2-amd64 (3.2.20) have been working fine for me. lspci -v 07:00.0 Ethernet controller: Atheros Communications Inc. AR242x / AR542x Wireless Network Adapter (PCI-Express) (rev 01) Subsystem: AMBIT Microsystem Corp. Device 0422 Flags: bus master, fast devsel, latency 0, IRQ 19 Memory at b020 (64-bit, non-prefetchable) [size=64K] Capabilities: [40] Power Management version 2 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [60] Express Legacy Endpoint, MSI 00 Capabilities: [90] MSI-X: Enable- Count=1 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Kernel driver in use: ath5k cat /proc/version Linux version 3.2.0-3-amd64 (Debian 3.2.21-3) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-8) ) #1 SMP Thu Jun 28 09:07:26 UTC 2012 I found this same issue reported for linux-image-3.2.0-2-amd64 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665881 The fix of adding pcie_aspm=force to the kernel command line (see message #124) seems to be working for me. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5003892e.3060...@comcast.net
