Re: 4.4-rc5 Setting trap flag inside nmi handler results in HARD LOCKUP

On 12/16/15, Jeff Merkey wrote: > Setting the (trap flag | resume flag) inside of an nmi handler results > in a hard lockup while setting the resume flag works fine. > > The watchdog detector fails to detect the lockup. I am currently > examining the trap gate and interrupt gate setup on Linux

Re: 4.4-rc5 Setting trap flag inside nmi handler results in HARD LOCKUP

On 12/16/15, Jeff Merkey wrote: > On 12/16/15, Jeff Merkey wrote: >> Setting the (trap flag | resume flag) inside of an nmi handler results >> in a hard lockup while setting the resume flag works fine. >> >> The watchdog detector fails to detect the lockup. I am currently >> examining the trap

Re: 4.4-rc5 Setting trap flag inside nmi handler results in HARD LOCKUP

He is stepping into native_safe_halt() when this bug occurs (processor has halted). I am starting to wonder is this is a linux bug or intel bug. I am starting to lean towards intel bug possibly. I will go and review intels documentation about what happens when a processor has been halted, is

Re: 4.4-rc5 Setting trap flag inside nmi handler results in HARD LOCKUP

On 12/16/15, Jeff Merkey wrote: > Setting the (trap flag | resume flag) inside of an nmi handler results > in a hard lockup while setting the resume flag works fine. > > The watchdog detector fails to detect the lockup. I am currently > examining the trap gate and interrupt gate setup on Linux

4.4-rc5 Setting trap flag inside nmi handler results in HARD LOCKUP

Setting the (trap flag | resume flag) inside of an nmi handler results in a hard lockup while setting the resume flag works fine. The watchdog detector fails to detect the lockup. I am currently examining the trap gate and interrupt gate setup on Linux and if anyone has any ideas it would be

4.4-rc5 Setting trap flag inside nmi handler results in HARD LOCKUP

Setting the (trap flag | resume flag) inside of an nmi handler results in a hard lockup while setting the resume flag works fine. The watchdog detector fails to detect the lockup. I am currently examining the trap gate and interrupt gate setup on Linux and if anyone has any ideas it would be

Re: 4.4-rc5 Setting trap flag inside nmi handler results in HARD LOCKUP

On 12/16/15, Jeff Merkey wrote: > Setting the (trap flag | resume flag) inside of an nmi handler results > in a hard lockup while setting the resume flag works fine. > > The watchdog detector fails to detect the lockup. I am currently > examining the trap gate and interrupt

Re: 4.4-rc5 Setting trap flag inside nmi handler results in HARD LOCKUP

On 12/16/15, Jeff Merkey wrote: > On 12/16/15, Jeff Merkey wrote: >> Setting the (trap flag | resume flag) inside of an nmi handler results >> in a hard lockup while setting the resume flag works fine. >> >> The watchdog detector fails to detect the

Re: 4.4-rc5 Setting trap flag inside nmi handler results in HARD LOCKUP

He is stepping into native_safe_halt() when this bug occurs (processor has halted). I am starting to wonder is this is a linux bug or intel bug. I am starting to lean towards intel bug possibly. I will go and review intels documentation about what happens when a processor has been halted, is

Re: 4.4-rc5 Setting trap flag inside nmi handler results in HARD LOCKUP

On 12/16/15, Jeff Merkey wrote: > Setting the (trap flag | resume flag) inside of an nmi handler results > in a hard lockup while setting the resume flag works fine. > > The watchdog detector fails to detect the lockup. I am currently > examining the trap gate and interrupt