On Monday 17 December 2007 13:49:00 Robert Allerstorfer wrote:
> On Mon, 17 Dec 2007, 11:00 GMT+01 Michael Buesch wrote:
> 
> > On Monday 17 December 2007 02:46:29 Robert Allerstorfer wrote:
> >> The strange thing is that the "b43-phy0 debug: !WARNING!..." line
> >> disappeared from the dmesg output after I replaced ssb.ko by a
> >> self-compiled version (and - of course - rebooted).
> 
> > Which version of ssb were you using before and which one are you using now?
> > Can you make a diff -u?
> 
> Both ssb.ko binaries have been built from the same source, so their
> versions must be the same. However, I have now found that replacing
> ssb.ko had nothing to do with the b43-phy0 debug warning. After
> rebooting several times, the output of "dmesg | egrep
> 'b43|ssb|wlan0|wmaster0'" sometimes contains such a warning line and
> sometimes it doesn't.

Expected. So try the workaround I suggested earlier.

> If it is there, the number NN of the "cur=NN" 
> part can differ. I have seen cur=42 or cur=38 so far:
> 
> b43-phy0 debug: !WARNING! Idle-TSSI phy->cur_idle_tssi measuring
> failed. (cur=42, tgt=62). Disabling TX power adjustment. 
> 
> b43-phy0 debug: !WARNING! Idle-TSSI phy->cur_idle_tssi measuring
> failed. (cur=38, tgt=62). Disabling TX power adjustment.
> 
> Why can this warning be different or ebven absent after each reboot?

Because the "cur" value is a measured value which can have jitter.

-- 
Greetings Michael.
_______________________________________________
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Reply via email to