Re: initrd breakage in 2.5.38-2.5.40

From: Mikael Pettersson (mikpe@csd.uu.se)
Date: Mon Oct 07 2002 - 07:52:00 EST


On Thu, 3 Oct 2002 13:00:05 +0200, Mikael Pettersson wrote:
>I've been experiencing initrd-related problems since 2.5.38.
>It worked like a charm up to 2.5.37.
>
>The initrd itself works (mine allows users to select root
>partition, no modules involved), but some time later, the
>kernel hangs hard. (No message, NMI watchdog and SysRQ don't
>work.) I can trigger the hangs easily by generating a lot of
>FS activity, e.g. by unpacking a kernel tarball just after boot.
>
>When booting without an initrd image the kernel is rock solid.

Additional information: the problems occurs on every machine
I've tested, and it occurs even if I use a trivial initrd whose
/linuxrc just is "int main(void){return 0;}", so it's not caused
by mounting/pivot_root:ing from the initrd.

/Mikael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Mon Oct 07 2002 - 22:00:58 EST