All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Xudong Guan <xudong.guan@gmail.com>
Cc: Borislav Petkov <bbpetkov@yahoo.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.23-rc1: no setup signature found...
Date: Thu, 26 Jul 2007 08:19:08 -0700	[thread overview]
Message-ID: <46A8BB6C.6050903@zytor.com> (raw)
In-Reply-To: <20070726150854.GA7034@xguan-laptop>

Xudong Guan wrote:
> On 13:26(+0200) Tue 24 Jul, Borislav Petkov wrote:
>>    2.6.23-rc1 won't boot on my Asus M6N laptop and the last thing it shows after loading
>> grub is "No setup signature found...," which, imho, comes from
>> arch/i386/boot/header.S. I tried printing out the value of setup_sig like so
> 
> I hitted the same error message with v2.6.23-rc1-171-ge4903fb.
> No problem with v2.6.21-3770-g01e73be.
> Seems there has been some cleanup of the i386/boot code.
> Anyone can give a quick clue, or should I do a bisect?

The bisect will almost guaranteed show a change at the change to the new
setup code.  The message means that the setup code wasn't loaded
correctly into memory; the big question is *why*.

What distro/version of grub are you running?  I'm wondering if there are
some old version of grub out there which did the "load four sectors"
way-anciently-obsolete crap; the other possibility that comes to mind is
setting up the stack in an invalid manner.

	-hpa

  reply	other threads:[~2007-07-26 15:19 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-24 11:26 2.6.23-rc1: no setup signature found Borislav Petkov
2007-07-26 15:08 ` Xudong Guan
2007-07-26 15:19   ` H. Peter Anvin [this message]
2007-07-26 15:26     ` Xudong Guan
2007-07-26 15:43       ` H. Peter Anvin
     [not found]       ` <46A8C7BA.3040008@zytor.com>
     [not found]         ` <20070726162439.GA13387@xguan-laptop>
     [not found]           ` <46A8CB3F.7040207@zytor.com>
     [not found]             ` <20070726171609.GA16236@xguan-laptop>
2007-07-26 17:55               ` H. Peter Anvin
2007-07-26 16:30     ` Borislav Petkov
2007-07-26 16:36       ` Xudong Guan
2007-07-26 16:59         ` Borislav Petkov
2007-07-26 17:09           ` Xudong Guan
2007-07-26 18:12       ` H. Peter Anvin
2007-07-27  1:36         ` Borislav Petkov
2007-07-27  4:31           ` H. Peter Anvin
2007-07-27 15:51             ` Chuck Ebbert
2007-07-29  8:51             ` Borislav Petkov
2007-07-29  9:24               ` Xudong Guan
2007-07-29 10:37                 ` Borislav Petkov
2007-07-29 13:50                   ` H. Peter Anvin
2007-07-29 19:15                     ` Borislav Petkov
2007-07-30 14:05                       ` H. Peter Anvin
2007-07-30 18:53                         ` Borislav Petkov
2007-07-30 20:46                           ` H. Peter Anvin
2007-08-01  4:38                             ` Borislav Petkov
2007-08-01 12:41                               ` H. Peter Anvin
2007-08-01 14:36                               ` H. Peter Anvin
2007-08-02  5:13                                 ` 2.6.23-rc1: no setup signature found... SOLVED! Borislav Petkov
2007-08-02 17:41                                   ` 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=46A8BB6C.6050903@zytor.com \
    --to=hpa@zytor.com \
    --cc=bbpetkov@yahoo.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xudong.guan@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.