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: Andrew Morton <akpm@osdl.org>,
	ruben@puettmann.net, linux-kernel@vger.kernel.org,
	rddunlap@osdl.org, ak@suse.de
Subject: Re: 2.6.11.7 kernel panic on boot on AMD64
Date: Fri, 29 Apr 2005 16:34:50 +0200	[thread overview]
Message-ID: <20050429143450.GF21080@wotan.suse.de> (raw)
In-Reply-To: <1114775159.497.6.camel@localhost.localdomain>

On Fri, Apr 29, 2005 at 01:45:59PM +0200, Alexander Nyberg wrote:
> fre 2005-04-29 klockan 03:10 -0700 skrev Andrew Morton:
> > Alexander Nyberg <alexn@telia.com> wrote:
> > >
> > > >                                                                                                            
> > > > I'm trying to install linux on an HP DL385 but directly on boot I got                                           
> > > > this kernel panic:
> > > > 
> > > >         http://www.puettmann.net/temp/panic.jpg
> > > 
> > > 
> > > This is bogus appending stuff to the saved_command_line and at the same
> > > time in Rubens case it touches the late_time_init() which breakes havoc.
> > 
> > -ETOOTERSE.  Do you meen that the user's command line was so long that this
> > strcat wandered off the end of the buffer and corrupted late_time_init?
> 
> Yes indeed, 256 chars has now really been proven to not be long enough.

So the user had really 256 characters command line? That is hard to 
believe because afaik most boot loaders cannot even pass that much.

> 
> > 
> > > Signed-off-by: Alexander Nyberg <alexn@telia.com>
> > > 
> > > Index: linux-2.6/arch/x86_64/kernel/head64.c
> > > ===================================================================
> > > --- linux-2.6.orig/arch/x86_64/kernel/head64.c	2005-04-26 11:41:43.000000000 +0200
> > > +++ linux-2.6/arch/x86_64/kernel/head64.c	2005-04-29 11:57:46.000000000 +0200
> > > @@ -93,9 +93,6 @@
> > >  #ifdef CONFIG_SMP
> > >  	cpu_set(0, cpu_online_map);
> > >  #endif
> > > -	/* default console: */
> > > -	if (!strstr(saved_command_line, "console="))
> > > -		strcat(saved_command_line, " console=tty0"); 
> > 
> > Wasn't that code there for a reason?
> 
> Appending console=tty0 is from what I can see redundant. And if it
> really has a reason it needs a comment and a check to see if there
> really is room in saved_command_line for it. We'll see what Andi has to
> say...

It was needed long ago (in 2.5) to work around bugs in the console subsystem.
It is probably not needed anymore. It can be dropped.

> 
> btw x64 is seemingly the only architecture that actually uses
> saved_command_line as the real working command line and not
> command_line, this is a bit confusing.

I have no problem with changing it if someone sends a patch.

-Andi

  reply	other threads:[~2005-04-29 14:36 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 [this message]
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

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=20050429143450.GF21080@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