From: Arkh4mKn1ght <arkh4mkn1ght@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Weird Atheros 9485 http connecting problems
Date: Wed, 21 May 2014 17:51:44 -0300 [thread overview]
Message-ID: <537D11E0.7000501@gmail.com> (raw)
In-Reply-To: <CAM9Pttho0c=J+=8rUeE6-L3J3QmcA7+vc-AbNuxG+qXG+bWBWA@mail.gmail.com>
Yeah i do have one but i will test it after i discard that this problem
is related somehow to hibernating the laptop
Greetings
Oskar
On 05/21/2014 04:04 PM, Kyle Bassett wrote:
> Hi Oskar,
>
> Do you have a wired ethernet connection or a separate usb wireless
> adapter? I am curious to know if your problem still occurs while
> using a different interface. It would help isolate where this problem
> is occuring.
>
>
> On Wed, May 21, 2014 at 11:10 AM, Arkh4mKn1ght <arkh4mkn1ght@gmail.com
> <mailto:arkh4mkn1ght@gmail.com>> wrote:
>
> Hi rajkumar
>
> I dont know if this only happens when resuming from hibernate, it was
> just a thought that ocurred to me today. I will test again without
> hibernating to see if this happens again.
> I dont use any firewall on the laptop, so iptables -F is pointless.
> Ping latency times are good when the problem is ongoing.
> I will take a sniffer capture and send it back to you.
>
> Thanks for your help
>
> Oskar
>
> On 05/21/2014 11:59 AM, Rajkumar Manoharan wrote:
> > On Wed, May 21, 2014 at 11:37:36AM -0300, Arkh4mKn1ght wrote:
> >> Ok i tried the patch but the issue happened again :(
> >>
> >> After resuming my laptop from hibernation i saw in
> >> /var/log/kernel/errors.log these messages again:
> >>
> >> May 21 09:20:10 localhost kernel: mei_me 0000:00:16.0: suspend
> >> May 21 09:20:10 localhost kernel: ath: phy1: RX failed to go
> idle in 10 ms
> >> RXSM=0xdeadbeef
> >> May 21 09:20:10 localhost kernel: ath: phy1: DMA failed to stop
> in 10 ms
> >> AR_CR=0xdeadbeef AR_DIAG_SW=0xdeadbeef DMADBG_7=0xdeadbeef
> >> May 21 09:20:11 localhost kernel: dpm_run_callback():
> >> usb_dev_restore+0x0/0x20 [usbcore] returns -107
> >> May 21 09:20:11 localhost kernel: PM: Device 1-1 failed to
> restore async:
> >> error -107
> >>
> >> ASPM was disabled on root complex and atheros card.powersave
> was off.
> >> After 1 hour and 10 minutes of those messages that problem
> arise. I have
> >> noticed that the problem arises always after some time of
> resuming the
> >> laptop from hibernation.
> >>
> >> Its really odd, because when it does happen, browsing the web
> is painfully
> >> slow with the "connecting to domain.com..." message in the
> browser status
> >> bar... it does load the website but after some minutes..
> >> Meanwhile at the same time if i try to download a torrent using
> a bittorrent
> >> client i can do it without problems at full speed. If i pause
> the torrent,
> >> browsing websites still behaves slowly until i reboot the laptop.
> >>
> >> At first i thought that i have a defective atheros card, but
> why i can
> >> download torrents at full speed when this problem arises?
> >> What options do i have now? i have tested all combinations of ASPM
> >> enabled/disabled and powersave on/off.
> >>
> >> I have seen that there is a BIOS update for my laptop, but im
> unsure it
> >> could help for this at all (besides that i would have to
> install windows 8
> >> to install the friggin bios update)
> >>
> > Oskar,
> >
> > I am quite confused. Does the issue happen only after resume
> from hibernate?
> > Initially you havn't mentioned hibernate/resume. Are you able to
> > reproduce the issue without hibernating? Please flush ip table
> entries
> > and test.
> >
> > sudo iptables -F
> >
> > Can you please take a sniffer capture at the problematic time?
> Are you seeing huge
> > latency for ping (icmp)?
> >
> > -Rajkumar
> >
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org <mailto:ath9k-devel@lists.ath9k.org>
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20140521/a3fb3da7/attachment-0001.htm
next prev parent reply other threads:[~2014-05-21 20:51 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
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 [this message]
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=537D11E0.7000501@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox