public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chuck Ebbert <cebbert@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: bbpetkov@yahoo.de, 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 11:51:48 -0400	[thread overview]
Message-ID: <46AA1494.5020709@redhat.com> (raw)
In-Reply-To: <46A9753A.1010206@zytor.com>

On 07/27/2007 12:31 AM, H. Peter Anvin wrote:
> Borislav Petkov wrote:
>>> 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 ?
> 
> If we can't reproduce the problem in simulation, that itself will tell
> us something very important.  If we *can* reproduce it in simulation, it
> will be vastly easier to debug.

We're seeing boot failure when using isolinux with the latest kernels,
but so far only on Dell machines. It loads the kernel and initrd, types
"Ready." and then just reboots. Adding "vga=ask" gives the mode prompt
and allows selecting a video mode, but it just reboots after that too.


  reply	other threads:[~2007-07-27 15:51 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
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 [this message]
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=46AA1494.5020709@redhat.com \
    --to=cebbert@redhat.com \
    --cc=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