Skip to contentSkip to conversation

kernel BUG at kernel/timer.c:370!

DISCUSSION Rafael D'Halleweyn (List) 2 participants 2 messages Feb 14, 2004

lore
Share & tools
lore
#0 lore raw

I sometimes get the following BUG (transcribed from a digital camera snapshot, so it might contain errors). I did not copy the stack trace, let me know if you want it.

kernel BUG at kernel/timer.c:370!

invalid operand: 0000 [#1]
CPU:    0
EIP:    0060:[<c01284f8>]    Not tainted
EFLAGS: 00010003

EIP is at cascade+0x50/0x70
eax: d0a77724 ebx: d0a77724 ecx: c04aaa28 edx: 0000001c
esi: c04aab08 edi: c04aa220 ebp: 0000001c esp: c0457e9e
ds: 007b es: 007b ss: 0068
Process swapper (pid: 0, threadinfo=c0456000 task=c03d2de0)

Stack: ...
Call Trace:
 [<c01289e4>] update_process_times+0x44/0x50
 [<c0128b3f>] run_timer_softirq+0x12f/0x1c0
 [<c0124695>] do_softirq+0x95/0xa0
 [<c010d2fb>] do_IRQ+0xfb/0x130
 [<c010b5e8>] common_interrupt+0x18/0x20

Code: 0f 0b 72 01 92 d1 38 c0 eb d5 8d b4 26 00 00 00 00 8d bc 27
 <0>Kernel panic: Fatal exception in interrupt

In interrupt handler - not syncing

Signature · 1 line
Rafael D'Halleweyn (List) <[email protected]>
#1 lore raw
Quoted 11 lines · Rafael D'Halleweyn (List)

I sometimes get the following BUG (transcribed from a digital camera
snapshot, so it might contain errors). I did not copy the stack trace, let me know if you want it.

kernel BUG at kernel/timer.c:370!
invalid operand: 0000 [#1]
CPU: 0
EIP: 0060:[<c01284f8>] Not tainted
EFLAGS: 00010003
EIP is at cascade+0x50/0x70

Quoted 11 lines
 eax: d0a77724   ebx: d0a77724   ecx: c04aaa28   edx: 0000001c
 esi: c04aab08   edi: c04aa220   ebp: 0000001c   esp: c0457e9e
 ds: 007b   es: 007b   ss: 0068
 Process swapper (pid: 0, threadinfo=c0456000 task=c03d2de0)
 Stack: ...
 Call Trace:
  [<c01289e4>] update_process_times+0x44/0x50
  [<c0128b3f>] run_timer_softirq+0x12f/0x1c0
  [<c0124695>] do_softirq+0x95/0xa0
  [<c010d2fb>] do_IRQ+0xfb/0x130
  [<c010b5e8>] common_interrupt+0x18/0x20

This could be a hardware problem. Or it could be a bug basically anywhere in the kernel.

Are you using CONFIG_DEBUG_SLAB?

Could you please apply the below patch, wait for the problem to reoccur, then let us know?

kernel/timer.c renamed from kernel/timer.c~a +10 -1
diff -puN kernel/timer.c~a kernel/timer.c
@@ -31,6 +31,7 @@
 #include <linux/time.h>
 #include <linux/jiffies.h>
 #include <linux/cpu.h>
+#include <linux/kallsyms.h>
 
 #include <asm/uaccess.h>
 #include <asm/div64.h>
@@ -367,7 +368,15 @@ static int cascade(tvec_base_t *base, tv
 		struct timer_list *tmp;
 
 		tmp = list_entry(curr, struct timer_list, entry);
-		BUG_ON(tmp->base != base);
+		if (tmp->base != base) {
+			printk("%s: %p != %p\n",
+				__FUNCTION__, tmp->base, base);
+			printk("handler=%p", tmp->function);
+			print_symbol(" (%s)", (unsigned long)tmp->function);
+			printk("\n");
+			dump_stack();
+			tmp->base = base;
+		}
 		curr = curr->next;
 		internal_add_timer(base, tmp);
 	}

_