* getting "ath5k phy0: noise floor calibration timeout"
@ 2009-09-21 7:02 Holger Schurig
2009-09-22 23:29 ` Dan Williams
0 siblings, 1 reply; 5+ messages in thread
From: Holger Schurig @ 2009-09-21 7:02 UTC (permalink / raw)
To: linux-wireless; +Cc: Luis R. Rodriguez
I kept my laptop the week-end on. The devices was unused during
that time. I got a bunch output into my syslog:
Sep 18 17:30:03 laptop kernel: ##HS cfg80211_bss_expire:129 0
Sep 18 17:30:03 laptop kernel: ##HS expire 00:1b:d4:44:35:90
Sep 18 17:30:03 laptop kernel: ##HS expire 00:13:19:80:da:30
Sep 18 17:30:03 laptop kernel: ##HS expire 00:1b:53:11:dc:40
Sep 18 18:15:04 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
Sep 18 18:26:12 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
Sep 19 11:12:09 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
Sep 19 11:29:36 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
Sep 19 11:47:57 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
Sep 19 12:31:05 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
Sep 19 13:06:42 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
Sep 19 14:07:51 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
Sep 19 14:10:31 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
Sep 19 14:12:00 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
Sep 20 00:06:20 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
Sep 20 07:46:24 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
Sep 20 16:36:43 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
Sep 20 16:47:43 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
Sep 20 16:52:43 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
Sep 20 17:01:43 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
Sep 20 20:07:57 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
Sep 21 06:22:55 laptop last message repeated 2 times
Sep 21 06:26:00 laptop last message repeated 2 times
Sep 21 06:28:26 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
Sep 21 06:33:14 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
Sep 21 06:38:34 laptop last message repeated 2 times
Sep 21 06:40:21 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
Sep 21 06:41:40 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
Sep 21 06:43:44 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
Sep 21 06:55:17 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
Sep 21 07:03:10 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
Sep 21 07:04:35 laptop last message repeated 2 times
Sep 21 07:06:11 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
Sep 21 07:16:58 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
Sep 21 07:21:37 laptop last message repeated 2 times
Is this anything where I should care? Or can I just
ignore that? If the latter is the case, should I add a
patch that only three consecutive calibration timeouts
produce a message, so that the log doesn't get "spammed" ?
--
http://www.holgerschurig.de
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: getting "ath5k phy0: noise floor calibration timeout"
2009-09-21 7:02 getting "ath5k phy0: noise floor calibration timeout" Holger Schurig
@ 2009-09-22 23:29 ` Dan Williams
2009-09-23 7:05 ` Holger Schurig
2009-09-24 8:15 ` Holger Schurig
0 siblings, 2 replies; 5+ messages in thread
From: Dan Williams @ 2009-09-22 23:29 UTC (permalink / raw)
To: Holger Schurig; +Cc: linux-wireless, Luis R. Rodriguez
On Mon, 2009-09-21 at 09:02 +0200, Holger Schurig wrote:
> I kept my laptop the week-end on. The devices was unused during
> that time. I got a bunch output into my syslog:
I get that all the time, and have since 2.6.27 or earlier. If it's a
real bug, we should fix it, but if it's just an informational message,
maybe we should silence it?
Dan
> Sep 18 17:30:03 laptop kernel: ##HS cfg80211_bss_expire:129 0
> Sep 18 17:30:03 laptop kernel: ##HS expire 00:1b:d4:44:35:90
> Sep 18 17:30:03 laptop kernel: ##HS expire 00:13:19:80:da:30
> Sep 18 17:30:03 laptop kernel: ##HS expire 00:1b:53:11:dc:40
> Sep 18 18:15:04 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
> Sep 18 18:26:12 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
> Sep 19 11:12:09 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
> Sep 19 11:29:36 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
> Sep 19 11:47:57 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
> Sep 19 12:31:05 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
> Sep 19 13:06:42 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
> Sep 19 14:07:51 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
> Sep 19 14:10:31 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
> Sep 19 14:12:00 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
> Sep 20 00:06:20 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
> Sep 20 07:46:24 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
> Sep 20 16:36:43 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
> Sep 20 16:47:43 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
> Sep 20 16:52:43 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
> Sep 20 17:01:43 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
> Sep 20 20:07:57 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
> Sep 21 06:22:55 laptop last message repeated 2 times
> Sep 21 06:26:00 laptop last message repeated 2 times
> Sep 21 06:28:26 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
> Sep 21 06:33:14 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
> Sep 21 06:38:34 laptop last message repeated 2 times
> Sep 21 06:40:21 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
> Sep 21 06:41:40 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
> Sep 21 06:43:44 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
> Sep 21 06:55:17 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
> Sep 21 07:03:10 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
> Sep 21 07:04:35 laptop last message repeated 2 times
> Sep 21 07:06:11 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
> Sep 21 07:16:58 laptop kernel: ath5k phy0: noise floor calibration timeout (2412MHz)
> Sep 21 07:21:37 laptop last message repeated 2 times
>
> Is this anything where I should care? Or can I just
> ignore that? If the latter is the case, should I add a
> patch that only three consecutive calibration timeouts
> produce a message, so that the log doesn't get "spammed" ?
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: getting "ath5k phy0: noise floor calibration timeout"
2009-09-22 23:29 ` Dan Williams
@ 2009-09-23 7:05 ` Holger Schurig
2009-09-24 8:15 ` Holger Schurig
1 sibling, 0 replies; 5+ messages in thread
From: Holger Schurig @ 2009-09-23 7:05 UTC (permalink / raw)
To: Dan Williams; +Cc: linux-wireless, Luis R. Rodriguez
> I get that all the time, and have since 2.6.27 or earlier. If it's a
> real bug, we should fix it, but if it's just an informational message,
> maybe we should silence it?
This is what I'd like to know: if it's a real but or not.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: getting "ath5k phy0: noise floor calibration timeout"
2009-09-22 23:29 ` Dan Williams
2009-09-23 7:05 ` Holger Schurig
@ 2009-09-24 8:15 ` Holger Schurig
2009-09-25 14:39 ` Bob Copeland
1 sibling, 1 reply; 5+ messages in thread
From: Holger Schurig @ 2009-09-24 8:15 UTC (permalink / raw)
To: Dan Williams; +Cc: linux-wireless, Luis R. Rodriguez
> I get that all the time, and have since 2.6.27 or earlier. If
> it's a real bug, we should fix it, but if it's just an
> informational message, maybe we should silence it?
On ath5k-devel, there was a mail "[ath5k-devel] [RFC/RFT] ath5k:
use noise calibration from madwifi hal" from Bob Copeland.
Part of the patch is "- we do not complain if NF calibration
isn't complete, instead we keep the last read value.".
I now applied this patch, the message is gone and the device
seems to work quite nicely. Maybe it should still emit a warning
if there are n consecutive calibration errors, but for now I'm
happy.
--
http://www.holgerschurig.de
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: getting "ath5k phy0: noise floor calibration timeout"
2009-09-24 8:15 ` Holger Schurig
@ 2009-09-25 14:39 ` Bob Copeland
0 siblings, 0 replies; 5+ messages in thread
From: Bob Copeland @ 2009-09-25 14:39 UTC (permalink / raw)
To: Holger Schurig; +Cc: Dan Williams, linux-wireless, Luis R. Rodriguez
On Thu, Sep 24, 2009 at 4:15 AM, Holger Schurig
<hs4233@mail.mn-solutions.de> wrote:
> On ath5k-devel, there was a mail "[ath5k-devel] [RFC/RFT] ath5k:
> use noise calibration from madwifi hal" from Bob Copeland.
>
> Part of the patch is "- we do not complain if NF calibration
> isn't complete, instead we keep the last read value.".
Yeah, NF calibration timeout happens all the time (also in
madwifi/ath9k) so we should just silence it. At best, it indicates
a problem that the user can't do anything about; at worst, it
leads to bug reports accusing the NF calibration of wholly unrelated
things.
I really should finish testing and push that patch, real life has
just been in the way lately.
--
Bob Copeland %% www.bobcopeland.com
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2009-09-25 14:39 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-09-21 7:02 getting "ath5k phy0: noise floor calibration timeout" Holger Schurig
2009-09-22 23:29 ` Dan Williams
2009-09-23 7:05 ` Holger Schurig
2009-09-24 8:15 ` Holger Schurig
2009-09-25 14:39 ` Bob Copeland
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox