From: "Torquil Macdonald Sørensen" <torquil@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] AR9285: Possible intermittent connection drop-outs
Date: Tue, 17 Aug 2010 18:10:33 +0200 [thread overview]
Message-ID: <4C6AB479.2010603@gmail.com> (raw)
Hi guys!
Essential, I'd like recommendations as to which ath9k debugging options I would
want to use to effectively diagnose the following problem:
I'm having some problems with my AR9285 based wireless card on an Asus X5DID
laptop, using Linux 2.6.35.2 on Debian Sid. I'm connecting to a D-Link DIR-615
wireless router with the newest firmware.
The problem is: sometimes, even though Network Manager displays a good
connection strength, I loose communication with the router and therefore also
the internet. In this state, which is temporary, I cannot ping the router.
Typical scenario:
While I am browsing, suddenly Firefox is no longer able to receive web pages. I
typically try to ping the router at 192.168.0.1, but get no reply or very slow
replies and many lost pings.
I have a sneaking suspicion that my pinging efforts are able to "wake" the
connection up to some degree, since often times web pages are able to load just
after I start to ping.
The problem fixes itself, usually after a few minutes. But the problem will come
and go quite randomly. Network Manager never notices any of this. It happily
displays a good connection all the time.
Most of the time everything works fine. I'm quite certain that wireless in the
Windows 7 OS on the same laptop works flawlessly, so its not a hardware or
router problem. The other guy here uses Windows XP with a USB wireless card and
never has similar problems.
I have recompiled Linux to get some debugging going, but there are lots of debug
options and some of them result in a massive amount of information being logged.
So I'd like to get some recommendation as to which debugging option I should try
first, out of these:
http://wireless.kernel.org/en/users/Drivers/ath9k/debug
The settings on the router are:
Enable auto channel selection: on
Transmission rate: Best (auto)
WMM Enable: on (wireless QoS)
Security mode: WPA/WPA2 Wireless Security (enhanced)
Cipher type: AUTO (TKIP/AES)
PSK/EAP: PSK
Network Key: ******** (hidden)
Beacon interval: 100ms
RTS threshold: 2346
Fragmentation: 2346
DTIM interval: 1
Preamble type: Short
CTS mode: Auto
Wireless mode: 802.11 Mixed (g/b)
From 'lspci':
04:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network
Adapter (PCI-Express) (rev 01)
next reply other threads:[~2010-08-17 16:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 16:10 Torquil Macdonald Sørensen [this message]
2010-08-18 15:20 ` [ath9k-devel] AR9285: Possible intermittent connection drop-outs Peter Stuge
2010-08-18 17:08 ` Alan
2010-08-18 23:34 ` Ben Gamari
2010-08-19 0:59 ` Peter Stuge
2010-08-19 1:22 ` Adrian Chadd
2010-08-19 23:43 ` Torquil Macdonald Sørensen
2010-08-20 0:40 ` Adrian Chadd
[not found] ` <AANLkTik=6gKT7+eXc8H9fGfWJ6egD5bm8CMzTJivbP7Z@mail.gmail.com>
2010-08-21 12:52 ` Torquil Macdonald Sørensen
[not found] ` <4C6FC95C.4090703@gmail.com>
[not found] ` <AANLkTimEVJwVsGrsDkhCp6vA6auqYqP6913_RQse=zRR@mail.gmail.com>
2010-08-23 15:20 ` Torquil Macdonald Sørensen
2010-09-08 16:33 ` Torquil Macdonald Sørensen
-- strict thread matches above, loose matches on Subject: below --
2010-11-20 10:18 Dan Borlovan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C6AB479.2010603@gmail.com \
--to=torquil@gmail.com \
--cc=ath9k-devel@lists.ath9k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.