From: Daniel Qarras <dqarras@yahoo.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>,
Alan Stern <stern@rowland.harvard.edu>
Cc: Linux-pm mailing list <linux-pm@lists.linux-foundation.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Acer Aspire 1690 Suspend/Hibernate Report with 2.6.29-rc3
Date: Fri, 30 Jan 2009 06:33:30 -0800 (PST) [thread overview]
Message-ID: <333776.95358.qm@web36801.mail.mud.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0901291816130.6298-100000@iolanthe.rowland.org>
Hi!
> > (Of course for a layman like me it is a bit saddening
> > that this worked earlier but not anymore.)
>
> Perhaps Rafael has some idea on what has changed in the
> meantime to cause this problem. It could have something to do with the
> way ACPI is now integrated with the PCI drivers, for example.
Not sure if this is appropriate but I'll mention that I have dual-boot and with Windows XP SP 3 hibernation works all ok.
> > Please find such a dmesg attached.
>
> The log doesn't indicate a real cause. It does show
> that wakeup was disabled on the EHCI controller, but nevertheless that
> controller must have been responsible for waking up your system when the
> mouse was plugged back in. You can test this by unloading ehci-hcd
> before suspending.
Correct, I tested suspend after removing the offending module and plugging the mouse does not wake the machine anymore! One thing is still different when comparing to Win XP (if I may): hitting mouse buttons will activate the internal led while in suspend even after removing the module but nothing done with the mouse wakes the machine.
> The fact that _un_plugging the mouse didn't cause a
> wakeup has an interesting explanation. The mouse is a low-speed USB
> device, and as such is managed by the UHCI controller. Evidently that
> controller really was disabled for wakeup, since unplugging the mouse
> didn't have any effect. But when a new USB device is plugged in, the
> system doesn't know what speed it runs at. So the device is
> attached first to EHCI, and then if it proves not to be high-speed it
> gets switched electronically over to UHCI. Thus the plug-in event
> stimulated the EHCI controller to cause a wakeup.
>
> This does seem like a firmware problem, but maybe Rafael
> can suggest a way to work around it.
That would be awesome. I'm able to test any patches you might cook up.
Thanks!
next prev parent reply other threads:[~2009-01-30 14:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 17:49 Acer Aspire 1690 Suspend/Hibernate Report with 2.6.29-rc3 Daniel Qarras
2009-01-29 18:13 ` Linus Torvalds
2009-01-29 20:20 ` Daniel Qarras
2009-01-29 20:36 ` Linus Torvalds
2009-01-29 20:47 ` Alan Stern
2009-01-29 21:27 ` Daniel Qarras
2009-01-29 23:24 ` Alan Stern
2009-01-30 14:33 ` Daniel Qarras [this message]
2009-01-30 14:54 ` Alan Stern
2009-02-07 9:21 ` Pavel Machek
2009-02-07 22:24 ` Daniel Qarras
2009-02-07 23:41 ` Rafael J. Wysocki
2009-02-09 15:43 ` Daniel Qarras
2009-02-08 10:32 ` Pavel Machek
2009-02-08 11:11 ` Daniel Qarras
2009-02-10 10:58 ` Pavel Machek
2009-02-10 14:24 ` Rafael J. Wysocki
2009-02-13 21:46 ` Pavel Machek
2009-02-13 23:01 ` Rafael J. Wysocki
2009-02-08 13:25 ` 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=333776.95358.qm@web36801.mail.mud.yahoo.com \
--to=dqarras@yahoo.com \
--cc=gregkh@suse.de \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
--cc=torvalds@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.