From: Johannes Berg <johannes@sipsolutions.net>
To: Alan Jenkins <sourcejedi.lkml@googlemail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
"Luis R. Rodriguez" <mcgrof@gmail.com>
Subject: Re: [RFT v9] rfkill: rewrite
Date: Wed, 13 May 2009 16:38:27 +0200 [thread overview]
Message-ID: <1242225507.9913.0.camel@johannes.local> (raw)
In-Reply-To: <9b2b86520905130736j6cde99cak6fad414531b0168c@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 943 bytes --]
On Wed, 2009-05-13 at 15:36 +0100, Alan Jenkins wrote:
> >> <http://picasaweb.google.com/sourcejedi.lkml/Screenshots#5334936857267342674>
> >>
> >> The kernel then hangs later on in the boot process. It responds to
> >> SysRq, but does not echo normal keypresses. SysRq+P shows that the
> >> kernel is in the idle task. I left it for three minutes, but I didn't
> >> get any trace from the hung task detector or soft lockup detector.
> >>
> >> At first I thought it must be a problem with wireless-testing.
> >> However, it went away when I eventually tried un-applying the rfkill
> >> rewrite patch.
> >
> > Confusing, but I think the stacktrace is just bogus. Can you recompile
> > your kernel with CONFIG_FRAME_POINTER please?
>
> Nope, cos it's already enabled :-).
Damn, I had hoped to get relevant information. I really don't see how
rfkill could cause a problem in regulatory code, let's ask Luis.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-05-13 14:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 8:31 [RFT v9] rfkill: rewrite Johannes Berg
2009-05-12 14:09 ` Alan Jenkins
2009-05-13 10:49 ` Johannes Berg
2009-05-13 14:36 ` Alan Jenkins
2009-05-13 14:38 ` Johannes Berg [this message]
2009-05-13 21:48 ` Luis R. Rodriguez
2009-05-13 21:45 ` Luis R. Rodriguez
2009-05-14 9:02 ` Alan Jenkins
2009-05-14 9:08 ` Johannes Berg
2009-05-14 9:58 ` Alan Jenkins
2009-05-14 10:00 ` Johannes Berg
2009-05-14 4:34 ` Luis R. Rodriguez
2009-05-14 8:24 ` Alan Jenkins
2009-05-12 17:26 ` Will Keaney
2009-05-12 17:52 ` Johannes Berg
2009-05-12 17:59 ` Dan Williams
2009-05-12 18:04 ` Johannes Berg
2009-05-12 18:09 ` Will Keaney
2009-05-12 18:13 ` Johannes Berg
2009-05-13 21:40 ` Henrique de Moraes Holschuh
2009-05-13 22:19 ` Johannes Berg
2009-05-15 1:27 ` Henrique de Moraes Holschuh
2009-05-15 8:23 ` Johannes Berg
2009-05-18 11:00 ` Henrique de Moraes Holschuh
2009-05-19 12:12 ` Johannes Berg
2009-05-19 18:24 ` Henrique de Moraes Holschuh
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=1242225507.9913.0.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=sourcejedi.lkml@googlemail.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.