From: Janos Farkas <jf-ml-k1-1087813225@lk8rp.mail.xeon.eu.org>
To: linux-kernel@vger.kernel.org
Cc: Andi Kleen <ak@suse.de>, Chris Bruner <cryst@golden.net>
Subject: COMMAND_LINE_SIZE increasing in 2.6.11-rc1-bk6
Date: Thu, 20 Jan 2005 00:13:22 +0100 [thread overview]
Message-ID: <20050119231322.GA2287@lk8rp.mail.xeon.eu.org> (raw)
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.
next reply other threads:[~2005-01-19 23:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 23:13 Janos Farkas [this message]
2005-01-20 4:21 ` Chris Bruner
2005-01-20 16:28 ` Adrian Bunk
2005-01-20 16:40 ` Linus Torvalds
2005-01-20 16:48 ` Andi Kleen
2005-01-20 20:53 ` Something very strange on x86_64 2.6.X kernels Eric Dumazet
2005-01-20 21:08 ` Andrew Morton
2005-01-20 21:19 ` Eric Dumazet
2005-01-21 16:26 ` Petr Vandrovec
2005-01-21 16:49 ` Eric Dumazet
2005-01-21 18:30 ` Petr Vandrovec
2005-01-22 1:54 ` Andi Kleen
2005-01-22 2:14 ` Linus Torvalds
2005-01-21 6:58 ` COMMAND_LINE_SIZE increasing in 2.6.11-rc1-bk6 Catalin(ux aka Dino) BOIE
2005-01-21 7:11 ` Andi Kleen
2005-01-21 17:46 ` Matt Domsch
2005-01-21 19:05 ` H. Peter Anvin
2005-02-07 6:57 ` Werner Almesberger
2005-02-12 13:54 ` Eric W. Biederman
2005-02-12 14:51 ` Werner Almesberger
2005-02-12 15:17 ` Eric W. Biederman
2005-02-14 5:49 ` Werner Almesberger
2005-02-14 7:36 ` Eric W. Biederman
2005-02-14 6:15 ` Adam Sulmicki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050119231322.GA2287@lk8rp.mail.xeon.eu.org \
--to=jf-ml-k1-1087813225@lk8rp.mail.xeon.eu.org \
--cc=ak@suse.de \
--cc=cryst@golden.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®