From: Dan Williams <dcbw@redhat.com>
To: Pierre Frenkiel <pierre.frenkiel@apc.univ-paris7.fr>
Cc: linux-wireless@vger.kernel.org
Subject: Re: ath5k phy0: noise floor calibration timeout
Date: Fri, 18 Apr 2008 09:56:28 -0400 [thread overview]
Message-ID: <1208526988.9388.12.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0804181435480.16108@apcnb28.in2p3.fr>
On Fri, 2008-04-18 at 14:51 +0200, Pierre Frenkiel wrote:
> hi,
> I have a 3-com PCCARD, with the AR5413 chipset
> I installed 2 days ago compat-wireless-2.6.tar.bz2, on Ubuntu Gutsy,
> and everything seemed to work.
> I just had in the log 2 or 3 messages:
>
> ath5k phy0: noise floor calibration timeout
>
> but yesterday, when rebooting, I got a huge number of such messages(more
> than 100 in the log file), with also
>
> ath5k phy0: ath5k_chan_set: unable to reset channel
> ath0: failed to set freq to 2422 MHz for scan
> ath0: failed to restore operational channel after scan
I also get this all the time with a 5006E, and ath5k takes quite a lot
(30%) of CPU most of the time. Haven't tried to track it down yet.
Anyone have ideas about the root cause of the problem?
Dan
> and the boot froze. I then removed my PCCARD,
> and after poweroff/poweron, I could boot normally.
>
> It seems to be fixed now, as I have no more this problem after
> re-inserting the card.
> But as I did nothing, I would like to know what might happen:
> If this happened once, there is no reason why this would not happen an
> other time.
>
> Pierre
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-04-18 13:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 12:51 ath5k phy0: noise floor calibration timeout Pierre Frenkiel
2008-04-18 13:56 ` Dan Williams [this message]
2008-04-18 14:51 ` Nick Kossifidis
2008-04-18 14:59 ` Dan Williams
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=1208526988.9388.12.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pierre.frenkiel@apc.univ-paris7.fr \
/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).