lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110415145457.GA27650@eazy.amigager.de>
Date:	Fri, 15 Apr 2011 16:54:57 +0200
From:	Tino Keitel <tino.keitel@....de>
To:	Alan Stern <stern@...land.harvard.edu>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	ACPI Devel Mailing List <linux-acpi@...r.kernel.org>,
	Linux PM mailing list <linux-pm@...ts.linux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [linux-pm] /proc/acpi/wakeup regression in 2.6.39-rc3

On Fri, Apr 15, 2011 at 10:38:47 -0400, Alan Stern wrote:
> On Fri, 15 Apr 2011, Rafael J. Wysocki wrote:
> 
> > On Friday, April 15, 2011, Tino Keitel wrote:
> > > Hi,
> > > 
> > > with 2.6.38, I enabled wakeup from suspend to RAM with the USB keyboard
> > > this way:
> > > 
> > > echo USB2 > /proc/acpi/wakeup
> > > 
> > > This does not work anymore with 2.6.39-rc3. Wakeup using the keyboard
> > > won't work, and the USB2 line in /proc/acpi/wakeup doesn't change to
> > > "enabled" after the echo command.
> > > 
> > > Is this intended? If yes, what is the new way to enable keyboard
> > > wakeup?
> > 
> > No, it's supposed to work IIRC.  I'll have a look at that code tomorrow.
> 
> Tino, can you check the contents of the power/wakeup files in the
> appropriate sysfs directories?  That would be the directory for the
> keyboard device itself and the directory for the USB host controller
> for the bus the keyboard is on.
> 
> By default, power/wakeup should be "enabled" for the keyboard device 
> and "disabled" for the host controller.  If you write "enabled" into 
> the host controller's file by hand, does that fix the problem?

I already tried to write "enable" into all USB related wakeup files
yesterday, not change.

I'll check again how these files look like in 2.6.38, what sysfs
wakeup files change when writing into /proc/acpi/wakeup, and what
differences to 2.6.39-rc can be seen.

Regards,
Tino
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