From: Flavio Bruno Leitner <fbl@conectiva.com.br>
To: linux-kernel@vger.kernel.org
Subject: kernel BUG at kernel/timer.c:370!
Date: Fri, 5 Mar 2004 14:40:49 -0300 [thread overview]
Message-ID: <20040305174049.GA1759@conectiva.com.br> (raw)
Hello!
My laptop is an Acer TravelMate 630 and somewhere between 2.6.2 and 2.6.3-rc2
begins returning an oops right after boot.
kernel BUG at kernel/timer.c:370!
invalid operand: 0000 [#1]
CPU: 0
EIP: 0060:[<c0127177>] Not tainted
EFLAGS: 00010006
EIP is at cascade+0x44/0x4e
eax: c03e4368 ebx: c03e02b0 ecx: fffce200 edx: c03e03b0
esi: c03e0398 edi: c03dfa80 ebp: c0387f08 esp: c0387ef4
ds: 007b es: 007b ss: 0068
Process swapper (pid: 0, threadinfo=c0386000 task=c0306520)
Stack: c03dfa80 cde229c4 00000000 c03df7a8 c0387f20 c0387f38 c0127732 c03dfa80
c03e0288 00000022 c0387f34 c0387f20 c0387f20 c0308d64 00000001 c03df7a8
0000000a c0387f54 c0123b7c c03df7a8 00000046 00000000 c037da00 c0308d64
Call Trace:
[<c0127732>] run_timer_softirq+0xec/0x16b
[<c0123b7c>] do_softirq+0x98/0x9a
[<c010d2ff>] do_IRQ+0xe4/0x11c
[<c010b974>] common_interrupt+0x18/0x20
[<d08c8257>] acpi_processor_idle+0xe9/0x1e5 [processor]
[<c0105000>] _stext+0x0/0x2a
[<c01090b7>] cpu_idle+0x2f/0x38
[<c038c70a>] start_kernel+0x185/0x1c9
[<c038c44a>] unknow_bootoption+0x0/0x108
Code: 0f 0b 72 01 3b 05 2d c0 eb d4 55 89 e5 56 53 83 ec 04 0f bf
Here is the function:
static int cascade(tvec_base_t *base, tvec_t *tv, int index)
{
/* cascade all the timers from tv up one level */
struct list_head *head, *curr;
head = tv->vec + index;
curr = head->next;
/*
* We are removing _all_ timers from the list, so we don't have to
* detach them individually, just clear the list afterwards.
*/
while (curr != head) {
struct timer_list *tmp;
tmp = list_entry(curr, struct timer_list, entry);
BUG_ON(tmp->base != base);
curr = curr->next;
internal_add_timer(base, tmp);
}
INIT_LIST_HEAD(head);
return index;
}
Any ideas about this one?
Thanks!
--
Flávio Bruno Leitner <fbl@conectiva.com.br>
[ E74B 0BD0 5E05 C385 239E 531C BC17 D670 7FF0 A9E0 ]
next reply other threads:[~2004-03-05 17:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 17:40 Flavio Bruno Leitner [this message]
2004-03-05 23:06 ` kernel BUG at kernel/timer.c:370! 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
-- 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 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 16:59 Craig, Dave
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=20040305174049.GA1759@conectiva.com.br \
--to=fbl@conectiva.com.br \
--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.