From: Bradley Reed <bradreed1@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
john stultz <johnstul@us.ibm.com>
Subject: Re: RTC broken under 2.6.15-rc7-rt1 (was: Re: MPlayer broken under 2.6.15-rc7-rt1?)
Date: Sun, 1 Jan 2006 01:22:43 +0200 [thread overview]
Message-ID: <20060101012243.4208efb3@galactus.example.org> (raw)
In-Reply-To: <1136069215.6039.142.camel@localhost.localdomain>
On Sat, 31 Dec 2005 17:46:55 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Sat, 2005-12-31 at 21:58 +0100, Jan Engelhardt wrote:
> > >Subject: Re: MPlayer broken under 2.6.15-rc7-rt1?
> >
> > I seriously demand that this be changed into "RTC broekn
> > under..."! :)
>
> Done ;)
>
> [...]
>
> > >
> > >Index: linux-2.6.15-rc7-rt1/drivers/char/rtc.c
> >
> > This patch fixes the rtc BUG for me.
>
And me too. I had inadvertently cut off a bit at the very top of your
patch, when I re-cut and pasted, it applied fine.
Shouldn't patch kernels this close to new years. (Which was an hour and
a half ago here...)
> Yeah, attached is a program that does what mplayer does. I run it
> from the command line like this:
>
> # for i in `seq 10000`; do ./rtc_ioctl ; done
>
> And with the patch it runs perfectly fine. Without it, it segfaults
> several times.
Without it, it segfaults 100% here:
root@galactus:~[1002]# for i in `seq 10`; do ./rtc_ioctl; done
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Brad
next prev parent reply other threads:[~2005-12-31 23:22 UTC|newest]
Thread overview: 30+ 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 [this message]
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
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=20060101012243.4208efb3@galactus.example.org \
--to=bradreed1@gmail.com \
--cc=jengelh@linux01.gwdg.de \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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