From: Hans Verkuil <hverkuil@xs4all.nl>
To: Johann Klammer <klammerj@a1.net>
Cc: m.chehab@samsung.com, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH][RESEND][TRIVIAL] Turn bothersome error into a debug message
Date: Mon, 27 Oct 2014 14:57:16 +0100 [thread overview]
Message-ID: <544E4F3C.1010509@xs4all.nl> (raw)
In-Reply-To: <544E4C57.9080302@a1.net>
Hi Johann,
I've added this to my todo list and will look at this soon (next Friday or Monday
most likely).
Hans
On 10/27/2014 02:44 PM, Johann Klammer wrote:
> Let's see if that works now...
>
> On 09/30/2014 07:21 PM, Johann Klammer wrote:
>> Hello,
>>
>> After updating the kernel to 3.14.15 I am seeing these messages:
>>
>> [273684.964081] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep
>> timed out while waiting for registers getting programmed
>> [273690.020061] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep
>> timed out while waiting for registers getting programmed
>> [273695.076082] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep
>> timed out while waiting for registers getting programmed
>> [273700.132077] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep
>> timed out while waiting for registers getting programmed
>> [273705.188070] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep
>> timed out while waiting for registers getting programmed
>> [273710.244066] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep
>> timed out while waiting for registers getting programmed
>> [273715.300187] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep
>> timed out while waiting for registers getting programmed
>> [273720.356068] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep
>> timed out while waiting for registers getting programmed
>> [273725.412188] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep
>> timed out while waiting for registers getting programmed
>> [273730.468094] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep
>> timed out while waiting for registers getting programmed
>> [273735.524070] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep
>> timed out while waiting for registers getting programmed
>> [273740.580176] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep
>> timed out while waiting for registers getting programmed
>>
>> filling up the logs(one about every 5 seconds).
>>
>> The TV card is a Terratec Cinergy 1200 DVBS (I believe.. it's rather old).
>>
>> I can not observe any erratic behavior, just those pesky messages...
>>
>> I see there was an earlier post here in 2008 about a similar
>> problem...(Cinergy 1200 DVB-C... a coincidence?)
>>
>> What does it mean?
>> Do I need to be worried?
>>
>> I am using a debian testing on a 32 bit box.
>> The previous kernel was linux-image-3.12-1-486.
>> It did not show those messages, but maybe due to some configure
>> options... I built this one from linux-source-3.14...
>>
> Answering my own question:
> Other posts suggests that it is not actually an error on cards without a
> CI interface. Here's a patch that turns it into a debug message, so it
> does not clobber the logs.
>
> Signed-off-by: Johann Klammer <klammerj@a1.net>
> --- linux-source-3.14/drivers/media/common/saa7146/saa7146_core.c.orig 2014-07-31 23:51:43.000000000 +0200
> +++ linux-source-3.14/drivers/media/common/saa7146/saa7146_core.c 2014-10-06 18:57:54.000000000 +0200
> @@ -71,7 +71,7 @@ static inline int saa7146_wait_for_debi_
> if (saa7146_read(dev, MC2) & 2)
> break;
> if (err) {
> - pr_err("%s: %s timed out while waiting for registers getting programmed\n",
> + pr_debug("%s: %s timed out while waiting for registers getting programmed\n",
> dev->name, __func__);
> return -ETIMEDOUT;
> }
>
>
prev parent reply other threads:[~2014-10-27 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 17:21 saa7146_wait_for_debi_done_sleep timed out Johann Klammer
2014-10-13 7:12 ` [PATCH] Turn bothersome error into a debug message Johann Klammer
2014-10-27 13:44 ` [PATCH][RESEND][TRIVIAL] " Johann Klammer
2014-10-27 13:57 ` Hans Verkuil [this message]
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=544E4F3C.1010509@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=klammerj@a1.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=trivial@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;
as well as URLs for NNTP newsgroup(s).