From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Subject: Re: [ANNOUNCE] 3.0-rt6
Date: Thu, 04 Aug 2011 12:05:12 -0700 [thread overview]
Message-ID: <4E3AED68.5060506@ccrma.stanford.edu> (raw)
In-Reply-To: <1312450965.16729.7.camel@twins>
Was going to try this but it appears it is in rt7, trying to build rt7
fails with:
ERROR: "of_find_property" [drivers/tty/serial/of_serial.ko] undefined!
ERROR: "of_find_property" [drivers/hwmon/ltc4245.ko] undefined!
-- Fernando
On 08/04/2011 02:42 AM, Peter Zijlstra wrote:
> On Wed, 2011-08-03 at 23:34 -0700, Fernando Lopez-Lezcano wrote:
>> [ 117.026009] [<ffffffff814ef322>] _raw_spin_lock+0x45/0x79
>> [ 117.026009] [<ffffffff8107b6f1>] ? __run_posix_cpu_timers+0x8f/0x353
>> [ 117.026009] [<ffffffff8107b6f1>] __run_posix_cpu_timers+0x8f/0x353
>
> I think its this one, could you confirm?
>
> ---
> Index: linux-2.6/kernel/posix-cpu-timers.c
> ===================================================================
> --- linux-2.6.orig/kernel/posix-cpu-timers.c
> +++ linux-2.6/kernel/posix-cpu-timers.c
> @@ -1288,10 +1288,11 @@ static inline int fastpath_timer_check(s
> sig = tsk->signal;
> if (sig->cputimer.running) {
> struct task_cputime group_sample;
> + unsigned long flags;
>
> - raw_spin_lock(&sig->cputimer.lock);
> + raw_spin_lock_irqsave(&sig->cputimer.lock, flags);
> group_sample = sig->cputimer.cputime;
> - raw_spin_unlock(&sig->cputimer.lock);
> + raw_spin_unlock_irqrestore(&sig->cputimer.lock, flags);
>
> if (task_cputime_expired(&group_sample,&sig->cputime_expires))
> return 1;
>
next prev parent reply other threads:[~2011-08-04 19:05 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 21:43 [ANNOUNCE] 3.0-rt6 Thomas Gleixner
2011-07-28 22:33 ` Madovsky
2011-07-28 23:33 ` Peter W. Morreale
2011-07-29 0:56 ` Thomas Gleixner
2011-07-29 6:05 ` Mike Galbraith
2011-07-29 14:03 ` Paul E. McKenney
2011-07-29 15:57 ` [ANNOUNCE] 3.0-rt6 (kgdb working) Darren Hart
2011-07-30 15:49 ` [ANNOUNCE] 3.0-rt6 Remy Bohmer
2011-07-30 15:49 ` Remy Bohmer
2011-07-30 20:21 ` Remy Bohmer
2011-08-07 10:44 ` Remy Bohmer
2011-08-01 8:42 ` Rolando Martins
2011-08-01 10:34 ` Mike Galbraith
2011-08-01 10:45 ` Rolando Martins
2011-08-01 10:45 ` Rolando Martins
2011-08-01 11:06 ` Peter Zijlstra
2011-08-01 11:10 ` Rolando Martins
2011-08-04 6:34 ` Fernando Lopez-Lezcano
2011-08-04 9:42 ` Peter Zijlstra
2011-08-04 19:05 ` Fernando Lopez-Lezcano [this message]
2011-08-04 20:15 ` Uwe Kleine-König
2011-08-05 9:28 ` Uwe Kleine-König
2011-08-05 16:03 ` Fernando Lopez-Lezcano
2011-08-08 17:25 ` Fernando Lopez-Lezcano
2011-08-04 16:34 ` [ANNOUNCE] 3.0-rt6 : BUG at kernel/trmutex.c:724! Tim Sander
2011-08-04 16:34 ` Tim Sander
2011-08-04 16:37 ` Peter Zijlstra
2011-08-04 17:04 ` Tim Sander
2011-08-04 17:04 ` Tim Sander
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=4E3AED68.5060506@ccrma.stanford.edu \
--to=nando@ccrma.stanford.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.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 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.