mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Beth Kon <eak@us.ibm.com>,
	rostedt@goodmis.org, avi@redhat.com,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Wierdness - linux-next KVM patch breaks Dell Latitude D820, KVM not in kernel
Date: Sun, 20 Sep 2009 11:50:09 -0400	[thread overview]
Message-ID: <77690.1253461809@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 07 Sep 2009 10:07:07 EDT." <3850.1252332427@turing-police.cc.vt.edu>

[-- Attachment #1: Type: text/plain, Size: 667 bytes --]

On Mon, 07 Sep 2009 10:07:07 EDT, Valdis.Kletnieks@vt.edu said:

> Symptoms: Dell Latitude D820 either hangs at very early boot (before
> any output, not even penguins), or (apparently) triple-faults into an
> immediate reboot.  linux-2.6.31-rc7-mmotm0827 works fine, so whatever the
> real issue is, it hit linux-next between then and when Andrew pulled for
> -0902.  Since I was feeling lazy, I told 'git bisect' that 2.6.31-rc7 was
> good and HEAD was bad.

Whatever it was, I can no longer replicate it with 2.6.31-mmotm0917, so it
looks like some maintainer merged the fix for whatever it was.  File
this one under "things that go bump in the night", I guess...

[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]

      parent reply	other threads:[~2009-09-20 20:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-07 14:07 Valdis.Kletnieks
2009-09-08 13:32 ` Beth Kon
2009-09-08 19:41   ` Valdis.Kletnieks
2009-09-09 14:25     ` Avi Kivity
2009-09-09 17:34     ` Valdis.Kletnieks
2009-09-09 17:38       ` Avi Kivity
2009-09-09 18:59         ` Valdis.Kletnieks
2009-09-12 20:55           ` Valdis.Kletnieks
2009-09-13 11:39             ` Avi Kivity
2009-09-20 15:50 ` Valdis.Kletnieks [this message]

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=77690.1253461809@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=akpm@linux-foundation.org \
    --cc=avi@redhat.com \
    --cc=eak@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    /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®