From: Johannes Stezenbach <js@convergence.de>
To: Andrew de Quincey <adq_dvb@lidskialf.net>
Cc: linux-kernel@vger.kernel.org, linux-dvb@linuxtv.org,
franck@nenie.org, eric@lammerts.org
Subject: Re: [linux-dvb] Possible kernel thread related crashes on 2.4.x
Date: Thu, 11 Sep 2003 13:41:47 +0200 [thread overview]
Message-ID: <20030911114147.GC668@convergence.de> (raw)
In-Reply-To: <200309102303.34095.adq_dvb@lidskialf.net>
Andrew de Quincey wrote:
> Hi, I've been having fatal oopses with some of my DVB receiver systems
> when restarting streaming recently (i.e. opening/closing DVB devices).
> I've only just got into the office with a debug cable to find out what has happening.
>
> Anyway, here are the important parts of the oops (full oops at end of mail):
> Unable to handle kernel paging request at virtual address d905a984
> ...
> Trace; c011c79c <free_uid+2c/34>
> Trace; c011767b <release_task+2b/16c>
> Trace; c0118337 <sys_wait4+307/390>
> Trace; c0106c03 <system_call+33/38>
>
> Does this look familiar to anyone? I mean specifically this thread on linux-dvb (among others):
> http://www.linuxtv.org/mailinglists/linux-dvb/2003/04-2003/msg00291.html
I get this crash from time to time, and it was also reported on the
linux-dvb list recently:
http://www.linuxtv.org/mailinglists/linux-dvb/2003/08-2003/msg00361.html
But AFAIK there aren't many people who get this, and I didn't find any
possible cause in the DVB drivers.
> Searching about found me this patch on LKML:
> http://hypermail.idiosynkrasia.net/linux-kernel/archived/2003/week04/0468.html
>
> Which I applied to 2.4.21, and which appears to fix the problem. At least,
> I was able to continually restart streaming for 4 hours this afternoon without a problem.
> Previously, I could crash it within 15 minutes.
>
> It seems to be a bug related to kernel threads when starting/stopping them. The DVB drivers
> now do this when a DVB device is opened/closed, although I'm sure they previously left
> them running which would explain why I never saw this behaviour before.
Only the frontend driver core creates one thread per frontend for monitoring.
> My question is: is there a reason the patch has not yet made it into 2.4.x? It is not in
> 2.4.22-pre3.
If this actually fixes kernel_thread() related crashes then please apply to -pre4.
Johannes
next prev parent reply other threads:[~2003-09-11 11:41 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 ` Johannes Stezenbach [this message]
2003-09-11 20:18 ` [linux-dvb] " David Kuehling
2003-09-11 20:42 ` Andrew de Quincey
2003-09-12 21:09 ` [linux-dvb] " David Kuehling
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=20030911114147.GC668@convergence.de \
--to=js@convergence.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 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.