public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "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 14:10:59 -0400	[thread overview]
Message-ID: <20070315181059.GA1644@redhat.com> (raw)
In-Reply-To: <m1d53apjvu.fsf@ebiederm.dsl.xmission.com>

On Thu, Mar 15, 2007 at 10:11:01AM -0600, Eric W. Biederman wrote:
 > Dave Jones <davej@redhat.com> writes:
 > 
 > > On Tue, Mar 13, 2007 at 10:22:53AM +0100, Rafael J. Wysocki wrote:
 > >  > On Tuesday, 13 March 2007 05:08, Dave Jones wrote:
 > >  > > I spent considerable time over the last day or so bisecting to
 > >  > > find out why an X60 stopped resuming somewhen between 2.6.20 and current
 > > -git.
 > >  > > (Total lockup, black screen of death).
 > >  > 
 > >  > Do you have CONFIG_TICK_ONESHOT or CONFIG_NO_HZ set?  If you do, could you
 > >  > please unset them and retest?
 > >
 > > I did try with NO_HZ unset, made no difference, I don't recall TICK_ONESHOT.
 > > I'm in meetings all day, but I'll check when I get home.
 > 
 > I haven't heard anything more on this thread.
 > 
 > I just wanted to double check.  The tree that failed did it include
 > commits: 
 > 392ee1e6dd901db6c4504617476f6442ed91f72d and
 > 9f35575dfc172f0a93fb464761883c8f49599b7a
 > 
 > Mostly I was wondering if any of my later work to sort out msi 
 > suspend/resume actually solved anything.

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).

.. or it could be something else introduced between rc3 (which is
what my bisect was based on) and todays tree.

sigh. I'll do more bisecting after lunch.

	Dave

-- 
http://www.codemonkey.org.uk

  parent reply	other threads:[~2007-03-15 18:11 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 [this message]
2007-03-15 18:24         ` Eric W. Biederman
2007-03-15 19:45         ` Jeremy Fitzhardinge
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=20070315181059.GA1644@redhat.com \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox