diff options
| author | Jiri Kosina <jkosina@suse.cz> | 2015-11-06 03:44:41 +0100 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2015-11-06 04:34:48 +0100 |
| commit | 55537871ef666b4153fd1ef8782e4a13fee142cc (patch) | |
| tree | 9e71e9e7db5b2f4f04e9d9c48d801717bb11eed7 /Documentation/filesystems/ext2.txt | |
| parent | watchdog: do not unpark threads in watchdog_park_threads() on error (diff) | |
| download | linux-55537871ef666b4153fd1ef8782e4a13fee142cc.tar.xz linux-55537871ef666b4153fd1ef8782e4a13fee142cc.zip | |
kernel/watchdog.c: perform all-CPU backtrace in case of hard lockup
In many cases of hardlockup reports, it's actually not possible to know
why it triggered, because the CPU that got stuck is usually waiting on a
resource (with IRQs disabled) in posession of some other CPU is holding.
IOW, we are often looking at the stacktrace of the victim and not the
actual offender.
Introduce sysctl / cmdline parameter that makes it possible to have
hardlockup detector perform all-CPU backtrace.
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Reviewed-by: Aaron Tomlin <atomlin@redhat.com>
Cc: Ulrich Obergfell <uobergfe@redhat.com>
Acked-by: Don Zickus <dzickus@redhat.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Documentation/filesystems/ext2.txt')
0 files changed, 0 insertions, 0 deletions