From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 13886] Suspend to disk no longer works in 2.6.30.2 with an EIDE drive
Date: Sat, 1 Aug 2009 19:12:55 GMT [thread overview]
Message-ID: <200908011912.n71JCtI8006087@demeter.kernel.org> (raw)
In-Reply-To: <bug-13886-11633@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=13886
--- Comment #5 from Rafael J. Wysocki <rjw@sisk.pl> 2009-08-01 19:12:54 ---
(In reply to comment #4)
> The fix mentioned above (commit 2ea5521022ac8f4f528dcbae02668e02a3501a5a) does
> not address the problem I am encountering (which is present in 2.6.30.2).
>
Bart's point is that the problem introduced by commit
295f00042aaf6b553b5f37348f89bab463d4a469 was fixed by commit
2ea5521022ac8f4f528dcbae02668e02a3501a5a, so if you have a bisection point
between the two commits, the bisection may lead to commit
295f00042aaf6b553b5f37348f89bab463d4a469 instead of the real culprit.
> There is no e100 hardware present here.
How is e100 relevant here?
> I am more than willing to help with the debugging process from this end.
>
> Might we test by reverting his commit on 2.6.30.2?
That might be difficult, because I guess commit
295f00042aaf6b553b5f37348f89bab463d4a469 doesn't revert cleanly.
Could you instead test the kernel where commit
2ea5521022ac8f4f528dcbae02668e02a3501a5a is the head and see if the problem is
present there?
[Bart, I know you're not maintaining IDE any more, but your commit was pointed
out by the bisection. Thanks for the information that it was a false
positive.]
First-Bad-Commit: unknown
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2009-08-01 19:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-01 10:12 [Bug 13886] New: Suspend to disk no longer works in 2.6.30.2 with an EIDE drive bugzilla-daemon
2009-08-01 10:22 ` [Bug 13886] " bugzilla-daemon
2009-08-01 10:50 ` bugzilla-daemon
2009-08-01 10:52 ` bugzilla-daemon
2009-08-01 12:50 ` bugzilla-daemon
2009-08-01 15:13 ` bugzilla-daemon
2009-08-01 19:12 ` bugzilla-daemon [this message]
2009-08-04 7:58 ` bugzilla-daemon
2009-08-04 15:12 ` bugzilla-daemon
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=200908011912.n71JCtI8006087@demeter.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ide@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).