Bug 666483 - nmcli with RaLink RT2860 causes lots of messages kernel: ===>rt_ioctl_giwscan. 2(2) BSS returned, data->length = 225
Summary: nmcli with RaLink RT2860 causes lots of messages kernel: ===>rt_ioctl_giwscan...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 13
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-31 02:28 UTC by Wendell Baker
Modified: 2011-02-23 14:18 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-02-23 14:18:52 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
from /var/log/messages; see all the messages; see circa 17:37 when I logged in to GNOME; see the messages start when I log out (125.10 KB, application/octet-stream)
2010-12-31 02:30 UTC, Wendell Baker
no flags Details
/etc/sysconfig/network-scripts/ifcfg-ra0 (387 bytes, application/octet-stream)
2010-12-31 02:30 UTC, Wendell Baker
no flags Details
adding 'set -xv' to ifcfg-ra0 and running 'sudo /sbin/ifup ra0 >& o.nmcli.out' (1.40 KB, application/octet-stream)
2010-12-31 02:31 UTC, Wendell Baker
no flags Details
lspci -vv (21.15 KB, application/octet-stream)
2010-12-31 02:32 UTC, Wendell Baker
no flags Details
/sbin/ifconfig -a (1.38 KB, application/octet-stream)
2010-12-31 02:32 UTC, Wendell Baker
no flags Details

Description Wendell Baker 2010-12-31 02:28:19 UTC
Description of problem:

The kernel (modules) are emitting messages once every two seconds, which is annoying there is some interaction between NetworkManager and kmod-rt2860.  The messages substantially go away when one logs in to a GNOME desktop (i.e. they become much much more infrequent).

The messages:
Dec 30 17:27:07 host2 kernel: ===>rt_ioctl_giwscan. 2(2) BSS returned, data->length = 225
Dec 30 17:27:09 host2 kernel: ===>rt_ioctl_giwscan. 3(3) BSS returned, data->length = 343
Dec 30 17:27:11 host2 kernel: ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 122
Dec 30 17:27:13 host2 kernel: ===>rt_ioctl_giwscan. 3(3) BSS returned, data->length = 343
Dec 30 17:27:15 host2 kernel: ===>rt_ioctl_giwscan. 2(2) BSS returned, data->length = 225
Dec 30 17:27:17 host2 kernel: ===>rt_ioctl_giwscan. 3(3) BSS returned, data->length = 343
Dec 30 17:27:19 host2 kernel: ===>rt_ioctl_giwscan. 3(3) BSS returned, data->length = 343
Dec 30 17:27:21 host2 kernel: ===>rt_ioctl_giwscan. 3(3) BSS returned, data->length = 343
Dec 30 17:27:23 host2 kernel: ===>rt_ioctl_giwscan. 3(3) BSS returned, data->length = 343
Dec 30 17:27:25 host2 kernel: ===>rt_ioctl_giwscan. 3(3) BSS returned, data->length = 343
Dec 30 17:27:27 host2 kernel: ===>rt_ioctl_giwscan. 3(3) BSS returned, data->length = 343
Dec 30 17:27:29 host2 kernel: ===>rt_ioctl_giwscan. 3(3) BSS returned, data->length = 343
Dec 30 17:27:31 host2 kernel: ===>rt_ioctl_giwscan. 2(2) BSS returned, data->length = 225
Dec 30 17:27:33 host2 kernel: ===>rt_ioctl_giwscan. 3(3) BSS returned, data->length = 343
Dec 30 17:27:35 host2 kernel: ===>rt_ioctl_giwscan. 3(3) BSS returned, data->length = 343
Dec 30 17:27:37 host2 kernel: ===>rt_ioctl_giwscan. 3(3) BSS returned, data->length = 343
Dec 30 17:27:39 host2 kernel: ===>rt_ioctl_giwscan. 3(3) BSS returned, data->length = 343
Dec 30 17:27:41 host2 kernel: ===>rt_ioctl_giwscan. 3(3) BSS returned, data->length = 343
Dec 30 17:27:43 host2 kernel: ===>rt_ioctl_giwscan. 3(3) BSS returned, data->length = 343
Dec 30 17:27:45 host2 kernel: ===>rt_ioctl_giwscan. 3(3) BSS returned, data->length = 343
Dec 30 17:27:47 host2 kernel: ===>rt_ioctl_giwscan. 2(2) BSS returned, data->length = 225

