linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: Linux/PPC Development <linuxppc-dev@ozlabs.org>,
	Aaron Tokhy <atokhy@gmail.com>
Subject: Re: [PROBLEM] Soft lockup on Linux 2.6.27, 2 patches, Cell/PPC64
Date: Wed, 15 Oct 2008 22:37:33 +1100	[thread overview]
Message-ID: <1224070653.8157.452.camel@pasglop> (raw)
In-Reply-To: <Pine.LNX.4.64.0810151135330.1133@vixen.sonytel.be>


> > Well, at the time of the sample, the other CPU indeed -seems- to be in
> > an IRQ disabled section yes. 
> 
> This is not really a sample. The hardirqs enable/disable is actually tracked
> using the TRACE_{EN,DIS}ABLE_INTS macros.

That's what I meant. IE. the hardirq state was updated by the stuck CPU
but sampled by the non-stuck one. ie. the non-stuck one could have
sampled a transcient value where it happened to have hard irq
disabled...

> For the decrementer, the interrupt code is generated by the
> STD_EXCEPTION_COMMON_LITE() macro.

Yeah, I know that :-)

> Aha, none of the PPC interrupt handlers actually us TRACE_ENABLE_INTS (they do
> use TRACE_DISABLE_INTS). So that's why it thinks decrementer_common disabled
> interrupts, without enabling them again...

Well, they aren't supposed to enable IRQs if they were disabled...

Ben.

> With kind regards,
> 
> Geert Uytterhoeven
> Software Architect
> 
> Sony Techsoft Centre Europe
> The Corporate Village · Da Vincilaan 7-D1 · B-1935 Zaventem · Belgium
> 
> Phone:    +32 (0)2 700 8453
> Fax:      +32 (0)2 700 8622
> E-mail:   Geert.Uytterhoeven@sonycom.com
> Internet: http://www.sony-europe.com/
> 
> A division of Sony Europe (Belgium) N.V.
> VAT BE 0413.825.160 · RPR Brussels
> Fortis · BIC GEBABEBB · IBAN BE41293037680010

  reply	other threads:[~2008-10-15 11:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-12  4:32 [PROBLEM] Soft lockup on Linux 2.6.27, 2 patches, Cell/PPC64 Aaron Tokhy
2008-10-13  7:58 ` Geert Uytterhoeven
2008-10-14  9:32   ` Geert Uytterhoeven
2008-10-15  4:49     ` Benjamin Herrenschmidt
2008-10-15  9:25       ` Geert Uytterhoeven
2008-10-15  9:28         ` Benjamin Herrenschmidt
2008-10-15  9:46           ` Geert Uytterhoeven
2008-10-15 11:37             ` Benjamin Herrenschmidt [this message]
2008-10-15 11:46               ` Geert Uytterhoeven
2008-10-15 11:49                 ` Benjamin Herrenschmidt
2008-10-15 12:05                   ` Geert Uytterhoeven
2008-10-15 20:53                     ` Benjamin Herrenschmidt

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=1224070653.8157.452.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=Geert.Uytterhoeven@sonycom.com \
    --cc=atokhy@gmail.com \
    --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).