From: Grzegorz Kulewski <kangur@polcom.net>
To: Con Kolivas <kernel@kolivas.org>
Cc: Gregoire Favre <Gregoire.Favre@freesurf.ch>,
linux-kernel@vger.kernel.org
Subject: Re: Why my computer freeze completely with xawtv ?
Date: Mon, 8 Nov 2004 09:30:23 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.60.0411080919220.32677@alpha.polcom.net> (raw)
In-Reply-To: <418EBFE5.5080903@kolivas.org>
On Mon, 8 Nov 2004, Con Kolivas wrote:
> Gregoire Favre wrote:
>> On Mon, Nov 08, 2004 at 11:08:11AM +1100, Con Kolivas wrote:
>>
>>
>>>>>> I use DVB with VDR, but I can do the crash all the time without VDR,
>>>>>> all
>>>>>> I have to do is to have xawtv running and having a process that write
>>>>>> fast enough data to an HD (I tested xfs, reiserfs, ext2 and ext3 with
>>>>>> same result). If I don't have xawtv running I can't make crashing my
>>>>>> system which is rock stable :-)
>>>>>
>>>>> Is xawtv running as root or with real time privileges? That could do it.
>>
>>
>>> What does 'top' show as the PRI for xawtv?
>>
>>
>> I just started it and see 16 as priority in top. Should I renice it or
>> start it another way ?
>
> No I was just excluding whether you were running real time or not. You are
> not, so that excludes that as the cause of your problem. I have no further
> ideas though I'm afraid.
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. :-) I know that this is
not only my problem. And I know it is not probably related with nvidia or
any other binary drivers. And it happens with zapping or mplayer v4l[12]
too. And I tried every possible configuration of cards and IRQs. Nothing
helps.
I suspect two things:
- there is some bug in bttv and similar drivers (DVB) that corrupts memory
related with internal mm and vfs structures or does something equally bad,
- or maybe PCI bandwitch is overflowed, but I do not think it should
happen.
But it is very hard to prove any of these I am afraid.
Grzegorz Kulewski
next prev parent reply other threads:[~2004-11-08 8:31 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 [this message]
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
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=Pine.LNX.4.60.0411080919220.32677@alpha.polcom.net \
--to=kangur@polcom.net \
--cc=Gregoire.Favre@freesurf.ch \
--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.