[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/925524
Title:
10.04 11.04 11.10 imon lirc not responding on boot work after suspend
resume
Status in “linux” package in Ubuntu:
Expired
Bug description:
binary package - not sure possibilities are ehci_hcd
what happended - remote did not respond on clean boot
affects mythbuntu 10.04, 11.04 & 11.10 with kernel series any 3.0 and above
hardware used - Asus P8H61-I Intel i3-2120 8Gb ddr3 Kingston Ram,
IMON VFD (ffdc)
symptoms - lirc (irw) ir-keytable -t will not respond to (mce) remote
key presses on cold boot or restart of system. lirc (irw) and ir-
keytable -t will respond to keypresses and the remote will function
fine in both mythfrontend and xbmc following one suspend - resume
cycle.
history of testing
Clean Install of Mythbuntu 11.10 - Vanilla kernel - Everything Works
as it should with the remote. Upgrade Kernel (for Sandy Bridge suspend
fix) via debs at mainline to any 3.0 or greater, remote stops working
all log items dmesg, syslog etc shows that lircd is ready and has
initialized the ffdc (dev input by-id = if00) device but no response.
suspend and resume cycle - remote responds and works fine in both xbmc
and mythfrontend.
Clean Install of Mythbuntu 11.04 - Exactly the same results as 11.10.
Clean Install of Mythbuntu 10.04 - Again Exactly the same results as 11.04 &
11.10.
On the 10.04 system - it is completely updated prior to 3.0 or
greater kernel install. Everything on the system functions fine other
than the reported issue. I also downloaded lirc .0.9.0 and built to
test the symptoms and they are exactly the same as above and after a
suspend resume cycle the remote works perfectly with lirc 0.8.6 as
shipped with lucid.
Noteable
By default now I see that /cat/proc/acpi/wakeup USB devices are enabled by
default with any 3.0 > kernel no need to force wakeup of a USB attched ir rcvr,
I did force a wakeup enable for /sys/bus/usb/devices/1-1/power/wakeup with no
change to the above results.
I have compared the syslog on a clean boot to the one after a suspend
resume cycle and the only thing that stands out and confuses me is the
following.
Feb 2 07:12:59 fusion kernel: [ 560.092760] pcieport 0000:00:1c.4: wake-up
capability enabled by ACPI
Feb 2 07:12:59 fusion kernel: [ 560.108715] ehci_hcd 0000:00:1d.0: wake-up
capability enabled by ACPI
Feb 2 07:12:59 fusion kernel: [ 560.124593] ehci_hcd 0000:00:1a.0: wake-up
capability enabled by ACPI
The 1a device is the imon in my case, I am not sure if the wakeup
enabling is not changed in 3.0 > kernels. The device is already awake
after a clean boot.
I will attach addtn'l reports this evening. (02-02-2012)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925524/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
