public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 11:24:58 -0300	[thread overview]
Message-ID: <20040401142458.GB2132@conectiva.com.br> (raw)
In-Reply-To: <0320111483D8B84AAAB437215BBDA526847F70@NAEX01.na.qualcomm.com>

On Wed, Mar 31, 2004 at 09:16:52AM -0800, Craig, Dave wrote:
> cascade: c1a1d5e0 != c1a0d5e0
> hander=c028ee8d (igmp_ifc_timer_expire+0x0/0x3e)
> Call Trace:
>  [<c012ca73>] cascade+0x79/0xa1
>  [<c028ee8d>] igmp_ifc_timer_expire+0x0/0x3e
>  [<c012d0b3>] run_timer_softirq+0x159/0x1c9
>  [<c012899d>] do_softirq+0xc9/0xcb
>  [<c0119c46>] smp_apic_timer_interrupt+0xd8/0x140
>  [<c0108c09>] default_idle+0x0/0x32
>  [<c010bab2>] apic_timer_interrupt+0x1a/0x20
>  [<c0108c09>] default_idle+0x0/0x32
>  [<c0108c36>] default_idle+0x2d/0x32
>  [<c0108cb4>] cpu_idle+0x3a/0x43
>  [<c0105000>] rest_init+0x0/0x68
>  [<c039c89f>] start_kernel+0x1b7/0x209
>  [<c039c427>] unknown_bootoption+0x0/0x124
> 
> Here is the result.  I am doing a lot of IPv4 multicast.

Applied the patch, here is the result.
cascade: c040b170 != c040ab00           
handler=c040b168 (0xc040b168)
Call Trace:                  
 [<c012741f>] cascade+0x7f/0xb0
 [<c0127a3e>] run_timer_softirq+0xee/0x170
 [<c0123b15>] do_softirq+0xa5/0xb0        
 [<c010b625>] do_IRQ+0xe5/0x120   
 [<c0109a94>] common_interrupt+0x18/0x20
 [<c0107066>] default_idle+0x26/0x40    
 [<c01070f4>] cpu_idle+0x34/0x40    
 [<c03b0829>] start_kernel+0x189/0x1e0
 [<c03b0540>] unknown_bootoption+0x0/0x120
                                          
cascade: c040ab20 != c040ab00
handler=c040ab18 (0xc040ab18)
Call Trace:                  
 [<c012741f>] cascade+0x7f/0xb0
 [<c0127a3e>] run_timer_softirq+0xee/0x170
 [<c0123b15>] do_softirq+0xa5/0xb0        
 [<c010b625>] do_IRQ+0xe5/0x120   
 [<c0109a94>] common_interrupt+0x18/0x20
 [<c0107066>] default_idle+0x26/0x40    
 [<c01070f4>] cpu_idle+0x34/0x40    
 [<c03b0829>] start_kernel+0x189/0x1e0
 [<c03b0540>] unknown_bootoption+0x0/0x120


-- 
Flávio Bruno Leitner <fbl@conectiva.com.br>
[ E74B 0BD0 5E05 C385 239E  531C BC17 D670 7FF0 A9E0 ]

  parent reply	other threads:[~2004-04-01 14:25 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 [this message]
2004-04-01 17:24   ` Flavio Bruno Leitner
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=20040401142458.GB2132@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