public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Alexander Nyberg <alexn@telia.com>
Cc: Andi Kleen <ak@suse.de>, Ruben Puettmann <ruben@puettmann.net>,
	akpm@osdl.org, linux-kernel@vger.kernel.org, rddunlap@osdl.org
Subject: Re: 2.6.11.7 kernel panic on boot on AMD64
Date: Fri, 29 Apr 2005 16:46:32 +0200	[thread overview]
Message-ID: <20050429144632.GI21080@wotan.suse.de> (raw)
In-Reply-To: <1114785867.497.29.camel@localhost.localdomain>

On Fri, Apr 29, 2005 at 04:44:27PM +0200, Alexander Nyberg wrote:
> > Hmm? saved_command_Line should have enough space to add a simple string.
> > It is a 1024bytes. Unless you already have a 1k command line it should
> > be quite ok.
> 
> init/main.c:
> char saved_command_line[COMMAND_LINE_SIZE];
> 
> inclide/asm-x86-64/setup.h:
> #define COMMAND_LINE_SIZE	256
> 
> Rubens command line is a total of 251 chars, adding "console=tty0" will
> exceed it.

Ok that makes sense. I missed the fact that the original report
had such a overlong command line.

> 
> > Why do you think it is bogus?
> > 
> 
> I thought that saved_command_line on x64 was like the other archs, an
> untouched copy and it wouldn't have made sense to apply another string
> to it then, but I was wrong as it is the working line.
> 
> I still don't understand why console=tty0 is to be appended however.

It was needed in some 2.5 kernel when the console subsystem was 
very broken and I got tired of debugging it and just added this
easy workaround. Probably should have taken it out later, but
then these things tend to stick around.

-Andi

      reply	other threads:[~2005-04-29 14:49 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-27 14:03 2.6.11.7 kernel panic on boot on AMD64 Ruben Puettmann
2005-04-27 22:27 ` Randy.Dunlap
2005-04-28  9:05   ` Ruben Puettmann
2005-04-28 15:43     ` Randy.Dunlap
2005-04-28 15:53       ` Ruben Puettmann
2005-04-28 16:38       ` Coywolf Qi Hunt
2005-04-28 16:47         ` Randy.Dunlap
2005-04-29 14:29           ` Andi Kleen
2005-04-29 14:44             ` Ruben Puettmann
2005-04-29  8:25         ` Ruben Puettmann
2005-04-27 23:40 ` Randy.Dunlap
2005-04-29 10:06 ` Alexander Nyberg
2005-04-29 10:10   ` Andrew Morton
2005-04-29 11:10     ` Ruben Puettmann
2005-04-29 11:45     ` Alexander Nyberg
2005-04-29 14:34       ` Andi Kleen
2005-04-29 14:32   ` Andi Kleen
2005-04-29 14:41     ` Ruben Puettmann
2005-04-29 14:45       ` Andi Kleen
2005-04-29 20:11         ` Alexander Nyberg
2005-05-02 16:42           ` Andi Kleen
2005-04-29 14:44     ` Alexander Nyberg
2005-04-29 14:46       ` Andi Kleen [this message]

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=20050429144632.GI21080@wotan.suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=alexn@telia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.org \
    --cc=ruben@puettmann.net \
    /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