linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Boettcher <patrick.boettcher@posteo.de>
To: JPT <j-p-t@gmx.net>
Cc: linux-media@vger.kernel.org
Subject: Re: technisat-usb2: i2c-error
Date: Thu, 9 Oct 2014 17:26:14 +0200	[thread overview]
Message-ID: <20141009172614.5e16f240@vdr> (raw)
In-Reply-To: <5434226B.3010804@gmx.net>

Hi Jan,

On Tue, 07 Oct 2014 19:27:07 +0200 JPT <j-p-t@gmx.net> wrote:
> 01:14:52 VDR fails to start because there is no recording device.
> 
> I was able to get things running by unloading the modules and loading
> them again. After that I started VDR.
> 
> What exactly do the i2c-errors mean? Find attached a
> "grep i2c-error syslog*"

I can't tell you exactly what happens in the device, but I can tell you
that I have the same problem with my device on my PC sometimes. 

In addition to this I2c-failures from time to time the box is quite
sensitive regarding: repowering, replugging and host-rebooting. This is
a USB-device-firmware problem which makes the device crash and all
subsequent USB-transfers are failed. Reloading the module or replugging
the device will make it work again.

I lost contact with Technisat some time ago and wouldn't be able easily
to get the information (and I doubt they have a solution for this
problem - up to them to prove me wrong).

How many days without interruption did you use the device?

I was following quietly you're discussion with Antti. Has someone taken
care of the your changes regarding the transfer-size?

I think it should included.

regards,
-- 
Patrick.

  reply	other threads:[~2014-10-09 15:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-07 17:27 technisat-usb2: i2c-error JPT
2014-10-09 15:26 ` Patrick Boettcher [this message]
2014-10-10 10:09   ` JPT
2014-10-11 15:45     ` Patrick Boettcher

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=20141009172614.5e16f240@vdr \
    --to=patrick.boettcher@posteo.de \
    --cc=j-p-t@gmx.net \
    --cc=linux-media@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;
as well as URLs for NNTP newsgroup(s).