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
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
2008/4/18, Dan Williams <[email protected]>:
> 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 [email protected]
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
It seems that sometimes noise floor calibration takes longer than
usual. I'll check it out and come up with a patch asap ;-)
--
GPG ID: 0xD21DB2DB
As you read this post global entropy rises. Have Fun ;-)
Nick
On Fri, 2008-04-18 at 17:51 +0300, Nick Kossifidis wrote:
> 2008/4/18, Dan Williams <[email protected]>:
> > 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 [email protected]
> > > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> > the body of a message to [email protected]
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
>
> It seems that sometimes noise floor calibration takes longer than
> usual. I'll check it out and come up with a patch asap ;-)
Happy to test patches. AR5413 802.11agb NIC (rev 01). 168c:001b,
subsys 10cf:1329.
Dan
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 [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html