From: Brendon Higgins <blhiggins@gmail.com>
To: linux-media@vger.kernel.org
Subject: Regression since 2.6.25 kernel: Crash of userspace program leaves DVB device unusable
Date: Mon, 19 Jan 2009 13:37:26 +1000 [thread overview]
Message-ID: <200901191337.31272.blhiggins@gmail.com> (raw)
In-Reply-To: <200901031200.56314.blhiggins@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2187 bytes --]
Hi,
I wrote to linux-dvb (2009-01-03 12:00 pm):
> I've been coming up against a problem that seems to be with the DVB drivers
> that occurs when a program using them, usually VDR in my case, terminates
> uncleanly (segfault, general protection fault). Linux 2.6.25 doesn't have
> this problem, but 2.6.26, 2.6.27, and 2.6.28 do, though 2.6.28 manifests
> slightly differently to the others. I'll focus on what 2.6.28 does. I have
> a DViCO FusionHDTV DVB-T Plus, running on an amd64 Debian Testing (mostly)
> dual-core machine.
>
> After VDR crashes it attemps to restart itself. This was fine on 2.6.25,
> but on later kernels the crash seems to leave the device in some unusable
> state, where no program can subsequently use it - the device files
> (/dev/dvb) no longer exist. (In 2.6.2[67], the files existed, but accessing
> /dev/dvb/adapter0/dvr0 resulted in "No such device".) I had figured out
> that in order to get the device working again it is necessary to "rmmod
> cx88_dvb cx8802; modprobe cx88_dvb". This worked in 2.6.2[67] without
> trouble, but in 2.6.28, it's as if the cx88_dvb module gets lost somehow.
> It doesn't appear in lsmod, however:
> phi:~# modprobe cx88_dvb
> FATAL: Error inserting cx88_dvb
> (/lib/modules/2.6.28/kernel/drivers/media/video/cx88/cx88-dvb.ko): No such
> device
> phi:~# rmmod cx88_dvb cx8802
> ERROR: Module cx88_dvb does not exist in /proc/modules
> phi:~# modprobe cx88_dvb
>
> Note that probing it works only *after* cx8802 was unloaded. As before, now
> the device is accessible.
>
> So it seems something is wrong in the cx8802 module. Something is not being
> cleaned up after a userspace program crashes while using it, leaving the
> DVB system in a broken state.
>
> I'd very much like this to not be the case, since on my system a VDR crash
> is somewhat inevitable, and the automatic restart *was* very handy, back in
> 2.6.25.
Deafening silence. Does nobody have a clue? Or care? I just noticed I posted
to the linux-dvb list which has been deprecated, so I'm quoting it here in
its entirety in case relevent people missed it. Is there anything else I can
do?
Peace,
Brendon
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-01-19 3:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-03 2:00 [linux-dvb] Regression since 2.6.25 kernel: Crash of userspace program leaves DVB device unusable Brendon Higgins
2009-01-19 3:37 ` Brendon Higgins [this message]
2009-01-19 4:21 ` Andy Walls
2009-01-19 9:43 ` Brendon Higgins
2009-01-20 2:29 ` Andy Walls
2009-01-24 1:19 ` Brendon Higgins
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=200901191337.31272.blhiggins@gmail.com \
--to=blhiggins@gmail.com \
--cc=linux-media@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.