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:
signature.asc
Description: This is a digitally signed message part
