Bug#556009: ath9k disassociates from 2.6.32-5
Hi Ian, Ian MacDonald wrote: Contrary to my expectations, this is unresolved upstream for my hardware combination in STA mode. I've included some details on my additional tests upstream. Upstream, you wrote: With power management disabled, this bug still exists on my AR5008 (DWA-522) hardware. and said many things about a whole bunch of other Atheros chipsets :). Anyway, do you still experience this with the kernel from testing, sid or experimental? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556009: ath9k disassociates from 2.6.32-5
Thanks Ben; I expected that was the case based on policy. Contrary to my expectations, this is unresolved upstream for my hardware combination in STA mode. I've included some details on my additional tests upstream. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556009: ath9k disassociates from 2.6.32-5
On Thu, Oct 21, 2010 at 08:54:55AM -0400, Ian MacDonald wrote: On Thu, 2010-10-21 at 04:09 +0100, Ben Hutchings wrote: I don't see any fixes there except for disabling power-saving by default, and we have that already. After disabling power management (which I suspect may have already been turned off by default), no change with this issue. Oct 20 18:18:57 maple kernel: [89284.317016] No probe response from AP 00:01:46:XX:XX:XX after 500ms, disconnecting. Oct 20 23:38:25 maple kernel: [108452.317019] No probe response from AP 00:01:46:XX:XX:XX after 500ms, disconnecting. maple:~# iwconfig | grep Power Management Power Management:off There is no specific fix for 2.6.32 as it seems to have resolved itself in the current kernel release and from the comments, it appears the developers were unable to bisect to the specific commit possibly due to build problems over the range where the problem was introduced. Knowing this issue is pegged to Debian stable might help move that effort forwards so I'll post upstream as well. Would an ath9k update be considered/possible at this point if a build against current source resolves this issue? We will only apply bug fixes and new hardware support. We will not normally update a driver to a later upstream version because we do not have the resources to carry out regression testing. Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus signature.asc Description: Digital signature
Bug#556009: ath9k disassociates from 2.6.32-5
On Thu, 2010-10-21 at 04:09 +0100, Ben Hutchings wrote: I don't see any fixes there except for disabling power-saving by default, and we have that already. After disabling power management (which I suspect may have already been turned off by default), no change with this issue. Oct 20 18:18:57 maple kernel: [89284.317016] No probe response from AP 00:01:46:XX:XX:XX after 500ms, disconnecting. Oct 20 23:38:25 maple kernel: [108452.317019] No probe response from AP 00:01:46:XX:XX:XX after 500ms, disconnecting. maple:~# iwconfig | grep Power Management Power Management:off There is no specific fix for 2.6.32 as it seems to have resolved itself in the current kernel release and from the comments, it appears the developers were unable to bisect to the specific commit possibly due to build problems over the range where the problem was introduced. Knowing this issue is pegged to Debian stable might help move that effort forwards so I'll post upstream as well. Would an ath9k update be considered/possible at this point if a build against current source resolves this issue? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556009: ath9k disassociates from 2.6.32-5
Package: linux-2.6 Version: 2.6.32-5 Severity: important After upgrading to Squeeze, my ath9k is dropping its connection intermittently. My hardware and issues matches a bug that is apparently resolved in current linux vanilla (per upstream comments), however persists in the current squeeze 2.6.32-25 images. The issue is consistent with my syslog, my hardware, and my observation that this occurs under some load (rarely when idle) per upstream https://bugzilla.kernel.org/show_bug.cgi?id=14267 01:0a.0 Network controller: Atheros Communications Inc. AR5008 Wireless Network Adapter (rev 01) Subsystem: D-Link System Inc DWA-552 802.11n Xtreme N Desktop Adapter (rev A1) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 168, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 18 Region 0: Memory at fdde (32-bit, non-prefetchable) [size=64K] Capabilities: [40] #80 [] Kernel driver in use: ath9k I have implemented a shutdown of power management that may help per upstream, but have yet to confirm if this workaround is effective at all. # iwconfig ath1 power off The issue does not have a set frequency occurring at intervals of minutes, hours and days. Some syslog message samples with obfuscated mac appears as: Oct 19 07:44:27 maple kernel: [26796.312016] No probe response from AP 00:01:46:XX:XX:XX after 500ms, disconnecting. Oct 19 19:13:32 maple kernel: [ 6159.317018] No probe response from AP 00:01:46:XX:XX:XX after 500ms, disconnecting. Oct 20 14:23:26 maple kernel: [75153.317020] No probe response from AP 00:01:46:XX:XX:XX after 500ms, disconnecting. This system is running the 2.6.32-25 amd64-xen flavour. ii xen-linux-system-2.6.32-5-xen-amd64 2.6.32-25 Xen system with Linux 2.6.32 on 64-bit PCs (meta-package) ii wireless-tools 30~pre9-5 Tools for manipulating Linux Wireless Extensions -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556009: ath9k disassociates from 2.6.32-5
On Wed, 2010-10-20 at 16:03 -0400, Ian MacDonald wrote: Package: linux-2.6 Version: 2.6.32-5 Severity: important After upgrading to Squeeze, my ath9k is dropping its connection intermittently. My hardware and issues matches a bug that is apparently resolved in current linux vanilla (per upstream comments), however persists in the current squeeze 2.6.32-25 images. The issue is consistent with my syslog, my hardware, and my observation that this occurs under some load (rarely when idle) per upstream https://bugzilla.kernel.org/show_bug.cgi?id=14267 [...] I don't see any fixes there except for disabling power-saving by default, and we have that already. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
