Messages in this thread | | | Date | Thu, 20 Jan 2005 00:13:22 +0100 | From | Janos Farkas <> | Subject | COMMAND_LINE_SIZE increasing in 2.6.11-rc1-bk6 |
| |
Hi Andi!
I had difficulties booting recent rc1-bkN kernels on at least two Athlon machines (but somehow, on an *old* Pentium laptop booted with the a very similar system just fine).
The kernel just hung very early, just after displaying "BIOS data check successful" by lilo (22.6.1). Ctrl-Alt-Del worked to reboot, but nothing else was shown.
It is a similar experience to Chris Bruner's post here: > http://article.gmane.org/gmane.linux.kernel/271352
I also recall someone having similar problem with Opterons too, but can't find just now..
rc1-bk6 didn't boot, and thus I started checking revisions: rc1-bk3 did boot (as well as plain rc1) rc1-bk4 didn't boot rc1-bk7 booted *after* reverting the patch below:
> 4 days ak 1.2329.1.38 [PATCH] x86_64/i386: increase command line size > Enlarge i386/x86-64 kernel command line to 2k > This is useful when the kernel command line is used to pass other > information to initrds or installers. > On i386 it was duplicated for unknown reasons. > Signed-off-by: Andi Kleen > Signed-off-by: Andrew Morton > Signed-off-by: Linus Torvalds
While arguably it's not a completely scientific approach (no plain bk7, and no bk6 reverted was tested), I'm inclined to say this was my problem...
Isn't this define a lilo dependence?
-- Janos | romfs is at http://romfs.sourceforge.net/ | Don't talk about silence. - 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/
| |