On Thu, May 21, 2015 at 09:38:23AM +0800, long.wanglong wrote:
> On 2015/5/20 21:22, Petr Mladek wrote:
> > On Tue 2015-05-19 14:57:46, Petr Mladek wrote:
> >> On Tue 2015-05-19 09:08:45, Wang Long wrote:
> >>> This is my backport patch series to Fix the problem(backport to 3.10):
> >>> "
> >>> Whe
On 2015/5/20 21:22, Petr Mladek wrote:
> On Tue 2015-05-19 14:57:46, Petr Mladek wrote:
>> On Tue 2015-05-19 09:08:45, Wang Long wrote:
>>> This is my backport patch series to Fix the problem(backport to 3.10):
>>> "
>>> When trigger_all_cpu_backtrace() is called on x86, it will trigger an
>>> NMI
On Tue 2015-05-19 14:57:46, Petr Mladek wrote:
> On Tue 2015-05-19 09:08:45, Wang Long wrote:
> > This is my backport patch series to Fix the problem(backport to 3.10):
> > "
> > When trigger_all_cpu_backtrace() is called on x86, it will trigger an
> > NMI on each CPU and call show_regs(). But this
On Tue 2015-05-19 09:08:45, Wang Long wrote:
> This is my backport patch series to Fix the problem(backport to 3.10):
> "
> When trigger_all_cpu_backtrace() is called on x86, it will trigger an
> NMI on each CPU and call show_regs(). But this can lead to a hard lock
> up if the NMI comes in on anot
This is my backport patch series to Fix the problem(backport to 3.10):
"
When trigger_all_cpu_backtrace() is called on x86, it will trigger an
NMI on each CPU and call show_regs(). But this can lead to a hard lock
up if the NMI comes in on another printk().
"
The solution is described in commit "a9
5 matches
Mail list logo
