From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: pm list <linux-pm@lists.linux-foundation.org>,
Greg KH <gregkh@suse.de>, LKML <linux-kernel@vger.kernel.org>,
Alan Cox <alan@linux.intel.com>
Subject: Re: [Regression] 2.6.31-git: tty change broke resume from hibernation on MSI Wind U100
Date: Sun, 27 Sep 2009 17:00:38 +0200 [thread overview]
Message-ID: <200909271700.38541.rjw@sisk.pl> (raw)
In-Reply-To: <20090927124716.2fd8a1de@lxorguk.ukuu.org.uk>
On Sunday 27 September 2009, Alan Cox wrote:
> On Sat, 26 Sep 2009 00:38:21 +0200
> "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
>
> > Hi Alan,
> >
> > As stated at http://bugzilla.kernel.org/show_bug.cgi?id=14229, your commit
> > b50989dc444599c8b21edc23536fc305f4e9b7d5
> > (tty: make the kref destructor occur asynchronously) appears to have broken
> > resume from hibernation on MSI Wind U100.
> >
> > I verified that hibernation works correctly with this commit reverted.
> >
> > I'm still not sure what the root cause of the problem is, though.
>
> The root cause is that the patch to fix the console async/sync behaviour
> went into Andrews tree, back out of it and vanished.
>
> It's a known bug, with a known confirmed fix. You may want to pick it up
> and submit it as there is no tty maintainer currently.
Thanks, I guess it's this one:
tty-fix-regression-caused-by-tty-make-the-kref-destructor-occur-asynchronously.patch ?
next prev parent reply other threads:[~2009-09-27 15:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200909260038.22079.rjw@sisk.pl>
2009-09-27 11:47 ` [Regression] 2.6.31-git: tty change broke resume from hibernation on MSI Wind U100 Alan Cox
[not found] ` <20090927124716.2fd8a1de@lxorguk.ukuu.org.uk>
2009-09-27 15:00 ` Rafael J. Wysocki [this message]
2009-09-27 16:00 ` [PATCH, fix] " Rafael J. Wysocki
2009-09-25 22:38 Rafael J. Wysocki
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=200909271700.38541.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=alan@linux.intel.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.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