From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Keith Owens <kaos@ocs.com.au>
Cc: Lee Revell <rlrevell@joe-job.com>,
Arjan van de Ven <arjan@infradead.org>,
Bradley Reed <bradreed1@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: MPlayer broken under 2.6.15-rc7-rt1?
Date: Sun, 1 Jan 2006 22:57:24 +0000 [thread overview]
Message-ID: <200601012257.24795.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <29832.1136151227@ocs3.ocs.com.au>
On Sunday 01 January 2006 21:33, Keith Owens wrote:
> Lee Revell (on Sun, 01 Jan 2006 13:57:14 -0500) wrote:
> >On Sun, 2006-01-01 at 14:31 +0000, Alistair John Strachan wrote:
> >> On Sunday 01 January 2006 09:14, Arjan van de Ven 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.
> >>
> >> REPORTING-BUGS should probably be fixed to make the points you
> >> repeatedly have to make. I agree 100% that people should not be
> >> reporting easily reproducible bugs with proprietary drivers loaded;
> >> what's a reboot to them?
> >>
> >> Let's add something to REPORTING-BUGS about tainted kernels and/or
> >> proprietary drivers. A quick grep of this file from 2.6.15-rc6 gives me
> >> no hits for "proprietary", "tainted" or "binary".
> >
> >Heh, wow, that's a serious omission. It would explain why so many users
> >post tainted bug reports then act like we're fanatics for telling them
> >not to do that ;-)
>
> Historically this was covered in the kernel FAQ, see
> http://www.kernel.org/pub/linux/docs/lkml/#s1-18.
I can see no reason why it shouldn't also be in the kernel. The issue is not
even a political one, it is a matter of debugging practicality.
--
Cheers,
Alistair.
'No sense being pessimistic, it probably wouldn't work anyway.'
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
next prev parent reply other threads:[~2006-01-01 22:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-31 18:29 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
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 [this message]
-- 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=200601012257.24795.s0348365@sms.ed.ac.uk \
--to=s0348365@sms.ed.ac.uk \
--cc=arjan@infradead.org \
--cc=bradreed1@gmail.com \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
/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
all inboxes | Powered by JetHome®