linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: catchall <catchall@dharty.com>
To: linux-media@vger.kernel.org
Subject: Haupage 2250 / saa7164 kernel errors
Date: Wed, 28 Jan 2015 20:43:42 -0800	[thread overview]
Message-ID: <54C9BA7E.90907@dharty.com> (raw)

About once a day, my tuner stops working and my logs fill up with the 
following messages:

2015-01-28T20:40:23.736478-08:00 mediapc kernel: [169020.845484] 
saa7164_cmd_send() No free sequences
2015-01-28T20:40:23.736480-08:00 mediapc kernel: [169020.845486] 
saa7164_api_i2c_read() error, ret(1) = 0xc
2015-01-28T20:40:23.736483-08:00 mediapc kernel: [169020.845489] 
s5h1411_readreg: readreg error (ret == -5)

I've seen a couple other posts about it in this mailing list with no 
responses yet.  Does anybody have an idea of why this could be 
happening, or any suggestions on what I could try to debug this issue?

Thanks,

David


                 reply	other threads:[~2015-01-29  4:51 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=54C9BA7E.90907@dharty.com \
    --to=catchall@dharty.com \
    --cc=linux-media@vger.kernel.org \
    --cc=v4l@dharty.com \
    /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).