From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Michal Jaegermann <michal@ellpspace.math.ualberta.ca>,
Steven Rostedt <rostedt@goodmis.org>,
"Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
Oliver Neukum <oneukum@suse.de>,
linux-pm@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
"Greg Kroah-Hartman" <gregkh@suse.de>
Subject: Re: Suspend and resume on ASUS Laptops
Date: Sun, 4 Dec 2011 20:57:10 +0100 [thread overview]
Message-ID: <201112042057.11175.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1112041128580.32730-100000@netrider.rowland.org>
On Sunday, December 04, 2011, Alan Stern wrote:
> On Sat, 3 Dec 2011, Michal Jaegermann wrote:
>
> > On Sat, Dec 03, 2011 at 10:19:27AM -0500, Alan Stern wrote:
> > > On Fri, 2 Dec 2011, Michal Jaegermann wrote:
> > > >
> > > > On my ASUS K52Jc these controllers are also reported "disabled". This
> > >
> > > What exactly do you mean by that?
> >
> > I mean that you asked Steven about a content of
> > /sys/bus/pci/devices/0000\:00\:1[ad].0/power/wakeup
> > On my ASUS K52Jc these ids also happen to belong to ehci_hcd devices
> > (both "Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host
> > Controller") and both 'wakeup' files show "disabled" too.
>
> Oh, sorry -- I didn't realize you meant the power/wakeup file contained
> "disabled". It sounded like you were saying that the controllers were
> somehow disabled.
>
> > With that above I have to do all these manipulations with unbinding
> > and binding drivers and removing inserting modules or a laptop will hang
> > after a suspend. Now with a recent kernel I need additionally put
> > wireless driver modules on a "special handling" list or I will loose
> > such connection (no hang here, just a dead driver).
> >
> > All of this looks like pretty consistent, from what one can find on the
> > net, across various models of ASUS laptops.
>
> Yes, apparently ASUS's recent chipsets or firmware has a problem with
> suspend and resume. On the other hand, I'm writing this on an ASUS
> UL20A laptop, which suspends and resumes with no difficulty.
I wonder, though, who figured out what quirk to use before suspend on those
particular machines and on what basis (some information from the vendor or
what?).
Thanks,
Rafael
next prev parent reply other threads:[~2011-12-04 19:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 4:11 Steven Rostedt
2011-12-01 9:35 ` Rafael J. Wysocki
2011-12-01 11:48 ` Oliver Neukum
2011-12-01 14:28 ` Steven Rostedt
2011-12-01 14:38 ` Oliver Neukum
2011-12-01 15:01 ` Srivatsa S. Bhat
2011-12-01 18:16 ` Steven Rostedt
2011-12-01 18:41 ` Steven Rostedt
2011-12-02 15:43 ` Alan Stern
2011-12-02 16:09 ` Steven Rostedt
2011-12-02 16:23 ` Alan Stern
2011-12-02 17:41 ` Steven Rostedt
2011-12-02 21:57 ` Alan Stern
2011-12-05 11:03 ` Pavel Machek
2011-12-05 13:37 ` Steven Rostedt
2011-12-03 2:43 ` Michal Jaegermann
2011-12-03 15:19 ` Alan Stern
2011-12-03 20:23 ` Michal Jaegermann
2011-12-04 16:54 ` Alan Stern
2011-12-04 19:57 ` Rafael J. Wysocki [this message]
2011-12-03 18:48 ` Mantas M.
2011-12-01 15:20 ` Steven Rostedt
2011-12-02 4:04 ` Michal Jaegermann
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=201112042057.11175.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=gregkh@suse.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=michal@ellpspace.math.ualberta.ca \
--cc=oneukum@suse.de \
--cc=pavel@ucw.cz \
--cc=rostedt@goodmis.org \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--cc=stern@rowland.harvard.edu \
/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
Powered by JetHome