printk levels for spinlock debug.
From: Dave Jones (davej_at_redhat.com)
Date: 11/30/05
- Previous message: Tejun Heo: "Re: SIL_QUIRK_MOD15WRITE workaround problem on 2.6.14"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 29 Nov 2005 23:23:30 -0500 To: linux-kernel@vger.kernel.org
Signed-off-by: Dave Jones <davej@redhat.com>
--- vanilla/lib/spinlock_debug.c~ 2005-11-29 23:21:14.000000000 -0500
+++ vanilla/lib/spinlock_debug.c 2005-11-29 23:21:49.000000000 -0500
@@ -19,9 +19,9 @@ static void spin_bug(spinlock_t *lock, c
if (xchg(&print_once, 0)) {
if (lock->owner && lock->owner != SPINLOCK_OWNER_INIT)
owner = lock->owner;
- printk("BUG: spinlock %s on CPU#%d, %s/%d\n",
+ printk(KERN_EMERG "BUG: spinlock %s on CPU#%d, %s/%d\n",
msg, smp_processor_id(), current->comm, current->pid);
- printk(" lock: %p, .magic: %08x, .owner: %s/%d, .owner_cpu: %d\n",
+ printk(KERN_EMERG " lock: %p, .magic: %08x, .owner: %s/%d, .owner_cpu: %d\n",
lock, lock->magic,
owner ? owner->comm : "<none>",
owner ? owner->pid : -1,
@@ -77,7 +77,7 @@ static void __spin_lock_debug(spinlock_t
/* lockup suspected: */
if (print_once) {
print_once = 0;
- printk("BUG: spinlock lockup on CPU#%d, %s/%d, %p\n",
+ printk(KERN_EMERG "BUG: spinlock lockup on CPU#%d, %s/%d, %p\n",
smp_processor_id(), current->comm, current->pid,
lock);
dump_stack();
@@ -119,7 +119,7 @@ static void rwlock_bug(rwlock_t *lock, c
static long print_once = 1;
if (xchg(&print_once, 0)) {
- printk("BUG: rwlock %s on CPU#%d, %s/%d, %p\n", msg,
+ printk(KERN_EMERG "BUG: rwlock %s on CPU#%d, %s/%d, %p\n", msg,
smp_processor_id(), current->comm, current->pid, lock);
dump_stack();
#ifdef CONFIG_SMP
@@ -147,7 +147,7 @@ static void __read_lock_debug(rwlock_t *
/* lockup suspected: */
if (print_once) {
print_once = 0;
- printk("BUG: read-lock lockup on CPU#%d, %s/%d, %p\n",
+ printk(KERN_EMERG "BUG: read-lock lockup on CPU#%d, %s/%d, %p\n",
smp_processor_id(), current->comm, current->pid,
lock);
dump_stack();
@@ -219,7 +219,7 @@ static void __write_lock_debug(rwlock_t
/* lockup suspected: */
if (print_once) {
print_once = 0;
- printk("BUG: write-lock lockup on CPU#%d, %s/%d, %p\n",
+ printk(KERN_EMERG "BUG: write-lock lockup on CPU#%d, %s/%d, %p\n",
smp_processor_id(), current->comm, current->pid,
lock);
dump_stack();
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Tejun Heo: "Re: SIL_QUIRK_MOD15WRITE workaround problem on 2.6.14"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
- Re: XFS breakage in 2.6.18-rc1
... system disk too who had to take the hit. ... send the line "unsubscribe linux-kernel"
in ... More majordomo info at http://vger.kernel.org/majordomo-info.html ... Please
read the FAQ at http://www.tux.org/lkml/ ... (Linux-Kernel) - Re: How to run an a.out file in a kernel module
... called in a kernel module using call_usermodehelper ... Please read the FAQ
at http://www.tux.org/lkml/ ... More majordomo info at http://vger.kernel.org/majordomo-info.html
... (Linux-Kernel) - Re: XFS Bug null pointer dereference in xfs_free_ag_extent
... I also filed bug 6877 at kernel.org ... send the line "unsubscribe linux-kernel"
in ... More majordomo info at http://vger.kernel.org/majordomo-info.html ... Please
read the FAQ at http://www.tux.org/lkml/ ... (Linux-Kernel) - Re: [patch] remove unused acct variables from task_struct
... struct mempolicy *mempolicy; ... More majordomo info at http://vger.kernel.org/majordomo-info.html
... Please read the FAQ at http://www.tux.org/lkml/ ... send the line "unsubscribe
linux-kernel" in ... (Linux-Kernel) - Re: DIPC alpha2 for i386, Alpha, SPARC, and M68k
... there seems to be a delay on cs.uwindsor.ca between the time you upload something and
the time it actually shows up on the page. ... More majordomo info at http://vger.kernel.org/majordomo-info.html
... Please read the FAQ at http://www.tux.org/lkml/ ... To unsubscribe from this
list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
... (Linux-Kernel)