From: Sean Young <sean@mess.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>,
Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org, "H. Anvin" <hpa@zytor.com>
Subject: Re: Regression: boot failure on AMD Elan TS-5500
Date: Mon, 16 Jun 2008 16:19:44 +0000 [thread overview]
Message-ID: <20080616161944.GA53539@atlantis.8hz.com> (raw)
In-Reply-To: <48566C88.6000702@goop.org>
On Mon, Jun 16, 2008 at 06:37:12AM -0700, Jeremy Fitzhardinge wrote:
> Rusty Russell wrote:
> >On Monday 16 June 2008 22:11:39 Sean Young wrote:
> >
> >>The symptons are either a crash or reboot on booting the kernel. No
> >>printk's have occurred yet -- even with early printk on.
> >>
> >>2.6.15 worked on this board however current does not. I've bisected it to:
> >>
> >> commit a24e785111a32ccb7cebafd24b1b1cb474ea8e5d
> >> Author: Rusty Russell <rusty@rustcorp.com.au>
> >> Date: Sun Oct 21 16:41:35 2007 -0700
> >>
> >> i386: paravirt boot sequence
> >>
> >
> >Hi Sean,
> >
> > Thanks for tracking this down. Can we try reverting this in pieces to
> > see exactly what the cause was?
> >
> >1) Revert arch/x86/boot/compressed/head_32.S
> >2) If that doesn't fix it, Try removing the 8 lines which were added to
> >arch/x86/kernel/head_32.S
> >
> And the arch/x86/boot/compressed/misc_32.c change too, just in case...
Reverting only head_32.S makes the problem go away. I didn't try any other
changes.
> >I assume this is CONFIG_PARAVIRT=n?
Indeed.
> What bootloader does this platform use? I wonder if it's setting things
> up in an unexpected way?
It's syslinux. That must be the culprit, considering the change to head_32.S.
I'm digging in syslinux right now.
Thanks
Sean
next prev parent reply other threads:[~2008-06-16 16:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 12:11 Sean Young
2008-06-16 13:27 ` Rusty Russell
2008-06-16 13:37 ` Jeremy Fitzhardinge
2008-06-16 16:19 ` Sean Young [this message]
2008-06-16 17:06 ` H. Peter Anvin
2008-06-16 17:58 ` Sean Young
2008-06-16 18:16 ` H. Peter Anvin
2008-06-16 17:06 ` H. Peter Anvin
2008-06-16 17:07 ` Jeremy Fitzhardinge
2008-06-30 21:43 ` Sean Young
2008-06-30 21:52 ` Jeremy Fitzhardinge
2008-06-30 22:04 ` H. Peter Anvin
2008-06-30 22:14 ` H. Peter Anvin
2008-06-30 22:36 ` Jeremy Fitzhardinge
2008-06-30 22:45 ` H. Peter Anvin
2008-06-30 22:31 ` Sean Young
2008-06-30 22:34 ` Jeremy Fitzhardinge
2008-06-30 22:42 ` H. Peter Anvin
2008-07-01 19:59 ` Sean Young
2008-07-01 20:20 ` Sean Young
2008-07-01 20:24 ` Jeremy Fitzhardinge
2008-07-01 20:25 ` H. Peter Anvin
2008-07-15 22:23 ` Sean Young
2008-07-15 22:30 ` H. Peter Anvin
2008-07-01 20:22 ` Jeremy Fitzhardinge
2008-07-01 20:23 ` H. Peter Anvin
2008-07-01 20:29 ` Jeremy Fitzhardinge
2008-07-01 20:39 ` H. Peter Anvin
2008-07-06 13:21 ` Pavel Machek
2008-06-30 22:09 ` Sean Young
2008-07-06 2:41 ` Eric W. Biederman
2008-07-06 3:07 ` H. Peter Anvin
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=20080616161944.GA53539@atlantis.8hz.com \
--to=sean@mess.org \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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®