From: "Rafael D'Halleweyn (List)" <list@noduck.net>
To: linux-kernel@vger.kernel.org
Subject: kernel BUG at kernel/timer.c:370!
Date: Fri, 13 Feb 2004 22:33:11 -0500 [thread overview]
Message-ID: <1076729590.30432.4.camel@bigboy> (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
--
Rafael D'Halleweyn (List) <list@noduck.net>
next reply other threads:[~2004-02-14 3:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-14 3:33 Rafael D'Halleweyn (List) [this message]
2004-02-14 8:21 ` kernel BUG at kernel/timer.c:370! Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2004-03-05 17:40 Flavio Bruno Leitner
2004-03-05 23:06 ` Andrew Morton
2004-03-11 15:43 ` Flavio Bruno Leitner
2004-03-11 21:42 ` Andrew Morton
2004-03-12 19:11 ` Flavio Bruno Leitner
2004-03-31 16:59 Craig, Dave
2004-03-31 17:16 Craig, Dave
2004-03-31 19:52 ` Andrew Morton
2004-04-01 14:24 ` Flavio Bruno Leitner
2004-04-01 17:24 ` Flavio Bruno Leitner
2004-04-01 18:37 ` Andrew Morton
2004-04-02 14:42 ` Flavio Bruno Leitner
2004-03-31 21:39 Craig, Dave
2004-03-31 22:15 ` Andrew Morton
2004-04-01 19:05 Craig, Dave
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1076729590.30432.4.camel@bigboy \
--to=list@noduck.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.