From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Prakash Punnoor <prakash@punnoor.de>
Cc: LKML <linux-kernel@vger.kernel.org>, luto@kernel.org, mingo@kernel.org
Subject: Re: hard lock-up with 4.14 git
Date: Fri, 13 Oct 2017 13:56:04 +0200 [thread overview]
Message-ID: <20171013115604.GD235@x4> (raw)
In-Reply-To: <dde8f3cb-ff08-707f-1c52-c947739abd88@punnoor.de>
On 2017.10.13 at 13:39 +0200, Prakash Punnoor wrote:
> after some use (eg. compiling packages) the machine locks up hard. Magic
> SysRq doesn't work.
>
> I had trouble bisecting the offending commit. This is my third try. And
> it points to 94b1b03b519b81c494900cb112aa00ed205cc2d9 "x86/mm: Rework
> lazy TLB mode and TLB freshness tracking".
>
> Does it make sense? It still locks up with master. Please let me know if
> you need more infos. Please CC, as I am not subscribed.
This is a known issue. The fix is here:
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1508009.html
--
Markus
next prev parent reply other threads:[~2017-10-13 11:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 11:39 hard lock-up with 4.14 git Prakash Punnoor
2017-10-13 11:43 ` Prakash Punnoor
2017-10-13 11:56 ` Markus Trippelsdorf [this message]
2017-10-13 15:12 ` Prakash Punnoor
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=20171013115604.GD235@x4 \
--to=markus@trippelsdorf.de \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=prakash@punnoor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox