lib: spinlock_debug: Prevent continuous spin dump logs on panic
Once a spinlock lockup is detected on a CPU, we invoke a Kernel Panic. During the panic handling, we might see more instances of spinlock lockup from other CPUs. This causes the dmesg to be cluttered and makes it cumbersome to detect what exactly happened. Call spin_bug instead of calling spin_dump directly. Change-Id: I57857a991345a8dac3cd952463d05129145867a8 Signed-off-by: Rohit Vaswani <rvaswani@codeaurora.org> Signed-off-by: Prasad Sodagudi <psodagud@codeaurora.org>
This commit is contained in:
parent
e2cddd1040
commit
a543061653
1 changed files with 1 additions and 1 deletions
|
@ -116,7 +116,7 @@ static void __spin_lock_debug(raw_spinlock_t *lock)
|
|||
__delay(1);
|
||||
}
|
||||
/* lockup suspected: */
|
||||
spin_dump(lock, "lockup suspected");
|
||||
spin_bug(lock, "lockup suspected");
|
||||
#ifdef CONFIG_SMP
|
||||
trigger_all_cpu_backtrace();
|
||||
#endif
|
||||
|
|
Loading…
Add table
Reference in a new issue