From: Dan Williams <dcbw@redhat.com>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Dietmar Rudolph <dietmar@crlf.de>, linux-wireless@vger.kernel.org
Subject: Re: iwl3945 filling kern.log when HW switch is off
Date: Thu, 24 Oct 2013 09:48:01 -0500 [thread overview]
Message-ID: <1382626081.4328.3.camel@dcbw.foobar.com> (raw)
In-Reply-To: <20131024112750.GC1677@redhat.com>
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
next prev parent reply other threads:[~2013-10-24 14:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2013-10-25 10:04 ` Stanislaw Gruszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1382626081.4328.3.camel@dcbw.foobar.com \
--to=dcbw@redhat.com \
--cc=dietmar@crlf.de \
--cc=linux-wireless@vger.kernel.org \
--cc=sgruszka@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.