On Fri, 2012-10-26 at 14:09 +0200, Thomas Gleixner wrote:
> On Fri, 26 Oct 2012, Zhang, Yanmin wrote:
> > >From: Thomas Gleixner [mailto:t...@linutronix.de]
> > >Your code is returning HRTIMER_RESTART from the timer callback and at
> > >the same time it starts the timer from some other context.
On Fri, 2012-10-26 at 14:09 +0200, Thomas Gleixner wrote:
On Fri, 26 Oct 2012, Zhang, Yanmin wrote:
From: Thomas Gleixner [mailto:t...@linutronix.de]
Your code is returning HRTIMER_RESTART from the timer callback and at
the same time it starts the timer from some other context. That's what
On Fri, 26 Oct 2012, Zhang, Yanmin wrote:
> >From: Thomas Gleixner [mailto:t...@linutronix.de]
> >Your code is returning HRTIMER_RESTART from the timer callback and at
> >the same time it starts the timer from some other context. That's what
> >needs to be fixed.
>
> The timer user should fix it.
>-Original Message-
>From: Thomas Gleixner [mailto:t...@linutronix.de]
>Sent: Friday, October 26, 2012 5:55 PM
>To: He, Bo
>Cc: linux-kernel@vger.kernel.org; Peter Zijlstra; Ingo Molnar;
>yanmin_zh...@linux.intel.com; Zhang, Yanmin
>Subject: Re: [PATCH] hrtime
On Fri, 26 Oct 2012, he, bo wrote:
> From: Yanmin Zhang
>
> We hit a kernel panic at __run_hrtimer=>BUG_ON(timer->state !=
> HRTIMER_STATE_CALLBACK).
> <2>[ 10.226053, 3] kernel BUG at
> /home/android/xiaobing/ymz/r4/hardware/intel/linux-2.6/kernel/hrtimer.c:1228!
>
> Basically,
On Fri, 2012-10-26 at 10:51 +0800, he, bo wrote:
> From: Yanmin Zhang
>
> We hit a kernel panic at __run_hrtimer=>BUG_ON(timer->state !=
> HRTIMER_STATE_CALLBACK).
> <2>[ 10.226053, 3] kernel BUG at
> /home/android/xiaobing/ymz/r4/hardware/intel/linux-2.6/kernel/hrtimer.c:1228!
> <0>[
On Fri, 2012-10-26 at 10:51 +0800, he, bo wrote:
From: Yanmin Zhang yanmin.zh...@intel.com
We hit a kernel panic at __run_hrtimer=BUG_ON(timer-state !=
HRTIMER_STATE_CALLBACK).
2[ 10.226053, 3] kernel BUG at
/home/android/xiaobing/ymz/r4/hardware/intel/linux-2.6/kernel/hrtimer.c:1228!
On Fri, 26 Oct 2012, he, bo wrote:
From: Yanmin Zhang yanmin.zh...@intel.com
We hit a kernel panic at __run_hrtimer=BUG_ON(timer-state !=
HRTIMER_STATE_CALLBACK).
2[ 10.226053, 3] kernel BUG at
/home/android/xiaobing/ymz/r4/hardware/intel/linux-2.6/kernel/hrtimer.c:1228!
Basically,
-Original Message-
From: Thomas Gleixner [mailto:t...@linutronix.de]
Sent: Friday, October 26, 2012 5:55 PM
To: He, Bo
Cc: linux-kernel@vger.kernel.org; Peter Zijlstra; Ingo Molnar;
yanmin_zh...@linux.intel.com; Zhang, Yanmin
Subject: Re: [PATCH] hrtimer:__run_hrtimer races
On Fri, 26 Oct 2012, Zhang, Yanmin wrote:
From: Thomas Gleixner [mailto:t...@linutronix.de]
Your code is returning HRTIMER_RESTART from the timer callback and at
the same time it starts the timer from some other context. That's what
needs to be fixed.
The timer user should fix it. But could
From: Yanmin Zhang
We hit a kernel panic at __run_hrtimer=>BUG_ON(timer->state !=
HRTIMER_STATE_CALLBACK).
<2>[ 10.226053, 3] kernel BUG at
/home/android/xiaobing/ymz/r4/hardware/intel/linux-2.6/kernel/hrtimer.c:1228!
<0>[ 10.235682, 3] invalid opcode: [#1] PREEMPT SMP
<4>[
From: Yanmin Zhang yanmin.zh...@intel.com
We hit a kernel panic at __run_hrtimer=BUG_ON(timer-state !=
HRTIMER_STATE_CALLBACK).
2[ 10.226053, 3] kernel BUG at
/home/android/xiaobing/ymz/r4/hardware/intel/linux-2.6/kernel/hrtimer.c:1228!
0[ 10.235682, 3] invalid opcode: [#1] PREEMPT SMP
12 matches
Mail list logo