From: Bradley Reed <bradreed1@gmail.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: MPlayer broken under 2.6.15-rc7-rt1?
Date: Sun, 1 Jan 2006 11:51:21 +0200 [thread overview]
Message-ID: <20060101115121.034e6bb7@galactus.example.org> (raw)
In-Reply-To: <1136106861.17830.6.camel@laptopd505.fenrus.org>
On Sun, 01 Jan 2006 10:14:21 +0100
Arjan van de Ven <arjan@infradead.org> wrote:
> On Sat, 2005-12-31 at 20:29 +0200, Bradley Reed wrote:
> > I have tried MPlayer versions 1.0pre6, 1.0pre7, and cvs from today
> > and they all work fine under 2.6.14 and 2.6.14-rt21/22.
> >
> > I booted into 2.6.15-rc7-rt1 and the same MPlayer binaries segfault
> > on every video I try and play. Yes, I have nvidia modules loaded,
> > so won't get much help, but thought someone might like to know.
>
>
> you know, you could have done a little bit more effort and reproduced
> this without the binary crud... it's not that hard you know and it
> shows that you actually care about the problem enough that you want
> to make it worthwhile for people to look into it.
>
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.
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.
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?
Brad
next prev parent reply other threads:[~2006-01-01 9:51 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 [this message]
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
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=20060101115121.034e6bb7@galactus.example.org \
--to=bradreed1@gmail.com \
--cc=arjan@infradead.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.