From: Luis R. Rodriguez <lrodriguez@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] AR5008 hanging computer
Date: Mon, 22 Feb 2010 10:34:18 -0800 [thread overview]
Message-ID: <20100222183418.GH2528@tux> (raw)
In-Reply-To: <20100222202457.38761sxhi60szth5@ncircle.nullnet.fi>
On Mon, Feb 22, 2010 at 10:24:57AM -0800, Tomi Orava wrote:
> Quoting "Luis R. Rodriguez" <mcgrof@gmail.com>:
>
> > On Sun, Feb 21, 2010 at 12:31 AM, Tomi Orava
> > <Tomi.Orava@ncircle.nullnet.fi> wrote:
> >> On 02/18/2010 11:58 PM, Mark Sutton wrote:
> >>> On Thu, Feb 18, 2010 at 12:31:26PM -0800, Mark Sutton wrote:
> >>>> Hi,
> >>>> ? ? ?I have this problem as well.
> >>>> Hardware is:
> >>>>
> >>>> Atheros Communications Inc. AR5008
> >>>> Atheros AR5416 MAC/BB Rev:2 AR5133 RF Rev:81
> >>>>
> >>>> Kernel:Linux 2.6.32.7 #2 PREEMPT Thu Feb 4 14:19:02 PST 2010 i686
> >>>> GNU/Linux
>
> <snip>
>
> > Karmic uses 2.6.31 which has already reached the end of its
> > development. You will no longer see stable kernel releases based on
> > 2.6.31.y kernels so best is to upgrade. ath9k had a large number of
> > patches which did not get merged into 2.6.31 [1] which should have,
> > which is why we worked hard for 2.6.32 to ensure all regressions/fixes
> > are propagated to stable.
> >
> > Karmic ships lbm though and that uses the 802.11 bits from 2.6.32
> > which should be good.
> >
> > [1]
> > http://bombadil.infradead.org/~mcgrof/patches/ath9k/fixes-not-in-2.6.31-for-ath9k.txt
>
> Unfortunately, I completely forgot to mention the very important fact that
> in my understanding the "standard" karmic kernels ie. 2.6.31.x worked
> quite ok compared to the compat-wireless versions included in
> linux-backports-karmic etc etc. In other words, my problem tends to be
> that the latest
> ath9k versions are having some problems, while the older 2.6.31 seem to
> be working without hangs in my case (not counting connection drops
> every once in a while). Sorry, for turning this upside down.
>
> Although, I've been way too busy with other important matters, I'll
> try to find the last "properly" working kernel by using the GIT kernel
> versions, so that I can be sure about the used versions.
> Unfortunately, this laptop is quite slow and the hang doesn't happen
> immediately (might take 1-2 days, but still it will always happen with
> newer versions of the ath9k drivers). Anyway, it's very good to know
> if these problems are more common among cards based on these chips or
> is this just a rare case.
>
> This particular card was sold as D-Link DWA-645.
>
> I'll report back after I've done some more testing in order to get
> more facts about different ath9k driver versions.
You'll want to read:
http://wireless.kernel.org/en/users/Documentation/Reporting_bugs
http://wireless.kernel.org/en/users/Documentation/Fix_Propagation
That should get you to test and report against the right thing.
Luis
next prev parent reply other threads:[~2010-02-22 18:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 20:31 [ath9k-devel] AR5008 hanging computer Mark Sutton
2010-02-18 21:58 ` Mark Sutton
2010-02-19 1:36 ` Pavel Roskin
2010-03-05 23:04 ` Mark Sutton
2010-03-11 7:56 ` Pavel Roskin
2010-03-11 10:38 ` Peter Stuge
2010-04-17 17:49 ` Tomi Orava
2010-02-21 8:31 ` Tomi Orava
2010-02-22 18:02 ` Luis R. Rodriguez
2010-02-22 18:24 ` Tomi Orava
2010-02-22 18:34 ` Luis R. Rodriguez [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-02-12 15:25 James Grossmann
2010-02-12 22:53 ` Pavel Roskin
2010-02-12 23:35 ` James Grossmann
2010-02-12 23:42 ` hong zhang
2010-02-15 7:03 ` Pavel Roskin
[not found] ` <167ae39b1002152030s170128a0j362e7e9c61a4af42@mail.gmail.com>
[not found] ` <1266296860.17808.2.camel@mj>
2010-02-16 23:54 ` James Grossmann
2010-02-17 17:47 ` Pavel Roskin
2010-02-17 17:56 ` hong zhang
2010-02-17 18:15 ` Pavel Roskin
2010-02-23 6:45 ` James Grossmann
2010-02-23 7:02 ` James Grossmann
2010-03-11 8:01 ` Pavel Roskin
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=20100222183418.GH2528@tux \
--to=lrodriguez@atheros.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.