Skip to contentSkip to conversation

iwl3945 filling kern.log when HW switch is off

DISCUSSION Dietmar Rudolph 3 participants 4 messages Oct 23, 2013 – Oct 25, 2013

lore
Share & tools
lore
#0 lore raw

Hello, I hope this is the correct place to put a bug report in. I do not subscribe to this mailing list, but feel free to send PM in case you need additional info. You shoudn't :-)

After installing Ubuntu 13.10, I noticed kern.log growing faster than you could look at. Within a few working hours, kern.log was >6GB!

The reason is that I intentionally disabled WiFi on this laptop by turning the HW switch off. However, this makes iwl3945 write a log entry into kern.log every few microseconds!

The workaround is to turn the HW switch on. The bug fix would be to write just a single line to kern.log.

Regards
Dietmar

- - - from kern.log:

Oct 22 18:28:52 C50 kernel: [  141.144085] iwl3945 0000:02:00.0: Radio disabled by HW RF Kill switch
Oct 22 18:28:52 C50 kernel: [  141.144214] iwl3945 0000:02:00.0: Radio disabled by HW RF Kill switch
Oct 22 18:28:52 C50 kernel: [  141.145167] iwl3945 0000:02:00.0: Radio disabled by HW RF Kill switch
Oct 22 18:28:52 C50 kernel: [  141.145304] iwl3945 0000:02:00.0: Radio disabled by HW RF Kill switch
Oct 22 18:28:52 C50 kernel: [  141.146184] iwl3945 0000:02:00.0: Radio disabled by HW RF Kill switch
Oct 22 18:28:52 C50 kernel: [  141.146315] iwl3945 0000:02:00.0: Radio disabled by HW RF Kill switch
Oct 22 18:28:52 C50 kernel: [  141.147164] iwl3945 0000:02:00.0: Radio disabled by HW RF Kill switch
Oct 22 18:28:52 C50 kernel: [  141.147304] iwl3945 0000:02:00.0: Radio disabled by HW RF Kill switch
Oct 22 18:28:52 C50 kernel: [  141.148254] iwl3945 0000:02:00.0: Radio disabled by HW RF Kill switch
Oct 22 18:28:52 C50 kernel: [  141.148387] iwl3945 0000:02:00.0: Radio disabled by HW RF Kill switch
Oct 22 18:28:52 C50 kernel: [  141.149217] iwl3945 0000:02:00.0: Radio disabled by HW RF Kill switch
Oct 22 18:28:52 C50 kernel: [  141.149347] iwl3945 0000:02:00.0: Radio disabled by HW RF Kill switch
Oct 22 18:28:52 C50 kernel: [  141.150165] iwl3945 0000:02:00.0: Radio disabled by HW RF Kill switch
Oct 22 18:28:52 C50 kernel: [  141.150294] iwl3945 0000:02:00.0: Radio disabled by HW RF Kill switch
Oct 22 18:28:52 C50 kernel: [  141.151113] iwl3945 0000:02:00.0: Radio disabled by HW RF Kill switch
Oct 22 18:28:52 C50 kernel: [  141.151243] iwl3945 0000:02:00.0: Radio disabled by HW RF Kill switch
Oct 22 18:28:52 C50 kernel: [  141.152097] iwl3945 0000:02:00.0: Radio disabled by HW RF Kill switch
Oct 22 18:28:52 C50 kernel: [  141.152227] iwl3945 0000:02:00.0: Radio disabled by HW RF Kill switch
Signature · 10 lines
Dietmar Rudolph
Geschäftsführer/President

CR/LF GmbH
Obere Fuhr 27, 45136 Essen, Germany
phone: ++49 201 254566
mailto: [email protected], http://www.crlf.de

CR/LF Beratungsgesellschaft für EDV-Anwendungen mbH
Essen HRB 7016 - GF: Dipl.-Math. Dietmar Rudolph
#1 lore raw
Quoted 6 lines · Dietmar Rudolph

Hello, I hope this is the correct place to put a bug report in. I do not subscribe to this mailing list, but feel free to send PM in case you need additional info. You shoudn't :-)

After installing Ubuntu 13.10, I noticed kern.log growing faster than you could look at. Within a few working hours, kern.log was

Quoted 8 lines
Quoted 1 line

6GB!

The reason is that I intentionally disabled WiFi on this laptop by turning the HW switch off. However, this makes iwl3945 write a log entry into kern.log every few microseconds!

The workaround is to turn the HW switch on. The bug fix would be to write just a single line to kern.log.

This message is printed when someone try to UP device when RF kill switch is on. Either you did not compile kernel with CONFIG_RFKILL or your user space network management software does not handle rfkill .

Stanislaw

#2 lore raw
Quoted 13 lines · Stanislaw Gruszka
Quoted 12 lines · Dietmar Rudolph

Hello, I hope this is the correct place to put a bug report in. I do not subscribe to this mailing list, but feel free to send PM in case you need additional info. You shoudn't :-)

After installing Ubuntu 13.10, I noticed kern.log growing faster than you could look at. Within a few working hours, kern.log was

Quoted 1 line

6GB!

The reason is that I intentionally disabled WiFi on this laptop by turning the HW switch off. However, this makes iwl3945 write a log entry into kern.log every few microseconds!

Quoted 6 lines
Quoted 2 lines

The workaround is to turn the HW switch on. The bug fix would be to write just a single line to kern.log.

This message is printed when someone try to UP device when RF kill switch is on. Either you did not compile kernel with CONFIG_RFKILL or your user space network management software does not handle rfkill .

Though maybe it shouldn't actually print a dmesg error when that happens? Lots of software (scripts included) might try to open the device but not really know much about rfkill... Is there a way to print it once-per-rfkill instead maybe?

Dan

#3 lore raw
Quoted 17 lines · Dan Williams
Quoted 16 lines · Stanislaw Gruszka
Quoted 14 lines · Dietmar Rudolph

Hello, I hope this is the correct place to put a bug report in. I do not subscribe to this mailing list, but feel free to send PM in case you need additional info. You shoudn't :-)

After installing Ubuntu 13.10, I noticed kern.log growing faster than you could look at. Within a few working hours, kern.log was

Quoted 1 line

6GB!

The reason is that I intentionally disabled WiFi on this laptop by turning the HW switch off. However, this makes iwl3945 write a log entry into kern.log every few microseconds!

The workaround is to turn the HW switch on. The bug fix would be to write just a single line to kern.log.

Quoted 8 lines
Quoted 3 lines

This message is printed when someone try to UP device when RF kill switch is on. Either you did not compile kernel with CONFIG_RFKILL or your user space network management software does not handle rfkill .

Though maybe it shouldn't actually print a dmesg error when that happens? Lots of software (scripts included) might try to open the device but not really know much about rfkill... Is there a way to print it once-per-rfkill instead maybe?

I'll just remove this message. We can return ERFKILL error instead. That will allow user to identify problem without message.

Thanks
Stanislaw