public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Linos <info@linos.es>
To: linux-media@vger.kernel.org
Subject: bttv problem
Date: Sun, 19 Dec 2010 13:54:00 +0100	[thread overview]
Message-ID: <4D0E0068.5040706@linos.es> (raw)

Hi,
	i have 2 Provideo PV150 multi-capture PCI board video cards  (4 bt878 chipsets 
in every board), i have the four ports of the first multi-capture boards used in 
a xorg session with 4 instances of tvtime application showing the realtime of 
the four ports, and the other one recording with Helix producer.

Many times a day i have this errors in kernel:

[447547.296022] bttv7: timeout: drop=3276 irq=1957469/35501901, risc=204bb9ac, 
bits: HSYNC OFLOW
[447547.836020] bttv7: timeout: drop=3287 irq=1957508/35501981, risc=2a9a89ac, 
bits: HSYNC OFLOW
[448114.536016] bttv6: timeout: drop=4747 irq=26301665/59788770, risc=2050c998, 
bits: HSYNC OFLOW
[449923.196018] bttv1: timeout: drop=57206 irq=33728690/35680137, risc=19d83acc, 
bits: HSYNC OFLOW FBUS
[449923.736024] bttv1: timeout: drop=57217 irq=33728729/35680176, risc=344faf20, 
bits: HSYNC OFLOW FBUS

Tvtime seems to survive but the helix producer processess die with this error, 
if i don't load the xorg session with tvtime and at the same time I disable acpi 
in linux i don't get this erros, i have tried to disable acpi because i have 
read about other people having the same problem and fixing this way, but if i 
use tvtime at the same time the problem remains regardless of the acpi status, i 
have now gbuffers at 16 but still the same result.

My system it is using debian squeeze with 2.6.32 kernel in a Asus P5E-V HDMI 
with an intel G-35 chipset.

Any ideas on how i could fix this problem please?

Regards,
Miguel Angel.

             reply	other threads:[~2010-12-19 12:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-19 12:54 Linos [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-07-06 23:15 bttv problem Linos
2009-06-17  8:49 Linos
2009-07-05 22:29 ` Linos
2009-07-06  1:14   ` hermann pitton
2009-07-06 23:03     ` Linos

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=4D0E0068.5040706@linos.es \
    --to=info@linos.es \
    --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