From: Adrian Bunk <bunk@stusta.de>
To: Bradley Reed <bradreed1@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: MPlayer broken under 2.6.15-rc7-rt1?
Date: Sun, 1 Jan 2006 14:16:16 +0100 [thread overview]
Message-ID: <20060101131615.GT3811@stusta.de> (raw)
In-Reply-To: <20060101145402.0c6292bb@galactus.example.org>
On Sun, Jan 01, 2006 at 02:54:02PM +0200, Bradley Reed wrote:
> On Sun, 1 Jan 2006 12:50:38 +0100
> Adrian Bunk <bunk@stusta.de> wrote:
>
> > MPlayer has more than enough output drivers including some that work
> > without the nvidia module.
> >
> > If your problem was an RTC one, it might have even trigger using the
> > AAlib output driver.
>
> True, I can reproduce this kernel bug by running mplayer with AAlib
> output without nvidia's module loaded. I never run mplayer under usual
> use with the aalib library and never thought to test with it. If I had
> been asked to try that, I would have.
>
> Yes, I understand that GPL fanatics like Arjan refuse to look at bugs
> from tainted kernels, regardless of whether the tainted kernel module
> is at fault. That is his right. So be it.
>...
It's not about the GPL, it's simply a matter of fact that noone can
debug a kernel if any binary-onluy module was ever loaded.
There have been too many problems in the past where after hours of
debugging it turned out that it wasn't reproducible without the nvidia
module.
> Reporting all kernel bugs SOLELY to the source of a binary kernel
> module (NVidia in my case) is rather pointless as the only thing that
> changed in my system is the kernel. Their logical conclusion is the bug
> is in the part of the system that changed, i.e. the kernel. In this
> case it was a kernel bug as Mr. Rostedt's patch showed.
>...
A kernel module can do _anything it wants_ in the whole kernel.
If the nvidia module did something in a strange and completely
unsupported way or if the nvidia module contained a bug that only
wasn't triggered before a bug might not be in the changed kernel.
In your case the bug was in the kernel, but who can debug such bugs?
We don't have the sources for the nvidia module.
The nvidia developers have the source of the kernel.
Guess who has the source of everything involved and can therefore
debug the problem...
> Brad
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-01-01 13:16 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-31 18:29 MPlayer broken under 2.6.15-rc7-rt1? Bradley Reed
2005-12-31 18:47 ` Alistair John Strachan
2005-12-31 18:59 ` Bradley Reed
2005-12-31 19:14 ` Alistair John Strachan
2005-12-31 19:51 ` Steven Rostedt
2005-12-31 20:07 ` Bradley Reed
2005-12-31 20:33 ` Steven Rostedt
2005-12-31 20:58 ` Jan Engelhardt
2005-12-31 22:46 ` RTC broken under 2.6.15-rc7-rt1 (was: Re: MPlayer broken under 2.6.15-rc7-rt1?) Steven Rostedt
2005-12-31 23:22 ` Bradley Reed
2006-01-01 0:04 ` Steven Rostedt
2006-01-01 9:14 ` MPlayer broken under 2.6.15-rc7-rt1? Arjan van de Ven
2006-01-01 9:51 ` Bradley Reed
2006-01-01 11:26 ` Arjan van de Ven
2006-01-01 12:12 ` jerome lacoste
2006-01-01 12:25 ` Arjan van de Ven
2006-01-02 9:57 ` [OT] " jerome lacoste
2006-01-01 13:28 ` Arjan van de Ven
2006-01-01 14:21 ` Alexander E. Patrakov
2006-01-01 17:50 ` Prakash Punnoor
2006-01-01 11:50 ` Adrian Bunk
[not found] ` <20060101145402.0c6292bb@galactus.example.org>
2006-01-01 13:16 ` Adrian Bunk [this message]
2006-01-01 13:25 ` Arjan van de Ven
2006-01-01 13:41 ` Steven Rostedt
2006-01-01 15:21 ` Jan Engelhardt
2006-01-01 15:24 ` Jan Engelhardt
2006-01-01 14:31 ` Alistair John Strachan
2006-01-01 18:57 ` Lee Revell
2006-01-01 21:33 ` Keith Owens
2006-01-01 22:57 ` Alistair John Strachan
-- strict thread matches above, loose matches on Subject: below --
2005-12-31 18:18 Bradley Reed
2005-12-31 19:09 ` Mark Knecht
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=20060101131615.GT3811@stusta.de \
--to=bunk@stusta.de \
--cc=bradreed1@gmail.com \
--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