From: Richard Zidlicky <rz@linux-m68k.org>
To: Bob Copeland <me@bobcopeland.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: 2.6.31.[12] ath5k regression
Date: Mon, 12 Oct 2009 00:00:02 +0200 [thread overview]
Message-ID: <20091011220002.GA11603@linux-m68k.org> (raw)
In-Reply-To: <20091011133010.GA21494@hash.localnet>
On Sun, Oct 11, 2009 at 09:30:10AM -0400, Bob Copeland wrote:
> On Sun, Oct 11, 2009 at 02:26:16PM +0200, Richard Zidlicky wrote:
> > thanks, compiling it right now. Not quite sure - which version of this
> > > > - ret = ath5k_hw_reset(ah, sc->opmode, sc->curchan, true);
> > > > + ret = ath5k_hw_reset(ah, sc->opmode, sc->curchan, chan != NULL);
> >
> > is it supposed to be tested with?
>
> The "chan != NULL" case. The patch should apply against latest
> wireless-testing (but will probably work with linus-2.6).
so the results are same like before. The printk message came once only,
I will try to gather more debug info tomorrow.
It is striking that after running the not working driver the machine requires
a power-off reboot to have working ath5k again.
Richard
next prev parent reply other threads:[~2009-10-11 22:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-21 13:49 kernel crashes, 2.6.30, rt2x00, ath5k, ieee80211_get_*_rate, automatic rate control Richard Zidlicky
2009-06-21 18:04 ` Bob Copeland
2009-06-21 20:38 ` Richard Zidlicky
2009-06-22 20:15 ` Richard Zidlicky
2009-06-23 17:46 ` Richard Zidlicky
2009-06-23 20:25 ` Bob Copeland
2009-06-25 8:36 ` Richard Zidlicky
2009-07-05 12:31 ` Bob Copeland
2009-09-28 22:23 ` ath5k, wifi enable hotkeys Richard Zidlicky
2009-10-09 14:39 ` 2.6.31.[12] ath5k regression Richard Zidlicky
2009-10-10 12:58 ` Bob Copeland
2009-10-10 13:31 ` Bob Copeland
2009-10-11 12:26 ` Richard Zidlicky
2009-10-11 13:30 ` Bob Copeland
2009-10-11 22:00 ` Richard Zidlicky [this message]
2009-10-11 22:23 ` Bob Copeland
2009-10-12 20:23 ` Richard Zidlicky
2009-10-12 23:54 ` Bob Copeland
2009-10-13 19:37 ` Richard Zidlicky
2009-12-06 9:49 ` Richard Zidlicky
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=20091011220002.GA11603@linux-m68k.org \
--to=rz@linux-m68k.org \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.com \
/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;
as well as URLs for NNTP newsgroup(s).