From: Bongani <bhlope@mweb.co.za>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, kraxel@bytesex.org
Subject: [Patch] 2.5.44 Stop bttv_driver.c from flooding /var/log/messages
Date: Tue, 22 Oct 2002 22:02:22 +0200 [thread overview]
Message-ID: <200210222202.22801.bhlope@mweb.co.za> (raw)
[-- Attachment #1: Type: text/plain, Size: 609 bytes --]
Hi Alan
I have sent this patch to Gerd and I did not get any reply from him, so...
The bttv drivers are/were filling up my /var/log/messages file with the
following output
Oct 20 04:03:01 localhost kernel: bttv0: amux: mode=-1 audio=1 signal=no
mux=4/1 irq=yes
Oct 20 04:03:01 localhost kernel: bttv0: amux: mode=-1 audio=1 signal=yes
mux=1/1 irq=yes
Oct 20 04:03:08 localhost kernel: bttv0: amux: mode=-1 audio=1 signal=no
mux=4/1 irq=yes
(Which seems to repeat three times a second for three seconds and waits 7
second before printing the message again)
The following patch quites them down.
Thanx
[-- Attachment #2: bttv.patch --]
[-- Type: text/x-diff, Size: 610 bytes --]
--- linux-2.5/drivers/media/video/bttv-driver.c.old 2002-10-21 00:08:50.000000000 +0200
+++ linux-2.5/drivers/media/video/bttv-driver.c 2002-10-21 00:09:17.000000000 +0200
@@ -813,7 +813,7 @@
i2c_mux = mux = (btv->audio & AUDIO_MUTE) ? AUDIO_OFF : btv->audio;
if (btv->opt_automute && !signal && !btv->radio_user)
mux = AUDIO_OFF;
- printk("bttv%d: amux: mode=%d audio=%d signal=%s mux=%d/%d irq=%s\n",
+ dprintk(KERN_DEBUG "bttv%d: amux: mode=%d audio=%d signal=%s mux=%d/%d irq=%s\n",
btv->nr, mode, btv->audio, signal ? "yes" : "no",
mux, i2c_mux, in_interrupt() ? "yes" : "no");
next reply other threads:[~2002-10-22 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-22 20:02 Bongani [this message]
2002-10-22 21:04 ` Bjoern A. Zeeb
2002-10-23 6:39 ` Gerd Knorr
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=200210222202.22801.bhlope@mweb.co.za \
--to=bhlope@mweb.co.za \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=kraxel@bytesex.org \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome