linux.vnet.ibm.com; Peter Zijlstra
> (pet...@infradead.org); x...@kernel.org; 'linux-kernel@vger.kernel.org'
> (linux-kernel@vger.kernel.org); Wang, Xiaoming; Li, Zhuangzhi
> Subject: Re: Panic and page fault in loop during handling NMI backtrace
> handler
>
> On Wed, 16 Oct 2013 01:54
On Wed, 16 Oct 2013 01:54:51 +
"Liu, Chuansheng" wrote:
> > Since the NMI iretq nesting has been fixed, there's no reason that
> I think you patch fix the infinite loop, we will have a test soon.
> BTW, we are using 3.10, could you help to point out which NMI iretq nesting
> patch?
There
linux.vnet.ibm.com; Peter Zijlstra
> (pet...@infradead.org); x...@kernel.org; 'linux-kernel@vger.kernel.org'
> (linux-kernel@vger.kernel.org); Wang, Xiaoming; Li, Zhuangzhi
> Subject: Re: Panic and page fault in loop during handling NMI backtrace
> handler
>
>
> BTW, please d
BTW, please do not send out HTML email, as that gets blocked from going
to LKML.
On Tue, 15 Oct 2013 02:01:04 +
"Liu, Chuansheng" wrote:
> We meet one issue that during trigger all CPU backtrace, but during in the
> NMI handler arch_trigger_all_cpu_backtrace_handler,
> It hit the PAGE
On Tue, 15 Oct 2013 14:54:11 +0200
Frederic Weisbecker wrote:
> On Tue, Oct 15, 2013 at 02:37:17PM +0200, Peter Zijlstra wrote:
> > On Tue, Oct 15, 2013 at 02:18:53PM +0200, Frederic Weisbecker wrote:
> > > On Tue, Oct 15, 2013 at 02:01:04AM +, Liu, Chuansheng wrote:
> > > > We meet one
On Tue, Oct 15, 2013 at 03:17:59PM +0200, Frederic Weisbecker wrote:
> On Tue, Oct 15, 2013 at 06:06:59AM -0700, Paul E. McKenney wrote:
> > On Tue, Oct 15, 2013 at 02:59:15PM +0200, Frederic Weisbecker wrote:
> > > On Tue, Oct 15, 2013 at 05:48:37AM -0700, Paul E. McKenney wrote:
> > > > On Tue,
On Tue, Oct 15, 2013 at 06:06:59AM -0700, Paul E. McKenney wrote:
> On Tue, Oct 15, 2013 at 02:59:15PM +0200, Frederic Weisbecker wrote:
> > On Tue, Oct 15, 2013 at 05:48:37AM -0700, Paul E. McKenney wrote:
> > > On Tue, Oct 15, 2013 at 02:37:17PM +0200, Peter Zijlstra wrote:
> > > > On Tue, Oct
On Tue, Oct 15, 2013 at 02:59:15PM +0200, Frederic Weisbecker wrote:
> On Tue, Oct 15, 2013 at 05:48:37AM -0700, Paul E. McKenney wrote:
> > On Tue, Oct 15, 2013 at 02:37:17PM +0200, Peter Zijlstra wrote:
> > > On Tue, Oct 15, 2013 at 02:18:53PM +0200, Frederic Weisbecker wrote:
> > > > On Tue,
On Tue, Oct 15, 2013 at 05:48:37AM -0700, Paul E. McKenney wrote:
> On Tue, Oct 15, 2013 at 02:37:17PM +0200, Peter Zijlstra wrote:
> > On Tue, Oct 15, 2013 at 02:18:53PM +0200, Frederic Weisbecker wrote:
> > > On Tue, Oct 15, 2013 at 02:01:04AM +, Liu, Chuansheng wrote:
> > > > We meet one
On Tue, Oct 15, 2013 at 02:37:17PM +0200, Peter Zijlstra wrote:
> On Tue, Oct 15, 2013 at 02:18:53PM +0200, Frederic Weisbecker wrote:
> > On Tue, Oct 15, 2013 at 02:01:04AM +, Liu, Chuansheng wrote:
> > > We meet one issue that during trigger all CPU backtrace, but during in
> > > the NMI
On Tue, Oct 15, 2013 at 02:37:17PM +0200, Peter Zijlstra wrote:
> On Tue, Oct 15, 2013 at 02:18:53PM +0200, Frederic Weisbecker wrote:
> > On Tue, Oct 15, 2013 at 02:01:04AM +, Liu, Chuansheng wrote:
> > > We meet one issue that during trigger all CPU backtrace, but during in
> > > the NMI
On Tue, Oct 15, 2013 at 02:18:53PM +0200, Frederic Weisbecker wrote:
> On Tue, Oct 15, 2013 at 02:01:04AM +, Liu, Chuansheng wrote:
> > We meet one issue that during trigger all CPU backtrace, but during in the
> > NMI handler arch_trigger_all_cpu_backtrace_handler,
> > It hit the PAGE fault,
On Tue, Oct 15, 2013 at 02:01:04AM +, Liu, Chuansheng wrote:
> We meet one issue that during trigger all CPU backtrace, but during in the
> NMI handler arch_trigger_all_cpu_backtrace_handler,
> It hit the PAGE fault, then PAGE fault is in loop, at last the thread stack
> overflow, and system
Zijlstra
(pet...@infradead.org); x...@kernel.org; 'linux-kernel@vger.kernel.org'
(linux-kernel@vger.kernel.org); Wang, Xiaoming; Li, Zhuangzhi
Subject: Re: Panic and page fault in loop during handling NMI backtrace
handler
BTW, please do not send out HTML email, as that gets blocked from going
On Wed, 16 Oct 2013 01:54:51 +
Liu, Chuansheng chuansheng@intel.com wrote:
Since the NMI iretq nesting has been fixed, there's no reason that
I think you patch fix the infinite loop, we will have a test soon.
BTW, we are using 3.10, could you help to point out which NMI iretq nesting
Zijlstra
(pet...@infradead.org); x...@kernel.org; 'linux-kernel@vger.kernel.org'
(linux-kernel@vger.kernel.org); Wang, Xiaoming; Li, Zhuangzhi
Subject: Re: Panic and page fault in loop during handling NMI backtrace
handler
On Wed, 16 Oct 2013 01:54:51 +
Liu, Chuansheng chuansheng
On Tue, Oct 15, 2013 at 02:01:04AM +, Liu, Chuansheng wrote:
We meet one issue that during trigger all CPU backtrace, but during in the
NMI handler arch_trigger_all_cpu_backtrace_handler,
It hit the PAGE fault, then PAGE fault is in loop, at last the thread stack
overflow, and system
On Tue, Oct 15, 2013 at 02:18:53PM +0200, Frederic Weisbecker wrote:
On Tue, Oct 15, 2013 at 02:01:04AM +, Liu, Chuansheng wrote:
We meet one issue that during trigger all CPU backtrace, but during in the
NMI handler arch_trigger_all_cpu_backtrace_handler,
It hit the PAGE fault, then
On Tue, Oct 15, 2013 at 02:37:17PM +0200, Peter Zijlstra wrote:
On Tue, Oct 15, 2013 at 02:18:53PM +0200, Frederic Weisbecker wrote:
On Tue, Oct 15, 2013 at 02:01:04AM +, Liu, Chuansheng wrote:
We meet one issue that during trigger all CPU backtrace, but during in
the NMI handler
On Tue, Oct 15, 2013 at 02:37:17PM +0200, Peter Zijlstra wrote:
On Tue, Oct 15, 2013 at 02:18:53PM +0200, Frederic Weisbecker wrote:
On Tue, Oct 15, 2013 at 02:01:04AM +, Liu, Chuansheng wrote:
We meet one issue that during trigger all CPU backtrace, but during in
the NMI handler
On Tue, Oct 15, 2013 at 05:48:37AM -0700, Paul E. McKenney wrote:
On Tue, Oct 15, 2013 at 02:37:17PM +0200, Peter Zijlstra wrote:
On Tue, Oct 15, 2013 at 02:18:53PM +0200, Frederic Weisbecker wrote:
On Tue, Oct 15, 2013 at 02:01:04AM +, Liu, Chuansheng wrote:
We meet one issue that
On Tue, Oct 15, 2013 at 02:59:15PM +0200, Frederic Weisbecker wrote:
On Tue, Oct 15, 2013 at 05:48:37AM -0700, Paul E. McKenney wrote:
On Tue, Oct 15, 2013 at 02:37:17PM +0200, Peter Zijlstra wrote:
On Tue, Oct 15, 2013 at 02:18:53PM +0200, Frederic Weisbecker wrote:
On Tue, Oct 15, 2013
On Tue, Oct 15, 2013 at 06:06:59AM -0700, Paul E. McKenney wrote:
On Tue, Oct 15, 2013 at 02:59:15PM +0200, Frederic Weisbecker wrote:
On Tue, Oct 15, 2013 at 05:48:37AM -0700, Paul E. McKenney wrote:
On Tue, Oct 15, 2013 at 02:37:17PM +0200, Peter Zijlstra wrote:
On Tue, Oct 15, 2013 at
On Tue, Oct 15, 2013 at 03:17:59PM +0200, Frederic Weisbecker wrote:
On Tue, Oct 15, 2013 at 06:06:59AM -0700, Paul E. McKenney wrote:
On Tue, Oct 15, 2013 at 02:59:15PM +0200, Frederic Weisbecker wrote:
On Tue, Oct 15, 2013 at 05:48:37AM -0700, Paul E. McKenney wrote:
On Tue, Oct 15,
On Tue, 15 Oct 2013 14:54:11 +0200
Frederic Weisbecker fweis...@gmail.com wrote:
On Tue, Oct 15, 2013 at 02:37:17PM +0200, Peter Zijlstra wrote:
On Tue, Oct 15, 2013 at 02:18:53PM +0200, Frederic Weisbecker wrote:
On Tue, Oct 15, 2013 at 02:01:04AM +, Liu, Chuansheng wrote:
We meet
BTW, please do not send out HTML email, as that gets blocked from going
to LKML.
On Tue, 15 Oct 2013 02:01:04 +
Liu, Chuansheng chuansheng@intel.com wrote:
We meet one issue that during trigger all CPU backtrace, but during in the
NMI handler arch_trigger_all_cpu_backtrace_handler,
26 matches
Mail list logo