All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Dave Jones <davej@redhat.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: 2.6.21rc suspend to ram regression on Lenovo X60
Date: Thu, 15 Mar 2007 12:45:20 -0700	[thread overview]
Message-ID: <45F9A250.7040409@goop.org> (raw)
In-Reply-To: <20070315181059.GA1644@redhat.com>

Dave Jones wrote:
> I just did a build of top of tree, including those commits, and
> it's still broken.  Booting with pci=nomsi no longer 'fixes' it
> though, which may indicate that the MSI changes were a red herring.
> (Or that the subsequent changes have regressed it even more,
>  which seems unlikely looking at the changes).
>   

I just found the same thing on my X60.  Current top-of-tree with
pci=nomsi does not improve things.  When it resumes, the CPU is working
(capslock toggles, sysreq-b reboots), but the screen is blank.

I was about to try 2.6.21-rc3-mm2; I'll see if that's any different.

    J

  parent reply	other threads:[~2007-03-15 19:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-13  4:08 2.6.21rc suspend to ram regression on Lenovo X60 Dave Jones
2007-03-13  8:11 ` Eric W. Biederman
2007-03-16 16:21   ` Pavel Machek
2007-03-16 18:37     ` Kok, Auke
2007-03-13  9:22 ` Rafael J. Wysocki
2007-03-13 13:22   ` Dave Jones
2007-03-15 16:11     ` Eric W. Biederman
2007-03-15 17:00       ` Dave Jones
2007-03-15 18:10       ` Dave Jones
2007-03-15 18:24         ` Eric W. Biederman
2007-03-15 19:45         ` Jeremy Fitzhardinge [this message]
2007-03-15 20:00           ` Dave Jones
2007-03-13 14:41 ` Matt Mackall

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=45F9A250.7040409@goop.org \
    --to=jeremy@goop.org \
    --cc=davej@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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.