since 2.6.29-rc: apple infrared keeps system awake?
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 before?
johannes
Quoted 8 lines · Johannes Berg
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 before?
What driver is bound to this device? (what is the product ID?).
Signature · 2 lines
Jiri Kosina SUSE Labs
Quoted 11 lines · Jiri Kosina
Quoted 8 lines · Johannes Berg
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 before?
Quoted 1 line
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.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x05ac Apple, Inc. idProduct 0x8242 bcdDevice 0.16 iManufacturer 1 Apple Computer, Inc. iProduct 2 IR Receiver iSerial 0 bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 1 Apple Computer, Inc.
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 42
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 10
Device Status: 0x0000
(Bus Powered)
johannes
Quoted 8 lines · Johannes Berg
Quoted 8 lines
Quoted 7 lines
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
Quoted 4 lines
Quoted 1 line
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?
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).
Signature · 2 lines
Jiri Kosina SUSE Labs
Quoted 10 lines · Jiri Kosina
Quoted 8 lines · Johannes Berg
Quoted 8 lines
Quoted 7 lines
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
Quoted 8 lines
Quoted 4 lines
Quoted 1 line
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/devicesfor 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
Quoted 4 lines
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
Quoted 3 lines · Johannes Berg
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?
Well, you can always unbind the driver from the device, I guess that should shut it up.
But I'd like to understand why this started happening all of a sudden. Are you able to reproduce this easily?
Signature · 2 lines
Jiri Kosina SUSE Labs
Quoted 8 lines · Jiri Kosina
Quoted 3 lines · Johannes Berg
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?
Well, you can always unbind the driver from the device, I guess that should shut it up.
Ok, I'll have to write a script for that or something ;)
Quoted 2 lines
But I'd like to understand why this started happening all of a sudden. Are you able to reproduce this easily?
I've watched this issue some more over the last couple of days, and it seems that it's not (at least not only) related to the kernel version, 2.6.29-rc2 is behaving just fine right now for me. I'm almost ready to blame it only on the environment, though I don't know why a few places at university would have so much infrared signal that the device felt a need to react to them all the time.
I'll try to see whether it happens there with an older kernel too, in which case I'll just blame it on the environment and disable the device (well, I guess I want that anyway lest someone actually tries to use the IR when I'm somewhere with my laptop)
johannes