I'll include a portion of /var/log/messages separately.

Of note here is that the module "works" in the sense that it functions when one is logged in and NetworkManager is managing things.

I have two instance of this hardware configuration.
1) I am logged in one constantly ('host1' in this report) and it gives zero such messages
2. I am infrequently logged in on another one ('host2' in this report) and it is very chatty


These are wifi network devices so one might ask if the positioning of the machines has anything to do with it; the two machines sit 2 feet from each other on my desk; the AP is 20 feet away and equidistant +/-2ft from both.

The network interface (ra0) "works" to the extent that one can use it to ssh elsewhere. So the functionality doesn't seem to be diminished.  It is just chatty somehow on host2


NetworkManager the interface up properly if one is logged into GNOME; the messages in /var/log/messages substantially cease.

Trying to bring the interface up manually fails as:

$ sudo /sbin/ifup ra0
+ '[' true = true -a -n 70f4d245-6616-49ff-904b-70f716b9ee7d ']'
+ nmcli con up uuid 70f4d245-6616-49ff-904b-70f716b9ee7d
Error: No suitable device found: no device found for connection '2832 Emerson St acedia'.
+ exit 4

(I added set -xv to the scripts, full output included nearby as is the ifcfg-ra0)

Version-Release number of selected component (if applicable):

[host2 .. the chatty one]
$ rpm -q -a | grep -Ee '(kernel|kmod|2860|NetworkManager)' | sort
abrt-addon-kerneloops-1.1.14-1.fc13.i686
erlang-kernel-R13B-04.15.fc13.i686
kernel-2.6.33.6-147.2.4.fc13.i686
kernel-2.6.34.7-56.fc13.i686
kernel-2.6.34.7-61.fc13.i686
kernel-headers-2.6.34.7-61.fc13.i686
kernel-PAE-2.6.33.6-147.2.4.fc13.i686
kernel-PAE-2.6.34.7-56.fc13.i686
kernel-PAE-2.6.34.7-61.fc13.i686
kernel-PAE-devel-2.6.33.6-147.2.4.fc13.i686
kernel-PAE-devel-2.6.34.7-56.fc13.i686
kernel-PAE-devel-2.6.34.7-61.fc13.i686
kmod-rt2860-2.4.0.0-1.fc13.1.i686
kmod-rt2860-2.6.33.6-147.2.4.fc13.i686-2.3.0.0-1.fc13.6.i686
kmod-rt2860-2.6.33.6-147.2.4.fc13.i686.PAE-2.3.0.0-1.fc13.6.i686
kmod-rt2860-2.6.34.7-56.fc13.i686-2.4.0.0-1.fc13.i686
kmod-rt2860-2.6.34.7-56.fc13.i686.PAE-2.4.0.0-1.fc13.i686
kmod-rt2860-2.6.34.7-61.fc13.i686-2.4.0.0-1.fc13.1.i686
kmod-rt2860-2.6.34.7-61.fc13.i686.PAE-2.4.0.0-1.fc13.1.i686
kmod-rt2860-PAE-2.4.0.0-1.fc13.1.i686
libmikmod-3.2.0-11.beta2.fc13.i686
mikmod-3.2.2-10.beta1.fc11.i586
NetworkManager-0.8.1-9.git20100831.fc13.i686
NetworkManager-glib-0.8.1-9.git20100831.fc13.i686
NetworkManager-gnome-0.8.1-9.git20100831.fc13.i686
NetworkManager-openconnect-0.8.1-1.fc13.i686
NetworkManager-openvpn-0.8.1-1.fc13.i686
NetworkManager-pptp-0.8.1-1.fc13.i686
NetworkManager-vpnc-0.8.1-1.fc13.i686
rt2860-2.4.0.0-1.fc13.noarch
yum-NetworkManager-dispatcher-1.1.28-1.fc13.noarch


