Re: 2.6.33 dies on modprobe
From: M G Berberich
Date: Thu Mar 04 2010 - 15:38:16 EST
Am Donnerstag, den 04. MÃrz schrieb AmÃrico Wang:
> On Thu, Mar 04, 2010 at 12:04:38AM +0100, M G Berberich wrote:
> >Am Mittwoch, den 03. MÃrz schrieb AmÃrico Wang:
> >> On Wed, Mar 3, 2010 at 5:08 PM, AmÃrico Wang <xiyou.wangcong@xxxxxxxxx> wrote:
> >> > On Wed, Mar 3, 2010 at 4:58 PM, AmÃrico Wang <xiyou.wangcong@xxxxxxxxx> wrote:
> >> >> Ok, below is my patch, I am not sure it could fix the BUG for you,
> >> >> but it could fix the WARNING. But perhaps they are related.
> >> >>
> >> >> Please give it a try.
> >> >>
> >> >
> >> > Oops! Ignore the patch, it should not be correct, I will send a
> >> > correct version soon.
> >> > Sorry.
> >> >
> >> Here we go:
> >Seems to fix the warning, but not the modprobe-Oops.
> Thanks much for your testing!
> Could you please try to turn on DEBUG_KOBJECT and boot your kernel
> with "initcall_debug"? And then show us your dmesg.
If I'm doing this (enabled CONFIG_DEBUG_KERNEL and
CONFIG_DEBUG_KOBJECT), the kernel dies immediately - no output.
âDes is vÃllig wurscht, was heut beschlos- | M G Berberich
sen wird: I bin sowieso dagegn!â | berberic@xxxxxxxxxxxxxxxxx
(SPD-Stadtrat Kurt Schindler; Regensburg) | www.fmi.uni-passau.de/~berberic
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/