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: Thu, 9 Mar 2017 11:22:53 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1703091118230.3521@nanos> (raw)
In-Reply-To: <1489001551.2813.3.camel@sandisk.com>
Bart,
On Wed, 8 Mar 2017, Bart Van Assche wrote:
> Sorry but the cpuhp_issue_call() still occurs with Linus' latest tree
> (commit ec3b93ae0bf4 / Merge branch 'x86-urgent-for-linus' of
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip).
>
> This morning I discovered that the hang only occurs if I/O AT support is
> enabled in the BIOS. I had enabled I/O AT support in the BIOS on February
> 23rd. With I/O AT support enabled the following warning appears during boot:
That's interesting, but I have no idea how that's related.
> WARNING: CPU: 8 PID: 596 at drivers/dma/ioat/dca.c:342 ioat_dca_init+0x185/0x190 [ioatdma]
> ioatdma 0000:00:04.0: APICID_TAG_MAP set incorrectly by BIOS, disabling DCA
..
> In contrast with previous tests this morning I have been able to reproduce
> this hang with kernel v4.10. So it's not a kernel v4.10 regression. But the
> hang did not occur in a test with kernel v4.9.7. I assume this means that
> the regression got introduced between the v4.9 and v4.10 kernels.
Is it always the x86_pkg_thermal init which locks up?
Thanks,
tglx
next prev parent reply other threads:[~2017-03-09 10:23 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
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 [this message]
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.1703091118230.3521@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox