All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Knorr <kraxel@bytesex.org>
To: Grzegorz Kulewski <kangur@polcom.net>
Cc: Con Kolivas <kernel@kolivas.org>,
	Gregoire Favre <Gregoire.Favre@freesurf.ch>,
	linux-kernel@vger.kernel.org
Subject: Re: Why my computer freeze completely with xawtv ?
Date: 08 Nov 2004 10:17:39 +0100	[thread overview]
Message-ID: <87bre88zt8.fsf@bytesex.org> (raw)
In-Reply-To: <Pine.LNX.4.60.0411080919220.32677@alpha.polcom.net>

Grzegorz Kulewski <kangur@polcom.net> writes:

> I am seeing the same problem with my bttv card. It was present in the
> 2.4 day and is present to this day. There are some kernels that are
> more probable to hang while others are less. It does not depend on -ck
> or any other patchset or scheduling. I reported it to bttv maintainer
> year or two ago, but it looks like he is very unresponsive. :-)

Well, if it happens almost independant of the kernel/driver version it
most likely is buggy hardware.  I can't do much about it ...

Well known example are some via chipsets which have trouble with
multiple devices doing DMA at the same time (those tend to run stable
with bttv once you've turned off ide-dma ...).

Getting broken hardware run stable and fast is black magic.  You can
try these (if that happens to help we can put that info into the pci
quirks btw.):

  eskarina kraxel ~# modinfo bttv | grep "pci config"
  parm: vsfx:set VSFX pci config bit [yet another chipset flaw workaround]
  parm: triton1:set ETBF pci config bit [enable bug compatibility for triton1 + others]

Otherwise BIOS updates, obscure BIOS settings, shuffling cards in PCI
slots, enable/disable ACPI and/or APIC, whatelse may or may not help.

See also Documentation/video4linux/bttv/README.freeze

good luck,

  Gerd

-- 
#define printk(args...) fprintf(stderr, ## args)

  parent reply	other threads:[~2004-11-08  9:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-07 22:46 Why my computer freeze completely with xawtv ? Gregoire Favre
2004-11-07 23:53 ` Con Kolivas
2004-11-08  0:02   ` Gregoire Favre
2004-11-08  0:08     ` Con Kolivas
2004-11-08  0:33       ` Gregoire Favre
2004-11-08  0:37         ` Con Kolivas
2004-11-08  0:41           ` Gregoire Favre
2004-11-08  8:30           ` Grzegorz Kulewski
2004-11-08  9:08             ` Arnd Bergmann
2004-11-08  9:17             ` Gerd Knorr [this message]
2004-11-08 11:04               ` Grzegorz Kulewski
2004-11-08 18:52               ` Gregoire Favre
2004-11-08 21:28                 ` Gerd Knorr
2004-11-08 20:57             ` Olaf Titz
2004-11-08 23:45               ` Gerd Knorr
2004-11-09 20:10                 ` Olaf Titz
2004-11-09 20:40                   ` Valdis.Kletnieks
2004-11-11 21:56                     ` Olaf Titz

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=87bre88zt8.fsf@bytesex.org \
    --to=kraxel@bytesex.org \
    --cc=Gregoire.Favre@freesurf.ch \
    --cc=kangur@polcom.net \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.