All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rick Warner <rick@microway.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [bisected] rcu_sched detected stalls - 4.15 or newer kernel with some Xeon skylake CPUs and extended APIC
Date: Thu, 17 May 2018 11:59:42 -0400	[thread overview]
Message-ID: <df100e7c-ffd9-5afe-41c2-fb00f43bc255@microway.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1805171418210.1947@nanos.tec.linutronix.de>

Success!

This resolved the issue.  Thanks Thomas!

Rick

On 05/17/18 08:36, Thomas Gleixner wrote:
> Rick,
>
> On Wed, 16 May 2018, Rick Warner wrote:
>
>> I've attached the dmesg output with the kernel parameter and supplied patch.
> Thanks for providing the data. I think I know what's wrong here. Does the
> patch below fix your problem?
>
> While you test, I go looking for a big brown paperbag.
>
> Thanks,
>
> 	tglx
>
> 8<----------------
>
> --- a/arch/x86/kernel/apic/x2apic_cluster.c
> +++ b/arch/x86/kernel/apic/x2apic_cluster.c
> @@ -124,6 +124,7 @@ static void init_x2apic_ldr(void)
>  			goto update;
>  	}
>  	cmsk = cluster_hotplug_mask;
> +	cmsk->clusterid = cluster;
>  	cluster_hotplug_mask = NULL;
>  update:
>  	this_cpu_write(cluster_masks, cmsk);

  reply	other threads:[~2018-05-17 15:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-01 16:37 stall/hang on 4.15 kernel with some Xeon skylake CPUs and extended APIC Rick Warner
2018-05-15 16:07 ` [bisected] rcu_sched detected stalls - 4.15 or newer " Rick Warner
2018-05-15 20:19   ` Thomas Gleixner
2018-05-16 14:50     ` Thomas Gleixner
2018-05-16 23:02       ` Rick Warner
2018-05-17 12:36         ` Thomas Gleixner
2018-05-17 15:59           ` Rick Warner [this message]
2018-05-17 19:03           ` [tip:x86/urgent] x86/apic/x2apic: Initialize cluster ID properly tip-bot for Thomas Gleixner

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=df100e7c-ffd9-5afe-41c2-fb00f43bc255@microway.com \
    --to=rick@microway.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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.