From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "linux-pm@lists.linux-foundation.org"
<linux-pm@lists.linux-foundation.org>
Subject: Re: [REGRESSION] usb devices don't wake up the system
Date: Sun, 04 Jul 2010 18:44:42 +0300 [thread overview]
Message-ID: <1278258282.3571.10.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1007040848250.16841-100000@netrider.rowland.org>
[-- Attachment #1: Type: text/plain, Size: 3605 bytes --]
On Sun, 2010-07-04 at 08:51 -0400, Alan Stern wrote:
> On Sun, 4 Jul 2010, Maxim Levitsky wrote:
>
> > > Alan. thanks for saving me from another bisect...
> > > latest git tip works again.
> >
> > I mean, I think that
> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=48826626263d4a61d06fd8c5805da31f925aefa0
> >
> > fixed the problem.
>
> Ah, yes. Well, I can't claim a lot of credit for that because I'm the
> person who introduced the regression in the first place! But at least
> it's working okay now.
>
> > > (of course I need to explicitly enable power/wakeup on the mouse), but I
> > > can live with that.)
> > >
> > >
> > > I want to note that I still need to enable wakeup in /power/acpi/wakeup
> > > to make USB mouse wakeup the system.
> > > This isn't a regression, but I thought that I don't need that anymore.
>
> You shouldn't. Which setting in /proc/acpi/wakeup needs to be enabled?
The wakeup GPE for UHCI controller which is connected to the mouse.
maxim@MAIN:/sys/bus/pci/devices/0000:00:1d.0/usb5$ cat /proc/acpi/wakeup
Device S-state Status Sysfs node
SLPB S4 *enabled
P32 S4 *disabled pci:0000:00:1e.0
UAR1 S4 *disabled pnp:00:0a
ILAN S4 *disabled pci:0000:00:19.0
PEGP S4 *disabled
PEX0 S4 *disabled pci:0000:00:1c.0
PEX1 S4 *disabled pci:0000:00:1c.1
PEX2 S4 *disabled pci:0000:00:1c.2
PEX3 S4 *disabled pci:0000:00:1c.3
PEX4 S4 *disabled pci:0000:00:1c.4
PEX5 S4 *disabled
UHC1 S3 *enabled pci:0000:00:1d.0
UHC2 S3 *disabled pci:0000:00:1d.1
UHC3 S3 *disabled pci:0000:00:1d.2
UHC4 S3 *disabled
EHCI S3 *disabled pci:0000:00:1d.7
EHC2 S3 *disabled pci:0000:00:1a.7
UH42 S3 *disabled pci:0000:00:1a.0
UHC5 S3 *disabled pci:0000:00:1a.1
AZAL S3 *disabled pci:0000:00:1b.0
maxim@MAIN:/sys/bus/pci/devices/0000:00:1d.0/usb5$ cd 5-1/
5-1:1.0/ driver/ ep_00/ power/ subsystem/
maxim@MAIN:/sys/bus/pci/devices/0000:00:1d.0/usb5$ cd 5-1/
maxim@MAIN:/sys/bus/pci/devices/0000:00:1d.0/usb5/5-1$
maxim@MAIN:/sys/bus/pci/devices/0000:00:1d.0/usb5/5-1$
maxim@MAIN:/sys/bus/pci/devices/0000:00:1d.0/usb5/5-1$ cat idVendor
1241
maxim@MAIN:/sys/bus/pci/devices/0000:00:1d.0/usb5/5-1$ lsusb
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 003: ID 1241:1166 Belkin MI-2150 Trust Mouse
Bus 005 Device 002: ID 06a3:ff52 Saitek PLC Cyborg 3D Rumble Force Joystick
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
maxim@MAIN:/sys/bus/pci/devices/0000:00:1d.0/usb5/5-1$
Also, I tried to enable wakeup on the USB mouse using udev rule.
I did that rule for a test (very broad for testing):
SUBSYSTEM=="usb", ACTION=="add", ATTR{power/wakeup}="enabled"
I found that running udevd --debug confirms that it writes that attribute
(Log of mouse attach attached :-). (I connected it to different port now)
According to the log, udev does write 'enabled' to
/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-2/power/wakeup
but:
maxim@MAIN:~$ cat /sys/devices/pci0000:00/0000:00:1a.0/usb3/3-2/power/wakeup
disabled
This looks like kernel bug.
I am not against the default of disabled wakeup, it fact I welcome that,
but I think that udev rule should work to enable it back.
Best regards,
Maxim Levitsky
[-- Attachment #2: udev_log.txt.gz --]
[-- Type: application/x-gzip, Size: 3064 bytes --]
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2010-07-04 15:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-30 23:31 [REGRESSION] usb devices don't wake up the system Maxim Levitsky
2010-06-30 23:40 ` Rafael J. Wysocki
2010-07-01 0:28 ` Maxim Levitsky
2010-07-01 14:42 ` Alan Stern
2010-07-01 18:58 ` Rafael J. Wysocki
2010-07-01 20:44 ` Maxim Levitsky
2010-07-01 21:07 ` Rafael J. Wysocki
2010-07-03 22:41 ` Maxim Levitsky
2010-07-03 22:42 ` Maxim Levitsky
2010-07-03 23:27 ` Rafael J. Wysocki
2010-07-04 12:51 ` Alan Stern
2010-07-04 15:44 ` Maxim Levitsky [this message]
2010-07-06 15:17 ` Alan Stern
2010-07-06 16:51 ` Maxim Levitsky
2010-07-06 17:07 ` Alan Stern
2010-07-06 20:51 ` Maxim Levitsky
2010-07-06 23:05 ` Rafael J. Wysocki
2010-07-07 15:33 ` Alan Stern
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=1278258282.3571.10.camel@localhost.localdomain \
--to=maximlevitsky@gmail.com \
--cc=linux-pm@lists.linux-foundation.org \
--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