public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@brturbo.com.br>
To: 7eggert@gmx.de
Cc: Jeremy Laine <jeremy.laine@polytechnique.org>,
	linux-kernel@vger.kernel.org,
	"v4l >> Linux and Kernel Video" <video4linux-list@redhat.com>
Subject: Re: OOPS: frequent crashes with bttv in 2.6.X series (inc. 2.6.12)
Date: Fri, 08 Jul 2005 14:19:10 -0300	[thread overview]
Message-ID: <42CEB58E.5030401@brturbo.com.br> (raw)
In-Reply-To: <E1DqYg4-0001fC-VN@be1.7eggert.dyndns.org>

Bodo Eggert wrote:
> Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org> wrote:
> 
> 
>>Now I've upgraded to X.org 6.8.2 and done a first stress-test (copying
>>large files from network to local HDD), and I still can post.
> 
> 
> It occured again. So it wasn't that easy.

Bodo/Jeremy/Castet,

	It looks to be an old reported trouble with bttv cards.

	There is a doc at kernel that treats this subject. It is at:
		Documentation/video4linux/bttv/README.freeze


	Overlay works by transfering data from BTTV card directelly to Video Card.

	This looks to be problem related to DMA troubles on some motherboards.
Some chipsets (via being most prominent) have problems with DMA
transfers between two PCI cards (or PCI to AGP) that affects overlay. It
may also be related with multiple devices using DMA at the same time.

	Castet did mention, on this thread, that this is causing also disk
corruption on his machine, with is an inication that this is the case.

	Anyway, it doesn't seem to be a V4L specific issue.

Mauro.

  reply	other threads:[~2005-07-08 17:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4nrlt-8po-15@gated-at.bofh.it>
     [not found] ` <4nrlt-8po-13@gated-at.bofh.it>
2005-07-07 15:52   ` OOPS: frequent crashes with bttv in 2.6.X series (inc. 2.6.12) Bodo Eggert
2005-07-08 17:19     ` Mauro Carvalho Chehab [this message]
2005-07-09  7:34       ` Bodo Eggert
     [not found] <4njei-1Ps-21@gated-at.bofh.it>
2005-07-06 23:09 ` Bodo Eggert
2005-07-07  8:17   ` Duncan Sands
2005-07-07  8:31   ` Jeremy Laine
2005-07-06 15:02 Piszcz, Justin
2005-07-06 20:46 ` Lee Revell
  -- strict thread matches above, loose matches on Subject: below --
2005-07-06 10:11 Jeremy Laine
2005-07-06 14:44 ` Michael Krufky
2005-07-07 14:31   ` Lee Revell
2005-07-07 14:35     ` Michael Krufky
2005-07-06 14:59 ` Alexey Dobriyan
2005-07-07  8:25   ` Jeremy Laine
2005-07-07 15:12     ` Mauro Carvalho Chehab
2005-07-07 15:35       ` Jeremy Laine
2005-07-07 16:17       ` matthieu castet
2005-07-07 19:11         ` Duncan Sands

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=42CEB58E.5030401@brturbo.com.br \
    --to=mchehab@brturbo.com.br \
    --cc=7eggert@gmx.de \
    --cc=jeremy.laine@polytechnique.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=video4linux-list@redhat.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