All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Engelhardt <jengelh@inai.de>
To: sparclinux@vger.kernel.org
Subject: Re: Generic idle causes boot hang on T1000
Date: Mon, 24 Mar 2014 10:33:30 +0000	[thread overview]
Message-ID: <alpine.LSU.2.11.1403241130370.29957@nerf08.vanv.qr> (raw)
In-Reply-To: <alpine.LSU.2.11.1403232347380.23553@nerf08.vanv.qr>


On Monday 2014-03-24 01:38, David Miller wrote:
>> Trying to update beyond 3.9 gives me a boot hang on SPARC T1000.
>> The following commit is the result of the bisect:
>> 
>> commit 87fa05aeb3a5e8e21b1a5510eef6983650eff092
>> Author: Sam Ravnborg <sam@ravnborg.org>
>> Date:   Thu Apr 11 21:38:50 2013 +0200
>> 
>>     sparc: Use generic idle loop
>
>Interesting.
>
>> mptbase: ioc0: Initiating bringup
>> <hangs>
>> 
>> after ~1 minute:
>> 
>> INFO: rcu_sched self-detected stall on CPU { 0}  (t0061 jiffies
>> g\x18446744073709551319 c\x18446744073709551318 qA4)
>> INFO: rcu_sched detected stalls on CPUs/tasks:* CPU[  0]:
>> TSTATE[0000000080001603] TPC[000000000042b9b4] TNPC[000000000042b9b8]
>> TASK[swapper/0:0]
>>              TPC[arch_cpu_idle+0x74/0xa0] O7[arch_cpu_idle+0x5c/0xa0]
>>  I7[cpu_startup_entry+0x114/0x1a0] RPC[start_kernel+0x384/0x394]
>
>I suspect the cpu yield hypervisor call requires local cpu interrupts
>to be enabled in order to function properly.  Prior to this commit
>above, they did.
>
>Please try this:
>
>commit 87fa05aeb3a5e8e21b1a5510eef6983650eff092

This is the same commit as before (both in ID, as well as patch content).
Did you intend to paste another patch?


  parent reply	other threads:[~2014-03-24 10:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-23 22:47 Generic idle causes boot hang on T1000 Jan Engelhardt
2014-03-24  0:38 ` David Miller
2014-03-24 10:33 ` Jan Engelhardt [this message]
2014-03-24 16:53 ` David Miller
2014-03-24 18:19 ` Jan Engelhardt
2014-03-24 18:36 ` David Miller

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=alpine.LSU.2.11.1403241130370.29957@nerf08.vanv.qr \
    --to=jengelh@inai.de \
    --cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.