linux-kernel - Re: since 2.6.29-rc: apple infrared keeps system awake?

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: <1232969733.20525.4.camel@johannes.local>
Date:	Mon, 26 Jan 2009 12:35:32 +0100
From:	Johannes Berg <johannes@...solutions.net>
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	Linux Kernel list <linux-kernel@...r.kernel.org>,
	Matthew Garrett <mjg@...hat.com>,
	Samuel Ortiz <sameo@...nedhand.com>
Subject: Re: since 2.6.29-rc: apple infrared keeps system awake?

On Mon, 2009-01-26 at 12:25 +0100, Jiri Kosina wrote:
> On Mon, 26 Jan 2009, Johannes Berg wrote:
> 
> > > > Ever since 2.6.29-rc, I see this in powertop on my macbook5,1:
> > > > Top causes for wakeups:
> > > >   24.1% ( 27.8)   USB device usb1 : OHCI Host Controller (Linux 2.6.29-rc2-wl-di
> > > >   21.5% ( 24.8)       <interrupt> : ohci_hcd:usb1 
> > > >   14.5% ( 16.7)   USB device  1-5 : IR Receiver (Apple Computer, Inc.) 
> > > > which is way way more than what it used to be, I never saw the IR 
> > > > receiver before. I could bisect, but wondered if somebody had seen this 
> > > 
> > > What driver is bound to this device? (what is the product ID?).
> > None, oddly, it seems. At least listing input devices doesn't seem to
> > show it.
> > Bus 003 Device 002: ID 05ac:8242 Apple, Inc. 
> 
> This should be driven by hid-apple/usbhid. Could you please look into 
> /sys/bus/usb/devices for this device and check where does the 'driver' 
> symlink point to?

driver -> ../../../../../bus/usb/drivers/usb
3-5:1.0/driver -> ../../../../../../bus/usb/drivers/usbhid

> Also, for this device, we force a creation of hiddev node, so it's 
> possible (and, in fact, probable), that some lirc process has the node 
> open and wakes it up periodically? (I think there is a macmini lirc 
> userspace driver, please check whether it has the hiddev node open).

Nope.

Is it possible that I was just in an environment where there was lots of
random infrared traffic that the device picked up? Is it possible to
disable it completely?

johannes

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)