[host1 ... the silent one]
$ rpm -q -a | grep -Ee '(kernel|kmod|2860|NetworkManager)' | sort
abrt-addon-kerneloops-1.1.14-1.fc13.i686
erlang-kernel-R13B-04.15.fc13.i686
kernel-2.6.34.7-56.fc13.i686
kernel-2.6.34.7-61.fc13.i686
kernel-2.6.34.7-63.fc13.i686
kernel-headers-2.6.34.7-63.fc13.i686
kernel-PAE-2.6.34.7-56.fc13.i686
kernel-PAE-2.6.34.7-61.fc13.i686
kernel-PAE-2.6.34.7-63.fc13.i686
kernel-PAE-devel-2.6.34.7-56.fc13.i686
kernel-PAE-devel-2.6.34.7-61.fc13.i686
kernel-PAE-devel-2.6.34.7-63.fc13.i686
kmod-rt2860-2.4.0.0-1.fc13.2.i686
kmod-rt2860-2.6.34.7-56.fc13.i686-2.4.0.0-1.fc13.i686
kmod-rt2860-2.6.34.7-56.fc13.i686.PAE-2.4.0.0-1.fc13.i686
kmod-rt2860-2.6.34.7-61.fc13.i686-2.4.0.0-1.fc13.1.i686
kmod-rt2860-2.6.34.7-61.fc13.i686.PAE-2.4.0.0-1.fc13.1.i686
kmod-rt2860-2.6.34.7-63.fc13.i686-2.4.0.0-1.fc13.2.i686
kmod-rt2860-2.6.34.7-63.fc13.i686.PAE-2.4.0.0-1.fc13.2.i686
kmod-rt2860-PAE-2.4.0.0-1.fc13.2.i686
kmod-xtables-addons-2.6.34.7-63.fc13.i686-1.30-1.fc13.1.i686
libmikmod-3.2.0-11.beta2.fc13.i686
mikmod-3.2.2-10.beta1.fc11.i586
NetworkManager-0.8.1-10.git20100831.fc13.i686
NetworkManager-glib-0.8.1-10.git20100831.fc13.i686
NetworkManager-gnome-0.8.1-10.git20100831.fc13.i686
NetworkManager-openconnect-0.8.1-1.fc13.i686
NetworkManager-openvpn-0.8.1-1.fc13.i686
NetworkManager-pptp-0.8.1-1.fc13.i686
NetworkManager-vpnc-0.8.1-1.fc13.i686
rt2860-2.4.0.0-1.fc13.noarch

How reproducible:

100% ... I can login and logout and start and stop the chattiness.

Steps to Reproduce:
1. boot the machine (e.g. host2)
2. watch /var/log/messages (e.g. via another gnome-terminal over ssh)
3. log in to GNOME
4. watch /var/log/messages (e.g. via another gnome-terminal over ssh)
5. log out of GNOME
6. watch /var/log/messages (e.g. via another gnome-terminal over ssh)
7. try to start 
  
Actual results:

Messages in /var/log/messages
Dec 30 17:58:00 host2 kernel: ===>rt_ioctl_giwscan. 3(3) BSS returned, data->length = 343
Dec 30 17:58:02 host2 kernel: ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 118
Dec 30 17:58:04 host2 kernel: ===>rt_ioctl_giwscan. 2(2) BSS returned, data->length = 240
Dec 30 17:58:06 host2 kernel: ===>rt_ioctl_giwscan. 2(2) BSS returned, data->length = 240
Dec 30 17:58:08 host2 kernel: ===>rt_ioctl_giwscan. 2(2) BSS returned, data->length = 240
Dec 30 17:58:12 host2 kernel: ===>rt_ioctl_giwscan. 2(2) BSS returned, data->length = 221
Dec 30 17:58:14 host2 kernel: ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 118


Expected results:

I'd love to not see those messages in /var/log/messages

I'd love to be able to bring up ra0 when nobody is logged in.

Additional info:

The hardware (lspci -v output included nearby)

01:00.0 Network controller: RaLink RT2860
	Subsystem: Micro-Star International Co., Ltd. Device 6890
	Physical Slot: 32
	Flags: bus master, fast devsel, latency 0, IRQ 16
	Memory at feaf0000 (32-bit, non-prefetchable) [size=64K]
	Capabilities: <access denied>
	Kernel driver in use: rt2860
	Kernel modules: rt2860sta, rt2800pci


What other tickets mention this?

the bug https://bugzilla.redhat.com/show_bug.cgi?id=614592
mentions the error message containing "rt_ioctl_giwscan" but
that ticket reports on an X11 issue
<quote>
* /var/log/messages:
just contains "Aug  6 18:34:49 localhost kernel: ===>rt_ioctl_giwscan. 3(3) BSS
returned, data->length = 444" with different times repeated over the last hours
</quote>

