public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Kuehling <dvdkhlng@gmx.de>
To: adq_dvb@lidskialf.net
Cc: linux-kernel@vger.kernel.org, linux-dvb@linuxtv.org,
	franck@nenie.org, eric@lammerts.org
Subject: Re: [linux-dvb] Re: Possible kernel thread related crashes on 2.4.x
Date: 12 Sep 2003 23:09:19 +0200	[thread overview]
Message-ID: <87y8wt4su8.fsf@snail.pool> (raw)
In-Reply-To: <200309112142.55460.adq_dvb@lidskialf.net> (message from Andrew de Quincey on Thu, 11 Sep 2003 21:42:55 +0100)

>>>>> "Andrew" == Andrew de Quincey <adq_dvb@lidskialf.net> writes:

>> This would explain why my system hangs/crashes especially when
>> zapping a lot (it never crashed during continuous playback, only when
>> zapping).  I'm using MPlayer, which always re-opens the device for a
>> new channel.

> Yeah, I think the problem is exacerbated for me by the fact the
> streaming boxes have 5 cards each... so thats 5 kernel threads, so
> five times more likely for it to happen. As you say, it only occurs
> when starting/stopping streaming. Normal playback is rock solid.

> Please let me know if it fixes it.. be good to know if this is
> definitely the issue.

Seems to fix it.  Just zapped for 1h+ without problems.  Great.  With
all those recent updates to MPlayers DVB-support, I can now use my
Nova-t as full-featured DVB receiver :-)

David
-- 
GnuPG public key: http://user.cs.tu-berlin.de/~dvdkhlng/dk.gpg
Fingerprint: B17A DC95 D293 657B 4205  D016 7DEF 5323 C174 7D40


      reply	other threads:[~2003-09-12 21:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-10 22:03 Possible kernel thread related crashes on 2.4.x Andrew de Quincey
2003-09-11 11:41 ` [linux-dvb] " Johannes Stezenbach
2003-09-11 20:18 ` David Kuehling
2003-09-11 20:42   ` Andrew de Quincey
2003-09-12 21:09     ` David Kuehling [this message]

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=87y8wt4su8.fsf@snail.pool \
    --to=dvdkhlng@gmx.de \
    --cc=adq_dvb@lidskialf.net \
    --cc=eric@lammerts.org \
    --cc=franck@nenie.org \
    --cc=linux-dvb@linuxtv.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