Re: [PATCH v2 4/4] Add WARN() function call to hard-soft lockup

2016-02-01 Thread Jeffrey Merkey
>> >> +WARN(1, "Watchdog detected hard LOCKUP on cpu %d", this_cpu); >> + > > So we repeat the same exact print message and dump the same stack again as > we do a few lines above? That doesn't make any sense. > > Cheers, > Don > Agreed. I'll go back and work on it. Jeff

Re: [PATCH v2 4/4] Add WARN() function call to hard-soft lockup

2016-02-01 Thread Don Zickus
On Mon, Feb 01, 2016 at 01:45:27PM -0700, Jeffrey Merkey wrote: > This patch series adds config options which can be set during compile to > direct the compiler to output a breakpoint instruction anywhere a BUG_XX() > or WARN_XX() macro has been placed in the kernel to trigger the system to > enter

[PATCH v2 4/4] Add WARN() function call to hard-soft lockup

2016-02-01 Thread Jeffrey Merkey
This patch series adds config options which can be set during compile to direct the compiler to output a breakpoint instruction anywhere a BUG_XX() or WARN_XX() macro has been placed in the kernel to trigger the system to enter a debugger if a bug is detected by the system. Use of this compile tim