From: Flavio Bruno Leitner <fbl@conectiva.com.br>
To: "Craig, Dave" <dwcraig@qualcomm.com>
Cc: Andrew Morton <akpm@osdl.org>,
"Rafael D'Halleweyn (List)" <list@noduck.net>,
linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at kernel/timer.c:370!
Date: Thu, 1 Apr 2004 14:24:01 -0300 [thread overview]
Message-ID: <20040401172401.GD2132@conectiva.com.br> (raw)
In-Reply-To: <20040401142458.GB2132@conectiva.com.br>
Another output with all debug options enabled.
cascade: c03b3128 != c03b28c0
kernel/timer.c:296: spin_lock(kernel/timer.c:c03b28c0) already locked by kernel/timer.c/401
handler=c03b3120 (0xc03b3120)
Call Trace:
[<c01347ef>] cascade+0x7f/0xb0
[<c0135025>] run_timer_softirq+0x315/0x3f0
[<c012fa35>] do_softirq+0xa5/0xb0
[<c010caea>] do_IRQ+0x21a/0x360
[<c012b5bf>] profile_hook+0x1f/0x23
[<c010a934>] common_interrupt+0x18/0x20
[<c0107066>] default_idle+0x26/0x40
[<c01070f4>] cpu_idle+0x34/0x40
[<c0434829>] start_kernel+0x189/0x1e0
[<c0434540>] unknown_bootoption+0x0/0x120
cascade: c03b2f88 != c03b28c0
handler=c03b2f80 (0xc03b2f80)
Call Trace:
[<c01347ef>] cascade+0x7f/0xb0
[<c0135025>] run_timer_softirq+0x315/0x3f0
[<c012fa35>] do_softirq+0xa5/0xb0
[<c010caea>] do_IRQ+0x21a/0x360
[<c012b5bf>] profile_hook+0x1f/0x23
[<c010a934>] common_interrupt+0x18/0x20
[<c0107066>] default_idle+0x26/0x40
[<c01070f4>] cpu_idle+0x34/0x40
[<c0434829>] start_kernel+0x189/0x1e0
[<c0434540>] unknown_bootoption+0x0/0x120
cascade: c03b2910 != c03b28c0
handler=c03b2908 (0xc03b2908)
Call Trace:
[<c01347ef>] cascade+0x7f/0xb0
[<c0135025>] run_timer_softirq+0x315/0x3f0
[<c012fa35>] do_softirq+0xa5/0xb0
[<c010caea>] do_IRQ+0x21a/0x360
[<c012b5bf>] profile_hook+0x1f/0x23
[<c010a934>] common_interrupt+0x18/0x20
[<c0107066>] default_idle+0x26/0x40
[<c01070f4>] cpu_idle+0x34/0x40
[<c0434829>] start_kernel+0x189/0x1e0
[<c0434540>] unknown_bootoption+0x0/0x120
--
Flávio Bruno Leitner <fbl@conectiva.com.br>
[ E74B 0BD0 5E05 C385 239E 531C BC17 D670 7FF0 A9E0 ]
next prev parent reply other threads:[~2004-04-01 17:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-31 17:16 kernel BUG at kernel/timer.c:370! 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 [this message]
2004-04-01 18:37 ` Andrew Morton
2004-04-02 14:42 ` Flavio Bruno Leitner
-- strict thread matches above, loose matches on Subject: below --
2004-04-01 19:05 Craig, Dave
2004-03-31 21:39 Craig, Dave
2004-03-31 22:15 ` Andrew Morton
2004-03-31 16:59 Craig, Dave
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-02-14 3:33 Rafael D'Halleweyn (List)
2004-02-14 8:21 ` Andrew Morton
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=20040401172401.GD2132@conectiva.com.br \
--to=fbl@conectiva.com.br \
--cc=akpm@osdl.org \
--cc=dwcraig@qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=list@noduck.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox