From: Thomas Gleixner <tglx@linutronix.de>
To: Bart Van Assche <Bart.VanAssche@sandisk.com>
Cc: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"mingo@kernel.org" <mingo@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"hpa@zytor.com" <hpa@zytor.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Subject: Re: [GIT pull] CPU hotplug updates for 4.9
Date: Tue, 7 Mar 2017 10:30:00 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1703071027340.3584@nanos> (raw)
In-Reply-To: <1488851515.6858.2.camel@sandisk.com>
On Tue, 7 Mar 2017, Bart Van Assche wrote:
> On Mon, 2016-10-03 at 19:37 +0200, Thomas Gleixner wrote:
> > Yet another batch of cpu hotplug core updates and conversions:
>
> Hello Thomas,
>
> Although I'm not sure this behavior has been introduced by the changes in this
> pull request, since I started testing v4.11-rc[01] I ran several times into a
> cpuhp_issue_call() hang:
...
> INFO: task systemd-udevd:837 blocked for more than 480 seconds.
> Tainted: G I 4.11.0-rc1-dbg+ #1
> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> systemd-udevd D 0 837 542 0x00000104
> Call Trace:
> __schedule+0x302/0xc30
> schedule+0x38/0x90
> schedule_timeout+0x255/0x490
> wait_for_completion+0x103/0x170
> cpuhp_issue_call+0xb9/0xe0
> __cpuhp_setup_state+0xf6/0x180
> pkg_temp_thermal_init+0x76/0x1000 [x86_pkg_temp_thermal]
> do_one_initcall+0x3e/0x170
> do_init_module+0x5a/0x1ed
> load_module+0x2339/0x2a40
> SYSC_finit_module+0xbc/0xf0
> SyS_finit_module+0x9/0x10
> do_syscall_64+0x57/0x140
> entry_SYSCALL64_slow_path+0x25/0x25
>
> Kernel v4.10 runs fine on the same system. From the dmidecode output:
That's odd. There was no change related to the hotplug stuff post 4.10
neither in the core nor in that particular driver.
I have no immediate clue what to look for aside of asking you whether you
could do a bisect between 4.10 and 4.11-rc1.
Thanks,
tglx
next prev parent reply other threads:[~2017-03-07 11:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-03 17:37 [GIT pull] CPU hotplug updates for 4.9 Thomas Gleixner
2017-03-07 1:52 ` Bart Van Assche
2017-03-07 9:30 ` Thomas Gleixner [this message]
2017-03-07 22:32 ` Bart Van Assche
2017-03-08 8:25 ` Thomas Gleixner
2017-03-08 19:32 ` Bart Van Assche
2017-03-09 10:22 ` Thomas Gleixner
2017-03-09 17:20 ` Bart Van Assche
2017-03-09 17:43 ` Thomas Gleixner
2017-03-09 22:48 ` Bart Van Assche
2017-03-10 7:23 ` Ingo Molnar
2017-03-10 17:37 ` Bart Van Assche
2017-03-10 21:32 ` Bart Van Assche
2017-03-14 15:06 ` [PATCH] cpu/hotplug: Serialize callback invocations proper Sebastian Andrzej Siewior
2017-03-14 17:38 ` Bart Van Assche
2017-03-14 17:43 ` Thomas Gleixner
2017-03-14 18:25 ` [tip:smp/urgent] " tip-bot for Sebastian Andrzej Siewior
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.DEB.2.20.1703071027340.3584@nanos \
--to=tglx@linutronix.de \
--cc=Bart.VanAssche@sandisk.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=torvalds@linux-foundation.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.