2.5.45: initrd broken?

Gerd Knorr (kraxel@bytesex.org)
Thu, 31 Oct 2002 18:03:40 +0100


Hi,

2.5.45 doesn't boot for me. I'm using a initrd to load some modules.
The last lines I see are:

(1) RAMDISK telling me it has found a image.
(2) initrd is freed
(3) Oops.

2.5.44 used to print it has mounted the root fs (i.e. the initrd)
instead of oopsing.

I can hook up a serial console to grab the exact messages if needed.

Gerd

-- 
You can't please everybody.  And usually if you _try_ to please
everybody, the end result is one big mess.
				-- Linus Torvalds, 2002-04-20
-
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/