From: Vitaly Bordug <vbordug@ru.mvista.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: preempt crash in 2.6.18
Date: Sun, 15 Oct 2006 13:20:58 +0400 [thread overview]
Message-ID: <20061015132058.01c68605@localhost.localdomain> (raw)
In-Reply-To: <1160781278.4792.279.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 863 bytes --]
On Sat, 14 Oct 2006 09:14:38 +1000
Benjamin Herrenschmidt wrote:
> On Sat, 2006-10-14 at 01:21 +0400, Vitaly Bordug wrote:
> > On Fri, 13 Oct 2006 09:16:52 -0500
> > Rune Torgersen wrote:
> >
> > >
> > > This is from a Freescale 8265 running 2.6.18
> > > Anyone have any idea what this is and how to fix it?
> > >
> > Yes. Actually, I recall alike thing and used to fix with proper
> > spin-locking if the cascade PCI irq, which apparently does do_irq
> > that seems to confuse preempt counters.
> >
> > Just a pure guess.
>
> How so ? Cascades shouldn't do do_IRQ with the new irq code anyway
> unless this is still arch/ppc, they should do either __do_IRQ or
> better, generic_handle_irq().
>
To clarify - I was about __do_IRQ and arch/ppc.
Anyway, cascade for PCI is the first place I'd give a look.
--
Sincerely,
-Vitaly
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-10-15 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 14:16 preempt crash in 2.6.18 Rune Torgersen
2006-10-13 21:21 ` Vitaly Bordug
2006-10-13 23:14 ` Benjamin Herrenschmidt
2006-10-15 9:20 ` Vitaly Bordug [this message]
2006-10-16 13:50 ` Rune Torgersen
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=20061015132058.01c68605@localhost.localdomain \
--to=vbordug@ru.mvista.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).