From: Ravikiran G Thirumalai <kiran@scalex86.org>
To: "Bizhan Gholikhamseh (bgholikh)" <bgholikh@cisco.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel panic:BUG in cascade at kernel/timer.c
Date: Thu, 10 Aug 2006 18:00:00 -0700 [thread overview]
Message-ID: <20060811010000.GA3855@localhost.localdomain> (raw)
In-Reply-To: <F795765B112E7344AF36AA9112796415019ED349@xmb-sjc-212.amer.cisco.com>
On Thu, Aug 10, 2006 at 02:26:15PM -0700, Bizhan Gholikhamseh (bgholikh) wrote:
> Hi All,
> We have developed our own custom board based on MPC8541 board running
> linux 2.6.11 During stress testing the system we get following kernel
> panic which related to timer cascase.
> Any hints greatly apprieciated. Many thanks in advance:
Is this an MP configuration? If timer interrupts are distributed to more
than one cpu this could happen (buggy hardware). Also, I remember a missing
barrier someplace for PPC which was fixed in newer kernels. Read the GIT logs.
HTH
Kiran
prev parent reply other threads:[~2006-08-11 0:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 21:26 kernel panic:BUG in cascade at kernel/timer.c Bizhan Gholikhamseh (bgholikh)
2006-08-10 22:48 ` Alexey Dobriyan
2006-08-11 1:00 ` Ravikiran G Thirumalai [this message]
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=20060811010000.GA3855@localhost.localdomain \
--to=kiran@scalex86.org \
--cc=bgholikh@cisco.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox