From: Andi Kleen <ak@suse.de>
To: Adrian Bunk <bunk@stusta.de>
Cc: Janos Farkas <jf-ml-k1-1087813225@lk8rp.mail.xeon.eu.org>,
linux-kernel@vger.kernel.org, Andi Kleen <ak@suse.de>,
Chris Bruner <cryst@golden.net>, Andrew Morton <akpm@osdl.org>,
Linus Torvalds <torvalds@osdl.org>,
Matt Domsch <Matt_Domsch@dell.com>
Subject: Re: COMMAND_LINE_SIZE increasing in 2.6.11-rc1-bk6
Date: Thu, 20 Jan 2005 17:48:29 +0100 [thread overview]
Message-ID: <20050120164829.GG450@wotan.suse.de> (raw)
In-Reply-To: <20050120162807.GA3174@stusta.de>
> AOL:
> - lilo 22.6.1
> - CONFIG_EDD=y
> - 2.6.10-mm1 and 2.6.11-rc1 did boot
> - 2.6.11-rc1-mm1 and 2.6.11-rc1-mm2 didn't boot
> - 2.6.11-rc1-mm2 with this ChangeSet reverted boots.
What I gather so far the problem seems to only happen with lilo
and EDID together. grub appears to work. Or did anyone
see problems with grub too?
I'll dig a bit, but reverting for now is probably best.
Thanks Linus.
-Andi
next prev parent reply other threads:[~2005-01-20 16:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 23:13 COMMAND_LINE_SIZE increasing in 2.6.11-rc1-bk6 Janos Farkas
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 [this message]
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=20050120164829.GG450@wotan.suse.de \
--to=ak@suse.de \
--cc=Matt_Domsch@dell.com \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=cryst@golden.net \
--cc=jf-ml-k1-1087813225@lk8rp.mail.xeon.eu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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