summaryrefslogtreecommitdiffstats
path: root/arch
diff options
context:
space:
mode:
authorPaul Mackerras <paulus@samba.org>2014-06-12 16:53:08 +1000
committerBenjamin Herrenschmidt <benh@kernel.crashing.org>2014-08-05 16:34:28 +1000
commit9be9be2e9a966fe32c1a443c5197f829ecc3028c (patch)
tree874f5a970cb66d959dcb9f09b67696af845722e8 /arch
parent16a05bff128de196fc17edd2beaa40d0f07ae04a (diff)
downloadlinux-9be9be2e9a966fe32c1a443c5197f829ecc3028c.tar.gz
linux-9be9be2e9a966fe32c1a443c5197f829ecc3028c.tar.bz2
linux-9be9be2e9a966fe32c1a443c5197f829ecc3028c.zip
powerpc: Reduce scariness of interrupt frames in stack traces
Some people see things like "Exception: 501" in stack traces in dmesg and assume that means that something has gone badly wrong, when in fact "Exception: 501" just means a device interrupt was taken. This changes "Exception" to "interrupt" to make it clearer that we are just recording the fact of a change in control flow rather than some error condition. Signed-off-by: Paul Mackerras <paulus@samba.org> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Diffstat (limited to 'arch')
-rw-r--r--arch/powerpc/kernel/process.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/powerpc/kernel/process.c b/arch/powerpc/kernel/process.c
index 9c34327e38ca..bf44ae962ab8 100644
--- a/arch/powerpc/kernel/process.c
+++ b/arch/powerpc/kernel/process.c
@@ -1581,7 +1581,7 @@ void show_stack(struct task_struct *tsk, unsigned long *stack)
struct pt_regs *regs = (struct pt_regs *)
(sp + STACK_FRAME_OVERHEAD);
lr = regs->link;
- printk("--- Exception: %lx at %pS\n LR = %pS\n",
+ printk("--- interrupt: %lx at %pS\n LR = %pS\n",
regs->trap, (void *)regs->nip, (void *)lr);
firstframe = 1;
}