From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Richard Cochran <richardcochran@gmail.com>,
Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: powerpc: mpc85xx regression since 2.6.39-rc2, one cpu core lame
Date: Wed, 18 May 2011 07:40:16 +1000 [thread overview]
Message-ID: <1305668416.2781.23.camel@pasglop> (raw)
In-Reply-To: <20110517162827.GA16918@riccoc20.at.omicron.at>
On Tue, 2011-05-17 at 18:28 +0200, Richard Cochran wrote:
> Ben,
>
> Recent 2.6.39-rc kernels behave strangely on the Freescale dual core
> mpc8572 and p2020. There is a long pause (like 2 seconds) in the boot
> sequence after "mpic: requesting IPIs..."
>
> When the system comes up, only one core shows in /proc/cpuinfo. Later
> on, lots of messages appear like the following:
>
> INFO: task ksoftirqd/1:9 blocked for more than 120 seconds.
>
> I bisected [1] the problem to:
>
> commit c56e58537d504706954a06570b4034c04e5b7500
> Author: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> Date: Tue Mar 8 14:40:04 2011 +1100
>
> powerpc/smp: Create idle threads on demand and properly reset them
>
> I don't see from that commit what had gone wrong. Perhaps you can
> help resolve this?
Hrm, odd. Kumar, care to have a look ? That's what happens when you
don't get me HW to test with :-)
Cheers,
Ben.
> Thanks,
> Richard
>
>
> 1. I had to patch commit e5462d16 by hand when bisecting, which is a
> fixup for commit fa3f82c8 and not yet merged in c56e5853.
next prev parent reply other threads:[~2011-05-17 21:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 16:28 powerpc: mpc85xx regression since 2.6.39-rc2, one cpu core lame Richard Cochran
2011-05-17 21:40 ` Benjamin Herrenschmidt [this message]
2011-05-18 12:03 ` Richard Cochran
2011-05-18 17:19 ` Milton Miller
2011-05-18 21:48 ` Benjamin Herrenschmidt
2011-05-18 21:48 ` Benjamin Herrenschmidt
2011-05-19 5:32 ` Kumar Gala
2011-05-19 5:33 ` Kumar Gala
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=1305668416.2781.23.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=richardcochran@gmail.com \
/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).