From: Justin Mattock <justinmattock@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-uvc-devel@lists.berlios.de
Subject: sys.log spammed with uvcvideo: unknown event type 110.
Date: Thu, 30 Apr 2009 12:56:28 -0700 [thread overview]
Message-ID: <dd18b0c30904301256h501725f9v2da376759dc04b32@mail.gmail.com> (raw)
hello I'm trying to do some webcam
testing, but seem to be having a difficult time
reading dmesg due to uvcvideo spamming
dmesg with:
Apr 30 12:40:11 unix klogd: [ 9619.151420] uvcvideo: unknown event type 0.
Apr 30 12:40:11 unix klogd: [ 9619.207427] uvcvideo: unknown event type 23.
Apr 30 12:40:11 unix klogd: [ 9619.343364] uvcvideo: unknown event type 16.
Apr 30 12:40:11 unix klogd: [ 9619.471441] uvcvideo: unknown event type 59.
Apr 30 12:40:11 unix klogd: [ 9619.647442] uvcvideo: unknown event type 110.
Apr 30 12:40:11 unix klogd: [ 9619.775439] uvcvideo: unknown event type 110.
Apr 30 12:40:12 unix klogd: [ 9619.843295] uvcvideo: unknown event type 110.
Apr 30 12:40:12 unix klogd: [ 9619.911428] uvcvideo: unknown event type 110.
Apr 30 12:40:12 unix klogd: [ 9619.979437] uvcvideo: unknown event type 110.
Apr 30 12:40:12 unix klogd: [ 9620.047421] uvcvideo: unknown event type 110.
Apr 30 12:40:12 unix klogd: [ 9620.115439] uvcvideo: unknown event type 110.
Apr 30 12:40:12 unix klogd: [ 9620.183314] uvcvideo: unknown event type 110.
Apr 30 12:40:12 unix klogd: [ 9620.247423] uvcvideo: unknown event type 110.
Apr 30 12:40:12 unix klogd: [ 9620.315407] uvcvideo: unknown event type 110.
Apr 30 12:40:12 unix klogd: [ 9620.383305] uvcvideo: unknown event type 110.
Apr 30 12:40:12 unix klogd: [ 9620.451440] uvcvideo: unknown event type 110.
is there a way I can take this message out, as a quick workaround
so I can read the rest of dmesg, and sys.log?
--
Justin P. Mattock
reply other threads:[~2009-04-30 19:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dd18b0c30904301256h501725f9v2da376759dc04b32@mail.gmail.com \
--to=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-uvc-devel@lists.berlios.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®