From: Arkh4mKn1ght <arkh4mkn1ght@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Weird Atheros 9485 http connecting problems
Date: Thu, 15 May 2014 14:44:50 -0300 [thread overview]
Message-ID: <5374FD12.6030307@gmail.com> (raw)
In-Reply-To: <20140515160616.GA3571@qca.qualcomm.com>
I have attached the output of lspci -nn.
Output of iw wlan0 info:
[root at localhost ~]# iw wlan0 info
Interface wlan0
ifindex 3
wdev 0x1
addr 08:3e:8e:dd:c6:13
ssid TP-LINK_E6342E
type managed
wiphy 0
channel 11 (2462 MHz), width: 20 MHz (no HT), center1: 2462 MHz
[root at localhost ~]#
I have enabled the debug options, so i will wait until the problem arises
As soon as it happens i will let you know
Greetings
Oskar
On 05/15/2014 01:06 PM, Rajkumar Manoharan wrote:
> On Thu, May 15, 2014 at 09:57:29AM -0300, Arkh4mKn1ght wrote:
>> Hi
>>
>> Thanks for your reply. Im attaching the lspci output in this email. ..
>> yes, disconnecting from my AP after the problem arises and connecting to
>> smartphone tethering hotspot works fine and i can browse the internet
>> without problems. If i reconnect to the AP the problem resumes unless i
>> reboot or power off the computer.
>>
> Thanks for the quick response. please share output of lspci -nn.
>
>> How do i check if my AP is HT20 or HT40?
> iw wlan0 info
>> As for the kernel and debug logs, do you want me to send them after the
>> problem arises?
>>
> Nope. Set the debug mask at the beginning. And also please confirm if the
> problem can be reproducible in open authentication.
>
>
> Please check whether disabling ANI is improving the situation or not.
>
> echo 0 >/sys/kernel/debug/ieee80211/phy*/ath9k/ani
>
> -Rajkumar
>
-------------- next part --------------
00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM Controller [8086:0154] (rev 09)
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port [8086:0151] (rev 09)
00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04)
00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 [8086:1e3a] (rev 04)
00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04)
00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller [8086:1e20] (rev 04)
00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 [8086:1e10] (rev c4)
00:1c.1 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 [8086:1e12] (rev c4)
00:1c.2 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 3 [8086:1e14] (rev c4)
00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04)
00:1f.0 ISA bridge [0601]: Intel Corporation HM76 Express Chipset LPC Controller [8086:1e59] (rev 04)
00:1f.2 SATA controller [0106]: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] [8086:1e03] (rev 04)
00:1f.3 SMBus [0c05]: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller [8086:1e22] (rev 04)
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] [1002:6841]
01:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Turks/Whistler HDMI Audio [Radeon HD 6000 Series] [1002:aa90]
07:00.0 Network controller [0280]: Qualcomm Atheros AR9485 Wireless Network Adapter [168c:0032] (rev 01)
08:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5209 PCI Express Card Reader [10ec:5209] (rev 01)
09:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 07)
next prev parent reply other threads:[~2014-05-15 17:44 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 13:46 [ath9k-devel] Weird Atheros 9485 http connecting problems Arkh4mKn1ght
2014-05-15 12:37 ` Rajkumar Manoharan
2014-05-15 12:57 ` Arkh4mKn1ght
2014-05-15 16:06 ` Rajkumar Manoharan
2014-05-15 17:44 ` Arkh4mKn1ght [this message]
2014-05-15 23:02 ` Arkh4mKn1ght
2014-05-16 9:06 ` Rajkumar Manoharan
2014-05-16 12:22 ` Arkh4mKn1ght
2014-05-18 23:51 ` Adrian Chadd
2014-05-19 0:29 ` Arkh4mKn1ght
2014-05-19 6:10 ` Adrian Chadd
2014-05-19 13:12 ` Arkh4mKn1ght
2014-05-19 6:29 ` Rajkumar Manoharan
2014-05-19 13:12 ` Arkh4mKn1ght
2014-05-19 14:42 ` Rajkumar Manoharan
2014-05-20 0:32 ` Adrian Chadd
2014-05-20 14:34 ` Arkh4mKn1ght
2014-05-21 14:37 ` Arkh4mKn1ght
2014-05-21 14:59 ` Rajkumar Manoharan
2014-05-21 15:10 ` Arkh4mKn1ght
2014-05-21 19:04 ` Kyle Bassett
2014-05-21 20:51 ` Arkh4mKn1ght
2014-05-21 20:10 ` Adrian Chadd
2014-05-21 20:52 ` Arkh4mKn1ght
2014-05-21 22:05 ` Adrian Chadd
2014-05-23 0:50 ` Arkh4mKn1ght
2014-05-26 18:06 ` Oskar Kossuth
2014-05-27 11:43 ` Rajkumar Manoharan
2014-05-27 13:52 ` Arkh4mKn1ght
2014-05-21 15:39 ` [ath9k-devel] Weird Atheros 9485 http connecting problems - Sniffer Capture Arkh4mKn1ght
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=5374FD12.6030307@gmail.com \
--to=arkh4mkn1ght@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.