* iwl3945 filling kern.log when HW switch is off
@ 2013-10-23 9:24 Dietmar Rudolph
2013-10-24 11:27 ` Stanislaw Gruszka
0 siblings, 1 reply; 4+ messages in thread
From: Dietmar Rudolph @ 2013-10-23 9:24 UTC (permalink / raw)
To: linux-wireless
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
--
Dietmar Rudolph
Geschäftsführer/President
CR/LF GmbH
Obere Fuhr 27, 45136 Essen, Germany
phone: ++49 201 254566
mailto: dietmar@crlf.de, http://www.crlf.de
CR/LF Beratungsgesellschaft für EDV-Anwendungen mbH
Essen HRB 7016 - GF: Dipl.-Math. Dietmar Rudolph
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: iwl3945 filling kern.log when HW switch is off
2013-10-23 9:24 iwl3945 filling kern.log when HW switch is off Dietmar Rudolph
@ 2013-10-24 11:27 ` Stanislaw Gruszka
2013-10-24 14:48 ` Dan Williams
0 siblings, 1 reply; 4+ messages in thread
From: Stanislaw Gruszka @ 2013-10-24 11:27 UTC (permalink / raw)
To: Dietmar Rudolph; +Cc: linux-wireless
On Wed, Oct 23, 2013 at 11:24:49AM +0200, Dietmar Rudolph wrote:
> 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.
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: iwl3945 filling kern.log when HW switch is off
2013-10-24 11:27 ` Stanislaw Gruszka
@ 2013-10-24 14:48 ` Dan Williams
2013-10-25 10:04 ` Stanislaw Gruszka
0 siblings, 1 reply; 4+ messages in thread
From: Dan Williams @ 2013-10-24 14:48 UTC (permalink / raw)
To: Stanislaw Gruszka; +Cc: Dietmar Rudolph, linux-wireless
On Thu, 2013-10-24 at 13:27 +0200, Stanislaw Gruszka wrote:
> On Wed, Oct 23, 2013 at 11:24:49AM +0200, Dietmar Rudolph wrote:
> > 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.
>
> 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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: iwl3945 filling kern.log when HW switch is off
2013-10-24 14:48 ` Dan Williams
@ 2013-10-25 10:04 ` Stanislaw Gruszka
0 siblings, 0 replies; 4+ messages in thread
From: Stanislaw Gruszka @ 2013-10-25 10:04 UTC (permalink / raw)
To: Dan Williams; +Cc: Dietmar Rudolph, linux-wireless
On Thu, Oct 24, 2013 at 09:48:01AM -0500, Dan Williams wrote:
> On Thu, 2013-10-24 at 13:27 +0200, Stanislaw Gruszka wrote:
> > On Wed, Oct 23, 2013 at 11:24:49AM +0200, Dietmar Rudolph wrote:
> > > 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.
> >
> > 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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2013-10-25 10:08 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-10-23 9:24 iwl3945 filling kern.log when HW switch is off Dietmar Rudolph
2013-10-24 11:27 ` Stanislaw Gruszka
2013-10-24 14:48 ` Dan Williams
2013-10-25 10:04 ` Stanislaw Gruszka
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.