From: Borislav Petkov <bbpetkov@yahoo.de>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Xudong Guan <xudong.guan@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.23-rc1: no setup signature found...
Date: Fri, 27 Jul 2007 03:36:16 +0200 [thread overview]
Message-ID: <20070727013615.GC4570@gollum.tnic> (raw)
In-Reply-To: <46A8E3F9.5070809@zytor.com>
On Thu, Jul 26, 2007 at 11:12:09AM -0700, H. Peter Anvin wrote:
> Borislav Petkov wrote:
> >
> >> What distro/version of grub are you running?
> > Debian unstable
> >> 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.
> > grub version:
> >
> > [boris@gollum:18:17:27:-> apt-cache show grub
> > Package: grub
> > Priority: optional
> > Section: admin
> > Installed-Size: 708
> > Maintainer: Grub Maintainers <pkg-grub-devel@lists.alioth.debian.org>
> > Architecture: i386
> > Version: 0.97-29
> > Depends: libc6 (>= 2.5-5), libncurses5 (>= 5.4-5)
> > Suggests: grub-doc, mdadm
> > Filename: pool/main/g/grub/grub_0.97-29_i386.deb
> > Size: 366884
> > MD5sum: 2da7a5942db06eaba046dff4615bcce9
> > SHA1: 7f4da793da209d011ce94fceebaebe0e5f08790f
> > SHA256: 2596782c08f1f7365e9935f687fef74c67d8702503188f22448db9f0ac98e18e
> > Description: GRand Unified Bootloader
> > ...
>
> This concerns me deeply. This is a current version of Grub which
> shouldn't have any silly 8K limitations. Yet it appears to have a
> similar pathology over the ancient version Xudong just described.
>
> The absolute best would be if we could replicate this in simulation
> (Bochs or Qemu); this would make it very simple to debug. Would you be
> willing to try to do that?
sure, will do, however i'll be busy at work/travelling tomorrow but as soon as i
get home i'll whip up my qemu and run the kernel in question in it. However,
Xudong said that grub 0.97 boots just fine on his machine and i think it'll be
better to debug this right on the bare hardware (i.e. my laptop) ...?
Suggestions ?
--
Regards/Gruß,
Boris.
next prev parent reply other threads:[~2007-07-27 1:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 11:26 Borislav Petkov
2007-07-26 15:08 ` Xudong Guan
2007-07-26 15:19 ` H. Peter Anvin
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 [this message]
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=20070727013615.GC4570@gollum.tnic \
--to=bbpetkov@yahoo.de \
--cc=hpa@zytor.com \
--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 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®