These guys mention the message but the diagnosis from 2009 seems inconclusive
https://bugs.launchpad.net/archlinux/+source/linux/+bug/356807



What kernel?

$ uname -a
Linux host2 2.6.34.7-61.fc13.i686.PAE #1 SMP Tue Oct 19 04:24:06 UTC 2010 i686 i686 i386 GNU/Linux

Which modules?

$ find /lib -name '*2860*' | sort | xargs ls -ld
-rw-r--r--. 1 root root   8192 Aug 12 15:45 /lib/firmware/rt2860.bin
drwxr-xr-x. 2 root root   4096 Aug 22 08:56 /lib/modules/2.6.33.6-147.2.4.fc13.i686/extra/rt2860
-rw-r--r--. 1 root root 750288 Jul 27 04:18 /lib/modules/2.6.33.6-147.2.4.fc13.i686/extra/rt2860/rt2860sta.ko
-rwxr--r--. 1 root root   6204 Jul 23 10:48 /lib/modules/2.6.33.6-147.2.4.fc13.i686/kernel/drivers/edac/i82860_edac.ko
drwxr-xr-x. 2 root root   4096 Aug 22 09:23 /lib/modules/2.6.33.6-147.2.4.fc13.i686.PAE/extra/rt2860
-rw-r--r--. 1 root root 750740 Jul 27 04:19 /lib/modules/2.6.33.6-147.2.4.fc13.i686.PAE/extra/rt2860/rt2860sta.ko
-rwxr--r--. 1 root root   6208 Jul 23 10:44 /lib/modules/2.6.33.6-147.2.4.fc13.i686.PAE/kernel/drivers/edac/i82860_edac.ko
drwxr-xr-x. 2 root root   4096 Nov 11 07:32 /lib/modules/2.6.34.7-56.fc13.i686/extra/rt2860
-rw-r--r--. 1 root root 794948 Sep 21 22:16 /lib/modules/2.6.34.7-56.fc13.i686/extra/rt2860/rt2860sta.ko
-rwxr--r--. 1 root root   6440 Sep 14 20:51 /lib/modules/2.6.34.7-56.fc13.i686/kernel/drivers/edac/i82860_edac.ko
drwxr-xr-x. 2 root root   4096 Nov 11 07:32 /lib/modules/2.6.34.7-56.fc13.i686.PAE/extra/rt2860
-rw-r--r--. 1 root root 795396 Sep 21 22:16 /lib/modules/2.6.34.7-56.fc13.i686.PAE/extra/rt2860/rt2860sta.ko
-rwxr--r--. 1 root root   6444 Sep 14 20:44 /lib/modules/2.6.34.7-56.fc13.i686.PAE/kernel/drivers/edac/i82860_edac.ko
drwxr-xr-x. 2 root root   4096 Nov 11 07:32 /lib/modules/2.6.34.7-61.fc13.i686/extra/rt2860
-rw-r--r--. 1 root root 794948 Oct 21 14:55 /lib/modules/2.6.34.7-61.fc13.i686/extra/rt2860/rt2860sta.ko
-rwxr--r--. 1 root root   6440 Oct 18 22:01 /lib/modules/2.6.34.7-61.fc13.i686/kernel/drivers/edac/i82860_edac.ko
drwxr-xr-x. 2 root root   4096 Nov 11 07:32 /lib/modules/2.6.34.7-61.fc13.i686.PAE/extra/rt2860
-rw-r--r--. 1 root root 795396 Oct 21 14:55 /lib/modules/2.6.34.7-61.fc13.i686.PAE/extra/rt2860/rt2860sta.ko
-rwxr--r--. 1 root root   6444 Oct 18 22:13 /lib/modules/2.6.34.7-61.fc13.i686.PAE/kernel/drivers/edac/i82860_edac.k

$ find /etc/modprobe.d/
/etc/modprobe.d/
/etc/modprobe.d/dist.conf
/etc/modprobe.d/blacklist.conf
/etc/modprobe.d/openfwwf.conf
/etc/modprobe.d/blacklist-rt2800pci.conf
/etc/modprobe.d/dist-alsa.conf
/etc/modprobe.d/blacklist-visor.conf
/etc/modprobe.d/anaconda.conf
/etc/modprobe.d/dist-oss.conf
/etc/modprobe.d/libmlx4.conf

