From: Gregoire Favre <Gregoire.Favre@freesurf.ch>
To: Gerd Knorr <kraxel@bytesex.org>
Cc: Grzegorz Kulewski <kangur@polcom.net>,
Con Kolivas <kernel@kolivas.org>,
linux-kernel@vger.kernel.org
Subject: Re: Why my computer freeze completely with xawtv ?
Date: Mon, 8 Nov 2004 19:52:49 +0100 [thread overview]
Message-ID: <20041108185249.GK5360@magma.epfl.ch> (raw)
In-Reply-To: <87bre88zt8.fsf@bytesex.org>
On Mon, Nov 08, 2004 at 10:17:39AM +0100, Gerd Knorr wrote:
> Well, if it happens almost independant of the kernel/driver version it
> most likely is buggy hardware. I can't do much about it ...
? Why couldn't it be a bug present in all kernels/drivers ?
Under bugs.gentoo.org there are quiete a lots of those, for example
http://bugs.gentoo.org/show_bug.cgi?id=64728 and google can show a lots
more.
> 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 ...).
I had those xawtv crash with an SCSI only system, and on all my
MB/CPU/RAM test I doubt that all hardware configuration were buggy.
> 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
I only have DVB hardware, is that also considered as bttv ?
I have tried a lots of different configuration, with or without fb,
playing in the BIOS, pre-empt/no, ACPI/noACPI ... no change at all.
Some things I have noticed : xawtv and kdetv don't need CPU to achieve
the best quality I know about BUT they make the system crash.
kvdr and tvtime needs lots of time and there quality are really lower
than the two others, BUT they don't crash my system.
I can't speak about xawdecode because I am not able to run it under
amd64... neither zapping.
What I do now is to stop xawtv before doing a large copy of files...
I would happily try any suggestion :-)
Thank you very much,
--
Grégoire Favre
________________________________________________________________________
http://magma.epfl.ch/greg ICQ:16624071 mailto:Gregoire.Favre@freesurf.ch
next prev parent reply other threads:[~2004-11-08 18:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-07 22:46 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
2004-11-08 11:04 ` Grzegorz Kulewski
2004-11-08 18:52 ` Gregoire Favre [this message]
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=20041108185249.GK5360@magma.epfl.ch \
--to=gregoire.favre@freesurf.ch \
--cc=kangur@polcom.net \
--cc=kernel@kolivas.org \
--cc=kraxel@bytesex.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®