All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arkh4mKn1ght <arkh4mkn1ght@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Weird Atheros 9485 http connecting problems
Date: Tue, 20 May 2014 11:34:32 -0300	[thread overview]
Message-ID: <537B67F8.8010500@gmail.com> (raw)
In-Reply-To: <CAJ-VmokVuQTig--V4dCg71BzW_oOnekepr4PvO_5VBBrdY2L7w@mail.gmail.com>

Ok bad news, the issue happened again both with ASPM disabled on the 
root complex and atheros card and with powersave on and off. I will test 
the patch that rajkumar sent me and i will be back to you guys.

Greetings

Oskar


On 05/19/2014 09:32 PM, Adrian Chadd wrote:
> Right;
>
>> powersave is nothing but 802.11 protocol implementation to put the
>> station into network sleep when it is idle and wake it up whenever it is
>> active. IIRC it is not related to ASPM. So yes powersave would work event
>> without ASPM.
>>
>> Since the issue is happending only when ASPM is enabled, please test the
>> patch with ASPM.
> Just to be clear - the powersave support when loading ath9k also puts
> the MAC/PHY to sleep and wakes it up as appropriate.
>
> You're seeing 0xdeadc0de which the internal AHB glue reports if
> there's a transaction timeout (ie, the MAC/PHY is asleep or powered
> down when you went to access it.)
>
> ASPM has to do with the PHYs at both ends being awake (or not.) I
> think you'd either trigger some pcie error or read 0xffffffff if
> things were screwed up there.
>
> So I'd try with ASPM enabled/disabled as well as ps_enable on or off.
> It could be an interplay between the two as well.
>
>
> -a
>

  reply	other threads:[~2014-05-20 14:34 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 [this message]
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=537B67F8.8010500@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.