linux-kernel - Re: 2.6.21rc suspend to ram regression on Lenovo X60

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070315181059.GA1644@redhat.com>
Date:	Thu, 15 Mar 2007 14:10:59 -0400
From:	Dave Jones <davej@...hat.com>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Greg Kroah-Hartman <gregkh@...e.de>
Subject: Re: 2.6.21rc suspend to ram regression on Lenovo X60

On Thu, Mar 15, 2007 at 10:11:01AM -0600, Eric W. Biederman wrote:
 > Dave Jones <davej@...hat.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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/