From: Dieter Ries <clip2@gmx.de>
To: linux-kernel@vger.kernel.org
Cc: jbarnes@virtuousgeek.org, willy@linux.intel.com, pavel@suse.cz,
len.brown@intel.com, linux-pm@lists.linux-foundation.org,
rjw@sisk.pl
Subject: suspend to ram regression in current GIT, bisected
Date: Thu, 31 Jul 2008 21:05:27 +0200 [thread overview]
Message-ID: <48920CF7.4060907@gmx.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1358 bytes --]
Hi,
starting from 2.6.27-rc1, my Laptop (Thinkpad T60) did not return from
suspend to ram anymore.
When it should resume, the sleep LED went off, power went on, HD LED
flashed once, but the display stayed black.
It worked perfectly in 2.6.26, so I bisected it:
ce6fce4295ba727b36fdc73040e444bd1aae64cd is first bad commit
commit ce6fce4295ba727b36fdc73040e444bd1aae64cd
Author: Matthew Wilcox <matthew@wil.cx>
Date: Fri Jul 25 15:42:58 2008 -0600
PCI MSI: Don't disable MSIs if the mask bit isn't supported
David Vrabel has a device which generates an interrupt storm on the INTx
pin if we disable MSI interrupts altogether. Masking interrupts is only
a performance optimisation, so we can ignore the request to mask the
interrupt.
Signed-off-by: Matthew Wilcox <willy@linux.intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
:040000 040000 391a397ab982b7b80c0cb369d8a4999d8f7319fb
9a318bf27bf9c1bdd371e25754746397426a79ba M drivers
Reverting it was not a problem and fixed the issue.
As the screen stays black, I have no idea how to get further details on
that problem. Which additional information should I provide? Netconsole
didn't show anything.
cu
Dieter
--
3rd Law of Computing:
Anything that can go wr
fortune: Segmentation violation -- Core dumped
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next reply other threads:[~2008-07-31 19:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 19:05 Dieter Ries [this message]
2008-07-31 19:07 ` suspend to ram regression in current GIT, bisected Jesse Barnes
2008-07-31 19:25 ` Dieter Ries
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=48920CF7.4060907@gmx.de \
--to=clip2@gmx.de \
--cc=jbarnes@virtuousgeek.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pavel@suse.cz \
--cc=rjw@sisk.pl \
--cc=willy@linux.intel.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