From: Steven Rostedt <rostedt@goodmis.org>
To: Bradley Reed <bradreed1@gmail.com>
Cc: linux-kernel@vger.kernel.org, Arjan van de Ven <arjan@infradead.org>
Subject: Re: MPlayer broken under 2.6.15-rc7-rt1?
Date: Sun, 01 Jan 2006 08:41:16 -0500 [thread overview]
Message-ID: <1136122876.6039.153.camel@localhost.localdomain> (raw)
In-Reply-To: <20060101115121.034e6bb7@galactus.example.org>
On Sun, 2006-01-01 at 11:51 +0200, Bradley Reed wrote:
> And you could have saved the time and effort of replying, as you had
> nothing useful to say. Why do you expect kernel users (non-developers)
> to jump through hoops and cripple their systems in order to provide bug
> reports? Exactly how could I have tested MPLayer realistically without
> Xv support? It isn't that easy to swap video cards in a laptop.
Hi Bradley,
I never even noticed that it was a tainted kernel. But you did have a
same problem as someone without it. I too have two machines with NVidia
cards that are not very useful without the binary drivers. Thus the next
two machines I bought (a server, and a laptop) I made damn well that it
didn't have a NVidia card in them (I used to be a devoted NVidia
consumer, now I'm a frustrated one).
The reason that I will no long run test kernels with NVidia is that that
module has caused more bugs than I could stand. __Especially__ with the
-rt patch. I'm very surprised that you actually have the nvidia module
working with that patch, since it does things that the nvidia module
doesn't even know about. I gave up trying to modify the nvidia stuff to
work with the -rt patch almost a year ago. Too much black magic going
on in the binary part.
>
> I noticed that after trying a new kernel a user space tool, which
> worked fine under earlier kernels, was no longer working. Linus himself
> said that this is worth pointing out. I did so.
I agree that it is good to point it out, even if it was just a
coincidence that you had the same problem with someone that didn't have
a tainted kernel. It did help me to know exactly where the bug was.
But don't be surprised if someone tells you to try it without the
tainting module before they look any further. If you say you can't,
then they very well might just ignore your post.
>
> Yes, I was very fortunate in that someone else with a non-tainted
> kernel noticed a similar bug with /dev/rtc, and even more fortunate
> that Steven Rostedt provided a patch that worked for both of us. As I
> had said in my original post I was not expecting that, but thought the
> bug was worth reporting.
>
> DO YOU REALLY PREFER USERS NOT REPORT BUGS?
I say 'no', I don't want users to _not_ report bugs. Even if it
increases the noise out there. It's up to the developer to decide if
they want to look further, or just tell the user "sorry, I can't waste
my time if there's a chance that the problem is in code I can't see".
Cheers,
-- Steve
next prev parent reply other threads:[~2006-01-01 13:41 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
2006-01-01 13:25 ` Arjan van de Ven
2006-01-01 13:41 ` Steven Rostedt [this message]
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=1136122876.6039.153.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=arjan@infradead.org \
--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