linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Bob Copeland <me@bobcopeland.com>,
	Jiri Slaby <jirislaby@gmail.com>,
	Nick Kossifidis <mickflemm@gmail.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Ath5k on 2.6.32 suddenly fails
Date: Mon, 11 Jan 2010 23:36:49 +0100	[thread overview]
Message-ID: <201001112336.50125.mb@bu3sch.de> (raw)
In-Reply-To: <43e72e891001110811u49ddb2d5qbc7bef3a7e3e76d1@mail.gmail.com>

On Monday 11 January 2010 17:11:10 Luis R. Rodriguez wrote:
> >  11 Jan 10 11:11:28 quimby kernel: [163143.871947] ath5k phy0: failed to wakeup the MAC Chip
> 
> So to be clear, this seems to be a regression from 2.6.31 to 2.6.32.
> Can you confirm if ath5k worked in AP mode smoothly without this issue
> or was this a regression against some random wireless-testing based
> snapshit (which seems to be the case).

I don't know if it is a regression between .31 and .32.
Before I upgraded to .32, I used a .31 kernel, but with compat-wireless.
So I did not use the .31 wireless bits (there were some other breakages
that I did not track down further)

I was either using
compat-wireless-2009-09-28
or
compat-wireless-2009-10-28

I don't really remember exactly which one. I don't really know how to
find out, though.
I was using it for months and it was rock-stable.

> Michael, it seems this is not easy to reproduce but can you try the
> latest 2.6.33-rc code to see if the issue is also there? I can make a
> new compat-wireless snapshot for that soon if it helps.

Well, It's a real pain to do experiments on that machine, because
it is a production machine. Each failure will immediately result in people
yelling at me. :D So I don't feel to well running an rc kernel on it...

I currently have one and a half days of uptime. I think I'll first
continue running .32 to check whether it happens again or if this was just
some random hardware burp.
I think it should be likely to trigger again within one or two days, if this is a bug.

-- 
Greetings, Michael.

  parent reply	other threads:[~2010-01-11 22:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-10 10:52 Ath5k on 2.6.32 suddenly fails Michael Buesch
2010-01-11 16:11 ` Luis R. Rodriguez
2010-01-11 16:35   ` Larry Finger
2010-01-11 16:43     ` Luis R. Rodriguez
2010-01-11 22:36   ` Michael Buesch [this message]
2010-01-15 22:29     ` Michael Buesch
2010-01-15 22:40       ` Michael Buesch
2010-01-15 22:47         ` Luis R. Rodriguez
2010-01-15 22:50           ` Michael Buesch
2010-01-21 12:05             ` Michael Buesch
2010-01-21 15:57               ` Bob Copeland

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=201001112336.50125.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=jirislaby@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lrodriguez@atheros.com \
    --cc=me@bobcopeland.com \
    --cc=mickflemm@gmail.com \
    --cc=rjw@sisk.pl \
    /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).