0e9c:0000 streamzap IR module floods dmesg
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Low
|
Unassigned | ||
Maverick |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
After upgrading from 10.04 I noticed a flood of message in dmesg like :
streamzap 3-1:1.0: streamzap_callback: received urb, len 2
streamzap 3-1:1.0: sz idx 0: f
streamzap 3-1:1.0: sz idx 1: ff
Has been for a while, but it finally got in my way enough to force me to find out what was going on.
To reproduce it, looks like you just need a streamzap and to press some buttons on it.
I think the problem is in the driver:
/drivers/
in the function streamzap_callback
The lines:
dev_info(sz->dev, "%s: received urb, len %d\n", __func__, len);
and
dev_info(sz->dev, "sz idx %d: %x\n",
i, (unsigned char)sz-
which are the messages swamping dmesg.
I think what is meant to happen is that these lines are only done if "debug" is true. Then you can control this logging with the "/sys/module/
I emailed the maintainer and he said it was fixed four or five months ago. So can we have this fixed back ported? Or at very least some temporary fix. Compiling my own streamzap module every kernel release would soon get as annoying as the dmesg flood. Especially for something so simple to fix in the right place.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-
Regression: Yes
Reproducible: Yes
ProcVersionSign
Uname: Linux 2.6.35-24-generic i686
NonfreeKernelMo
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
/dev/snd/
/dev/snd/pcmC0D0p: jk 1628 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'I82801DBICH4'
Mixer name : 'Analog Devices AD1981A'
Components : 'AC97a:41445372'
Controls : 25
Simple ctrls : 17
Card1.Amixer.info:
Card hw:1 'Live'/'SB Live! Value [CT4670] (rev.4, serial:0x201102) at 0xd400, irq 19'
Mixer name : 'TriTech TR28023'
Components : 'AC97a:54524103'
Controls : 216
Simple ctrls : 38
Card2.Amixer.info:
Card hw:2 'U0x46d0x805'/'USB Device 0x46d:0x805 at usb-0000:00:1d.7-3, high speed'
Mixer name : 'USB Mixer'
Components : 'USB046d:0805'
Controls : 2
Simple ctrls : 1
Card2.Amixer.
Simple mixer control 'Mic',0
Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
Capture channels: Mono
Limits: Capture 0 - 6144
Mono: Capture 0 [0%] [6.00dB] [on]
Date: Sun Jan 9 22:02:21 2011
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
vboxnet0 no wireless extensions.
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
PATH=(custom, user)
LANG=en_GB.utf8
SHELL=/bin/bash
RelatedPackageV
RfKill:
SourcePackage: linux
dmi.bios.date: 07/14/2003
dmi.bios.vendor: Intel Corp.
dmi.bios.version: RG84510A.
dmi.board.name: D845GBV
dmi.board.vendor: Intel Corporation
dmi.board.version: AAA84538-204
dmi.chassis.type: 2
dmi.modalias: dmi:bvnIntelCor
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
Joe Burmeister, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012. /wiki.ubuntu. com/Releases
Please see this document for currently supported Ubuntu releases:
https:/
We were wondering if this is still an issue in a supported release? If so, can you try with the latest development release of Ubuntu? ISO CD images are available from http:// cdimage. ubuntu. com/releases/ .
If it remains an issue, could you run the following command in a supported release from a Terminal (Applications- >Accessories- >Terminal) . It will automatically gather and attach updated debug information to this report.
apport-collect -p linux <replace- with-bug- number>
Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https:/ /wiki.ubuntu. com/KernelMainl ineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please remove the 'needs- upstream- testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs- upstream- testing' text. As well, please comment on which kernel version specifically you tested.
If this bug is fixed in the mainline kernel, please add the following tag 'kernel- fixed-upstream' .
If the mainline kernel does not fix this bug, please add the tag: 'kernel- bug-exists- upstream' .
If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel- unable- to-test- upstream' , and comment as to why specifically you were unable to test it.
Please let us know your results. Thanks in advance.
Helpful Bug Reporting Links: /help.ubuntu. com/community/ ReportingBugs# Bug_Reporting_ Etiquette /help.ubuntu. com/community/ ReportingBugs# A3._Make_ sure_the_ bug_hasn. 27t_already_ been_reported /help.ubuntu. com/community/ ReportingBugs# Adding_ Apport_ Debug_Informati on_to_an_ Existing_ Launchpad_ Bug /help.ubuntu. com/community/ ReportingBugs# Adding_ Additional_ Attachments_ to_an_Existing_ Launchpad_ Bug
https:/
https:/
https:/
https:/