What module configurations?

(nothing interesting or mentioning "2860")

$ grep -e 2860  -rI /etc/modprobe.d/.
/etc/modprobe.d/./blacklist-rt2800pci.conf:# This file comes with RPMFusion's rt2860 package.




Scanning is spotty on the interface but does work...

$ sudo /sbin/iwlist ra0 scanning
[sudo] password for wbaker: 
ra0       Failed to read scan data : Resource temporarily unavailable

$ sudo /sbin/iwlist ra0 scanning
ra0       No scan results

$ sudo /sbin/iwlist ra0 scanning
ra0       Scan completed :
          Cell 01 - Address: 00:25:9C:63:75:8B
                    Protocol:802.11b/g
                    ESSID:"acedia"
                    Mode:Managed
                    Frequency:2.437 GHz (Channel 6)
                    Quality:86/100  Signal level:-56 dBm  Noise level:-92 dBm
                    Encryption key:off
                    Bit Rates:54 Mb/s



$ sudo /sbin/iwlist ra0 scanning
[sudo] password for wbaker: 
ra0       Scan completed :
          Cell 01 - Address: DE:DA:51:EE:12:25
                    Protocol:802.11b/g
                    ESSID:"compass"
                    Mode:Ad-Hoc
                    Frequency:2.412 GHz (Channel 1)
                    Quality:81/100  Signal level:-58 dBm  Noise level:-92 dBm
                    Encryption key:on
                    Bit Rates:54 Mb/s
          Cell 02 - Address: 00:04:5A:0E:F4:A9
                    Protocol:802.11b
                    ESSID:"insouciant"
                    Mode:Managed
                    Frequency:2.412 GHz (Channel 1)
                    Quality:81/100  Signal level:-58 dBm  Noise level:-92 dBm
                    Encryption key:off
                    Bit Rates:11 Mb/s
          Cell 03 - Address: 00:25:9C:63:75:8B
                    Protocol:802.11b/g
                    ESSID:"acedia"
                    Mode:Managed
                    Frequency:2.437 GHz (Channel 6)
                    Quality:65/100  Signal level:-64 dBm  Noise level:-92 dBm
                    Encryption key:off
                    Bit Rates:54 Mb/s

Comment 1 Wendell Baker 2010-12-31 02:30:06 UTC
Created attachment 471242 [details]
from /var/log/messages; see all the messages; see circa 17:37 when I logged in to GNOME; see the messages start when I log out

Comment 2 Wendell Baker 2010-12-31 02:30:38 UTC
Created attachment 471243 [details]
/etc/sysconfig/network-scripts/ifcfg-ra0

Comment 3 Wendell Baker 2010-12-31 02:31:56 UTC
Created attachment 471244 [details]
adding 'set -xv' to ifcfg-ra0 and running 'sudo /sbin/ifup ra0 >& o.nmcli.out'

Comment 4 Wendell Baker 2010-12-31 02:32:24 UTC
Created attachment 471245 [details]
lspci -vv

Comment 5 Wendell Baker 2010-12-31 02:32:49 UTC
Created attachment 471246 [details]
/sbin/ifconfig -a

Comment 6 Jirka Klimes 2011-01-07 11:34:25 UTC
Dec 30 17:27:07 host2 kernel: ===>rt_ioctl_giwscan. 2(2) BSS returned,
data->length = 225
is the driver debug message. But, no idea why it stops when you log in.

Nonetheless, be aware that the RPMFusion driver is not supported by Fedora. You probably use it because in-kernel driver didn't work.
You can see some discussion about Ralink wireless drivers in bug 570869.

Check http://www.mail-archive.com/devel@linuxdriverproject.org/msg01113.html for the "rt_ioctl_giwscan" message.

Reassigning to kernel, as the guys should know the current status of kernel Ralink driver.

Comment 7 Stanislaw Gruszka 2011-02-23 14:18:52 UTC
I'm sorry, we do not support ralink driver here. You need to ask vendor for help. You can also try to use community rt2x00 driver, it make quite good progress lastly regarding supporting rt28xx. You can use compat-wireless to run current upstream drivers with fedora kernel: http://people.redhat.com/sgruszka/compat_wireless.html


Note You need to log in before you can comment on or make changes to this bug.