Bug 251845 - kernel-2.6.22.1-41.fc7 spams dmesg with wireless debug messages
kernel-2.6.22.1-41.fc7 spams dmesg with wireless debug messages
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
7
All Linux
low Severity low
: ---
: ---
Assigned To: John W. Linville
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-08-12 07:14 EDT by Osma Ahvenlampi
Modified: 2007-11-30 17:12 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-08-13 13:11:48 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Osma Ahvenlampi 2007-08-12 07:14:26 EDT
Between kernel-2.6.22.1-33.fc7 and kernel-2.6.22.1-41.fc7 the wireless patches
have become really verbose. I'm using the iwl4965 driver with firmware 4.44.17
installed from intellinuxwireless.org.

[oa@libretto ~]$ dmesg | tail -5
wlan0: RX WEP frame with unknown keyidx 2 (A1=ff:ff:ff:ff:ff:ff
A2=00:11:95:4c:4a:25 A3=00:11:95:4c:4a:25)
wlan0: RX WEP frame with unknown keyidx 2 (A1=ff:ff:ff:ff:ff:ff
A2=00:11:95:4c:4a:25 A3=00:11:95:4c:4a:25)
wlan0: RX WEP frame with unknown keyidx 2 (A1=ff:ff:ff:ff:ff:ff
A2=00:11:95:4c:4a:25 A3=00:11:95:4c:4a:25)
wlan0: RX WEP frame with unknown keyidx 2 (A1=ff:ff:ff:ff:ff:ff
A2=00:11:95:4c:4a:25 A3=00:11:95:4c:4a:25)
wlan0: RX WEP frame with unknown keyidx 2 (A1=ff:ff:ff:ff:ff:ff
A2=00:11:95:4c:4a:25 A3=00:11:95:4c:4a:25)
[oa@libretto ~]$ dmesg | grep "RX WEP frame with unknown keyidx" | wc -l
688
[oa@libretto ~]$ dmesg | wc -l
1395
Comment 1 John W. Linville 2007-08-13 10:36:08 EDT
I don't really see any recent changes that would account for this -- the 
message itself has been around for quite a while.

Are you sure there hasn't been some configuration change in your network?
Comment 2 Osma Ahvenlampi 2007-08-13 13:11:48 EDT
You're correct - it's not new to -41. I just booted again with -33 and see the
same messages, so it must be a new device in the network or something.
Accordingly, I'll close this ticket, sorry about the false alert.

Still, the message is quite chatty, and is caused by events outside of the scope
of the local machine and the user's sphere of influence, so perhaps that should
be looked at upstream.

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