* [3.2->3.3 regression] mceusb: only every second keypress is recognised [not found] ` <4FDF2B39.1000402@gmail.com> @ 2012-06-22 4:52 ` Ben Hutchings 2012-07-15 13:25 ` Michael Schmitt 0 siblings, 1 reply; 2+ messages in thread From: Ben Hutchings @ 2012-06-22 4:52 UTC (permalink / raw) To: Jarod Wilson, linux-media; +Cc: 677727, Michael Schmitt [-- Attachment #1: Type: text/plain, Size: 1275 bytes --] [Full bug log is at <http://bugs.debian.org/677727>.] On Mon, 2012-06-18 at 15:20 +0200, Michael Schmitt wrote: > Hi Ben, > > mschmitt@ganymed:~$ dmesg |head -3 > [ 0.000000] Initializing cgroup subsys cpuset > [ 0.000000] Initializing cgroup subsys cpu > [ 0.000000] Linux version 3.3.0-rc6-686-pae (Debian > 3.3~rc6-1~experimental.1) (debian-kernel@lists.debian.org) (gcc version > 4.6.3 (Debian 4.6.3-1) ) #1 SMP Mon Mar 5 21:21:52 UTC 2012 > > that is the first kernel I found on snapshot.d.o that does show that > issue. The next one backwards is "linux-image-3.2.0-2-686-pae > (3.2.20-1)" and that one works. > > Is there anything that comes to your mind? No, but this version information should help to track down how the bug was introduced. Michael originally wrote: > with the current kernel from experimental only every second keypress is > recognized on my ir remote control. Reboot to kernel 3.2 from sid, all back to > normal. > I have no idea how the kernel could be responsible there... ok, a weird bug in > the responsible kernel module for the remote, but somehow I doubt that. The driver in question is mceusb. Ben. -- Ben Hutchings Every program is either trivial or else contains at least one bug [-- Attachment #2: This is a digitally signed message part --] [-- Type: application/pgp-signature, Size: 828 bytes --] ^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [3.2->3.3 regression] mceusb: only every second keypress is recognised 2012-06-22 4:52 ` [3.2->3.3 regression] mceusb: only every second keypress is recognised Ben Hutchings @ 2012-07-15 13:25 ` Michael Schmitt 0 siblings, 0 replies; 2+ messages in thread From: Michael Schmitt @ 2012-07-15 13:25 UTC (permalink / raw) To: Ben Hutchings; +Cc: Jarod Wilson, linux-media, 677727 Did this issue drop under everybodys radar? :) I am the person that reported that bug in the Debian bugtracker a month ago and I find it hard to believe no-one else can at least confirm that issue. As I have seen a second box with Debian wheezy and kernel 3.4 (needed because of radeon-hdmi-sound) with the *same* issue, but I think a different receiver (can't check that right now but it is a Zotac Zbox mini AD10 built-in IR-receiver). With kernel 3.2 no issue, with 3.4 only every second keypress recognized. Any thoughts about that issue would be greatly appreciated! And are there any other users out there having such kernel-related issues? Maybe some change in the kernel now needs a different kind of setup for lirc? Maybe similar to the switch from lirc drivers to in-kernel lirc / devinput? Just guessing here... regards Michael Am 22.06.2012 06:52, schrieb Ben Hutchings: > [Full bug log is at<http://bugs.debian.org/677727>.] > > On Mon, 2012-06-18 at 15:20 +0200, Michael Schmitt wrote: >> Hi Ben, >> >> mschmitt@ganymed:~$ dmesg |head -3 >> [ 0.000000] Initializing cgroup subsys cpuset >> [ 0.000000] Initializing cgroup subsys cpu >> [ 0.000000] Linux version 3.3.0-rc6-686-pae (Debian >> 3.3~rc6-1~experimental.1) (debian-kernel@lists.debian.org) (gcc version >> 4.6.3 (Debian 4.6.3-1) ) #1 SMP Mon Mar 5 21:21:52 UTC 2012 >> >> that is the first kernel I found on snapshot.d.o that does show that >> issue. The next one backwards is "linux-image-3.2.0-2-686-pae >> (3.2.20-1)" and that one works. >> >> Is there anything that comes to your mind? > No, but this version information should help to track down how the bug > was introduced. > > Michael originally wrote: >> with the current kernel from experimental only every second keypress is >> recognized on my ir remote control. Reboot to kernel 3.2 from sid, all back to >> normal. >> I have no idea how the kernel could be responsible there... ok, a weird bug in >> the responsible kernel module for the remote, but somehow I doubt that. > The driver in question is mceusb. > > Ben. > ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2012-07-15 13:25 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20120616142624.11863.63977.reportbug@ganymed.tcw.local>
[not found] ` <1339865057.4942.184.camel@deadeye.wl.decadent.org.uk>
[not found] ` <4FDE4C13.8030308@gmail.com>
[not found] ` <1339978963.4942.273.camel@deadeye.wl.decadent.org.uk>
[not found] ` <4FDF2B39.1000402@gmail.com>
2012-06-22 4:52 ` [3.2->3.3 regression] mceusb: only every second keypress is recognised Ben Hutchings
2012-07-15 13:25 ` Michael Schmitt
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.