chris_s, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:
apport-collect -p linux <replace-with-bug-number> Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags: kernel-fixed-upstream kernel-fixed-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested. For example: kernel-fixed-upstream-v3.11-rc4 This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag: needs-upstream-testing If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-VERSION-NUMBER As well, please remove the tag: needs-upstream-testing If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags: kernel-unable-to-test-upstream kernel-unable-to-test-upstream-VERSION-NUMBER Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Tags added: latest-bios-080016 needs-upstream-testing regression- potential ** Tags removed: kernel-bug-exists-upstream ** Tags added: kernel-bug-exists-upstream-3.7-rc8 ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Summary changed: - imon kernel module triggers continuous escape keystrokes + 15c2:0036 [ZOTAC NM10] imon kernel module triggers continuous escape keystrokes -- 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/1086120 Title: 15c2:0036 [ZOTAC NM10] imon kernel module triggers continuous escape keystrokes Status in “linux” package in Ubuntu: Incomplete Bug description: I have a SoundGraph LC16M VFD Display/IR Receiver (15c2:0036) in an 'origen ae' case and as soon as the imon kernel module is loaded I get a continuous stream of escape keystrokes making the system unusable until I blacklisted the module. After getting some basics like network and ssh running I started some testings on the module: loading the module with 'debug=1' revealed a continuous stream of 'intf1 decoded packet: 00 00 00 00 17 00 02 ee' in my syslog. Since everything seemd to work with natty (although I used a legacy lirc module via dkms there most of the time) I simply tested the same in my previous installation with almost the same result: The messages in syslog are the same when the module is loaded with debug, but there are no escape keystrokes present. So I compared the imon modules source code of the 2.6.38 natty kernel and the 3.2.0 precise kernel and found next to some minor changes that several new keycodes where added in imon_panel_key_table including 0x000000001700ffeell which happens to be escape. So the module received those packets all along, but did not decoded them. Now the question is: Is my SoundGraph module simply broken (I have no hardware to compare with). Is this behaviour standard for that specific device (15c2:0036) and some filter code is needed in the imon module. Is there an error somewhere else in the code generating these data packets. Did the manufacturer of my case (origen ae) some customizations to the SoundGraph module, causing this behaviour. While researching this problem I stumbled accros some entries with similar headlins in some german vdr and xbmc mailing lists, but they concluded the cause due to sticking buttons. By the way: Other than the cases powerbutton (which is looped though the module), there are no buttons on the module or connected to it. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: xbmc 1298 F.... xbmc.bin /dev/snd/pcmC0D0p: xbmc 1298 F...m xbmc.bin /dev/snd/timer: xbmc 1298 f.... xbmc.bin CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfe7fc000 irq 50' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,19daa125,00100101' Controls : 38 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfcf7c000 irq 16' Mixer name : 'Nvidia GPU 0b HDMI/DP' Components : 'HDA:10de000b,10de0101,00100200' Controls : 24 Simple ctrls : 4 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=0d41e0b3-7f19-4deb-acf4-67ad8cf5a0a9 InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120822.4) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-33-generic root=/dev/mapper/GROUP1-pp_root ro nosplash nouveau.modeset=0 rdblacklist=nouveau,lirc_imon,lirc_dev xbmc=autostart,nodiskmount ProcVersionSignature: Ubuntu 3.2.0-33.52-generic 3.2.31 RelatedPackageVersions: linux-restricted-modules-3.2.0-33-generic N/A linux-backports-modules-3.2.0-33-generic N/A linux-firmware 1.79.1 RfKill: Error: [Errno 2] No such file or directory StagingDrivers: cxd2099 Tags: precise staging Uname: Linux 3.2.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/11/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: NM10 dmi.board.vendor: ZOTAC dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd03/11/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnZOTAC:rnNM10:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1086120/+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
