DoRxHighPower(): RF_ZEBRA, Upper Threshold: 99 LOWER Threshold: 70

Bug #261098 reported by Markus Korn
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned
Hardy
Invalid
Low
Unassigned

Bug Description

My kern.log has thousands of lines like:

markus@thekorn:~$ tail /var/log/kern.log
Aug 25 13:08:01 thekorn kernel: [14291.454024] DoRxHighPower(): RF_ZEBRA, Upper Threshold: 99 LOWER Threshold: 70
Aug 25 13:08:03 thekorn kernel: [14293.450780] DoRxHighPower(): RF_ZEBRA, Upper Threshold: 99 LOWER Threshold: 70
Aug 25 13:08:05 thekorn kernel: [14295.447789] DoRxHighPower(): RF_ZEBRA, Upper Threshold: 99 LOWER Threshold: 70
Aug 25 13:08:07 thekorn kernel: [14297.444291] DoRxHighPower(): RF_ZEBRA, Upper Threshold: 99 LOWER Threshold: 70
Aug 25 13:08:09 thekorn kernel: [14299.441050] DoRxHighPower(): RF_ZEBRA, Upper Threshold: 99 LOWER Threshold: 70
Aug 25 13:08:11 thekorn kernel: [14301.437805] DoRxHighPower(): RF_ZEBRA, Upper Threshold: 99 LOWER Threshold: 70
Aug 25 13:08:13 thekorn kernel: [14303.438548] DoRxHighPower(): RF_ZEBRA, Upper Threshold: 99 LOWER Threshold: 70
Aug 25 13:08:15 thekorn kernel: [14305.431328] DoRxHighPower(): RF_ZEBRA, Upper Threshold: 99 LOWER Threshold: 70
Aug 25 13:08:17 thekorn kernel: [14307.428067] DoRxHighPower(): RF_ZEBRA, Upper Threshold: 99 LOWER Threshold: 70
Aug 25 13:08:19 thekorn kernel: [14309.424821] DoRxHighPower(): RF_ZEBRA, Upper Threshold: 99 LOWER Threshold: 70

I'm not sure if it indicates a bug, or if it's just debug output but at least it is confusing me. I'm also not sure which kind of hardware/driver etc. causes this messages, I'm happy to give you more information you need

markus@thekorn:~$ lsb_release -rd
Description: Ubuntu 8.04.1
Release: 8.04
markus@thekorn:~$ uname -a
Linux thekorn 2.6.24-21-generic #1 SMP Tue Aug 12 13:03:01 UTC 2008 x86_64 GNU/Linux

I'm not sure if this is related, but I'm not using ndiswrapper, and I'm using a realtek wifi card

markus@thekorn:~$ lsmod|grep rtl
ieee80211_rtl 85896 1 r8187
ieee80211_crypt_tkip_rtl 13056 1 ieee80211_rtl
ieee80211_crypt_wep_rtl 7680 2 ieee80211_rtl
ieee80211_crypt_ccmp_rtl 9088 1 ieee80211_rtl
ieee80211_crypt_rtl 7944 4 ieee80211_rtl,ieee80211_crypt_tkip_rtl,ieee80211_crypt_wep_rtl,ieee80211_crypt_ccmp_rtl

Markus

Tags: cft-2.6.27
Revision history for this message
radi2k (radiation-uc) wrote :

same problem here:
Aug 25 14:52:05 radiation kernel: [14610.439834] DoRxHighPower(): RF_ZEBRA, Upper Threshold: 99 LOWER Threshold: 70
Aug 25 14:52:07 radiation kernel: [14612.438012] DoRxHighPower(): RF_ZEBRA, Upper Threshold: 99 LOWER Threshold: 70
Aug 25 14:52:09 radiation kernel: [14614.436190] DoRxHighPower(): RF_ZEBRA, Upper Threshold: 99 LOWER Threshold: 70

this message appears every two seconds in syslog/kernel log. if someone needs any further informations about hardware contact me.

uname -a
Linux radiation 2.6.24-21-generic #1 SMP Tue Aug 12 13:37:22 UTC 2008 i686 GNU/Linux

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
radi2k (radiation-uc) wrote :

Stupid question, but how can i try the new kernel without using the LiveCD? I'd like to help you finding a solution, but i cannot find the package via synaptic. Some little tip would be nice :)

Revision history for this message
Markus Korn (thekorn) wrote :

I've no more messages like this on intrepid, but instead there is a lot like:

$ tail /var/log/syslog
Aug 29 17:55:11 ubuntu NetworkManager: <debug> [1220032511.647935] periodic_update(): Roamed from BSSID 00:0F:B5:E5:C7:68 (korn_home) to (none) ((none))
Aug 29 17:55:17 ubuntu NetworkManager: <debug> [1220032517.651959] periodic_update(): Roamed from BSSID (none) ((none)) to 00:0F:B5:E5:C7:68 (korn_home)
Aug 29 17:57:11 ubuntu NetworkManager: <debug> [1220032631.723935] periodic_update(): Roamed from BSSID 00:0F:B5:E5:C7:68 (korn_home) to (none) ((none))
Aug 29 17:57:17 ubuntu NetworkManager: <debug> [1220032637.727959] periodic_update(): Roamed from BSSID (none) ((none)) to 00:0F:B5:E5:C7:68 (korn_home)
Aug 29 17:59:11 ubuntu NetworkManager: <debug> [1220032751.803929] periodic_update(): Roamed from BSSID 00:0F:B5:E5:C7:68 (korn_home) to (none) ((none))
Aug 29 17:59:17 ubuntu NetworkManager: <debug> [1220032757.807920] periodic_update(): Roamed from BSSID (none) ((none)) to 00:0F:B5:E5:C7:68 (korn_home)
Aug 29 18:01:11 ubuntu NetworkManager: <debug> [1220032871.883919] periodic_update(): Roamed from BSSID 00:0F:B5:E5:C7:68 (korn_home) to (none) ((none))
Aug 29 18:01:17 ubuntu NetworkManager: <debug> [1220032877.887922] periodic_update(): Roamed from BSSID (none) ((none)) to 00:0F:B5:E5:C7:68 (korn_home)
Aug 29 18:03:11 ubuntu NetworkManager: <debug> [1220032991.963926] periodic_update(): Roamed from BSSID 00:0F:B5:E5:C7:68 (korn_home) to (none) ((none))
Aug 29 18:03:17 ubuntu NetworkManager: <debug> [1220032997.968458] periodic_update(): Roamed from BSSID (none) ((none)) to 00:0F:B5:E5:C7:68 (korn_home)

I'm not sure if this related or totally different, tested in a live session.

$ uname -a
Linux ubuntu 2.6.27-1-generic #1 SMP Sat Aug 23 23:19:01 UTC 2008 x86_64 GNU/Linux

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Guys,

@radi2k - If you do not want to test via a LiveCD you'd need to enable the Intrepid repository in order to install the 2.6.27 kernel.

@Markus - Thanks for testing and the update. I'm assuming with Hardy you had linux-ubuntu-modules installed? The reason I ask is that I'm only able to find this message existing in the hardy-lum git tree:

ogasawara@yoji:~/ubuntu-hardy-lum$ grep -rn "DoRxHighPower" *

ubuntu/wireless/rtl8187-usb/rtl8187/r8180_dm.c:344: printk("DoRxHighPower(): RF_ZEBRA, Upper Threshold: %d LOWER Threshold: %d\n",

Here's a link to the actual file:

http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-hardy-lum.git;a=blob;f=ubuntu/wireless/rtl8187-usb/rtl8187/r8180_dm.c;h=994493732de899c01f25cfca258151bb058f81ec;hb=HEAD

Looking at the code it just looks like a random printk was inadvertantly left in the code. You'll notice it looks like the majority of the other printk's were indeed commented out. I assume you saw no other issues with this driver - ie wifi is working for you otherwise?

Beginning with Intrepid however, linux-ubuntu-modules was merged with the linux kernel source. I quickly searched the intrepid kernel git tree but was unable to find this same message:

ogasawara@yoji:~/ubuntu-intrepid$ grep -rn "DoRxHighPower" *

ogasawara@yoji:~/ubuntu-intrepid$

Then searching for r8180_dm.c indeed shows the file no longer exists in Intrepid:

ogasawara@yoji:~/ubuntu-intrepid$ find -name "r8180_dm.c"
ogasawara@yoji:~/ubuntu-intrepid$

So it makes sense that the message is gone now when you've tested 2.6.27.

Regarding the new messages you are seeing, based on the above information I'd say they are unrelated to this specific bug and likely looks to be an issue with NetworkManager. Alexander did put out a call for testing NetworkManager 0.7 https://lists.ubuntu.com/archives/ubuntu-devel-announce/2008-August/000467.html so you may want to seach some of the newer Network Manager bug reports to see if this may already be reported.

Regarding this specific bug against Hardy let me know if you'd like me to try to get this pushed through the SRU process. It seems like it would be a simple one line fix of commenting out the offending printk. Thanks.

Revision history for this message
Markus Korn (thekorn) wrote :

Hi Leann,
thanks for your detailed follow-up.

This `printk("DoRxHighPower()....")` -issue looks like it's worse a SRU process, but IMO with a low priority as it does not really do any harm.

I'm going to do some tests with the recent alpha today and check wifi and NetworkManager again, but my feeling one week ago was that there is something wrong with the connection, I somehow lost connection periodically and had bad signal strength compared to the hardy installation on the same machine. But this seems to be not related to this bug.

Markus

Changed in linux:
status: New → Fix Released
assignee: nobody → ubuntu-kernel-team
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Revision history for this message
Julian Wiedmann (jwiedmann) wrote :

This release has reached end-of-life [0].

[0] https://wiki.ubuntu.com/Releases

Changed in linux (Ubuntu Hardy):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.