From: Coywolf Qi Hunt <coywolf@gmail.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Ruben Puettmann <ruben@puettmann.net>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.11.7 kernel panic on boot on AMD64
Date: Fri, 29 Apr 2005 00:38:24 +0800 [thread overview]
Message-ID: <2cd57c90050428093851785879@mail.gmail.com> (raw)
In-Reply-To: <20050428084313.1e69f59d.rddunlap@osdl.org>
On 4/28/05, Randy.Dunlap <rddunlap@osdl.org> wrote:
> On Thu, 28 Apr 2005 11:05:40 +0200
> Ruben Puettmann <ruben@puettmann.net> wrote:
>
> > On Wed, Apr 27, 2005 at 03:27:04PM -0700, Randy.Dunlap wrote:
> > Looks like this code in init/main.c:
> > >
> > > if (late_time_init)
> > > late_time_init();
> > >
> > > sees a garbage value in late_time_init (garbage being
> > > %eax == 0x00307974.743d656c, which is "le=tty0\n",
> > > as in "console=tty0").
> > >
> > > How long is your kernel boot/command line?
> > > Please post it.
> >
> > It was boot over pxe here is the append line from the
> > pxelinux.cfg/default
> >
> > APPEND vga=normal rw load_ramdisk=0 root=/dev/nfs nfsroot=192.168.112.1:/store/rescue/sarge-amd64,rsize=8192,wsize=8192,timo=12,retrans=3,mountvers=3,nfsvers=3
>
> Hm, no "console=tty...." at all. That didn't help (me) much.
Could that boot loader pxe append console=tty implicitly?
>From the vmlinux Ruben gave me,
ffffffff807980d8 A __bss_start
ffffffff807980d8 A _edata
ffffffff80798100 B boot_cpu_stack
ffffffff8079c100 B boot_exception_stacks
ffffffff807a1100 B system_state
ffffffff807a1120 B saved_command_line
ffffffff807a1220 B late_time_init
ffffffff807a1228 b execute_command
ffffffff807a1230 b panic_later
ffffffff807a1238 b panic_param
...
It seems possible to luckily skip the garbage. Comment out the two
lines and see if it works.
/* if (late_time_init)
late_time_init(); */
--
Coywolf Qi Hunt
http://sosdg.org/~coywolf/
next prev parent reply other threads:[~2005-04-28 16:38 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 [this message]
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
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=2cd57c90050428093851785879@mail.gmail.com \
--to=coywolf@gmail.com \
--cc=coywolf@lovecn.org \
--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