4.4-rc5 Setting trap flag inside nmi handler results in HARD LOCKUP

Path	csiph.com!eternal-september.org!feeder.eternal-september.org!aioe.org!bofh.it!news.nic.it!robomod
From	Jeff Merkey <linux.mdb@gmail.com>
Newsgroups	linux.kernel
Subject	4.4-rc5 Setting trap flag inside nmi handler results in HARD LOCKUP
Date	Wed, 16 Dec 2015 19:20:03 +0100
Message-ID	<qGoQb-5f3-51@gated-at.bofh.it> (permalink)
X-Original-To	LKML <linux-kernel@vger.kernel.org>
Dkim-Signature	v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=pU/BkgaJHAhGBntp5Lzhu9taR37+fxy/wLKoqkbpbbI=; b=V4HTO9JHDHo35xyWwlWE1LtqDO8nrGWaT/2Bl+13oyztT/sICpDkuE1cmS5z8SyKKJ KAUxl5HWPXxYm8nmwiZEuZJNc58bwxXLU+Gkl03RSmqhqFMJ3UbFofhbICo5TAxfpATg bfDntxEsqntbVnKBtOlxhSSu5bbZPSOxI8gjbVx9G8Uhnui1PsKIQt9GJ6YO0pZwCyWv 3q9csXuixyBfYFI91ABE7ybXi5PLzAxx3oXXon5huos6kHN97HMSVs6g8HzUufbYzO/F yLAvG9qOS9Bf/cZl2yDY/JAAs9Zyety9VKu2OdnyzOntxkNx3reW96JnLHhS3cZ4JGUF 6TWg==
MIME-Version	1.0
X-Received	by 10.50.73.1 with SMTP id h1mr11889580igv.88.1450289961550; Wed, 16 Dec 2015 10:19:21 -0800 (PST)
Content-Type	text/plain; charset=UTF-8
Sender	robomod@news.nic.it
List-ID	<linux-kernel.vger.kernel.org>
X-Mailing-List	linux-kernel@vger.kernel.org
Approved	robomod@news.nic.it
Lines	23
Organization	linux.* mail to news gateway
X-Original-Cc	tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com, x86@kernel.org, peterz@infradead.org, luto@kernel.org
X-Original-Date	Wed, 16 Dec 2015 11:19:21 -0700
X-Original-Message-ID	<CAO6TR8UPzM9J+JDhpZpBseNLX7mV35d-tAEk6dj4AM=O=+qJdA@mail.gmail.com>
X-Original-Sender	linux-kernel-owner@vger.kernel.org
Xref	csiph.com linux.kernel:1293269

Show key headers only | View raw

Setting the (trap flag | resume flag) inside of an nmi handler results
in a hard lockup while setting the resume flag works fine.

The watchdog detector fails to detect the lockup.  I am currently
examining the trap gate and interrupt gate setup on Linux and if
anyone has any ideas it would be nice to be able to debug and step
through the nmi handlers.  I got breakpoints to work.  I noticed
kgdb/kdb just punts here and refuses to allow someone to step inside
an nmi handler.

There is no reason Linux should not allow this to work since windows
does and every other OS out there.  I have seen this across some rex64
sysret calls as well this lockup behavior.

Anyone who is an intel expert with any clues would love some input if
you know about this problem.

Jeff
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

4.4-rc5 Setting trap flag inside nmi handler results in HARD LOCKUP Jeff Merkey <linux.mdb@gmail.com> - 2015-12-16 19:20 +0100
  Re: 4.4-rc5 Setting trap flag inside nmi handler results in HARD LOCKUP Jeff Merkey <linux.mdb@gmail.com> - 2015-12-16 19:50 +0100
    Re: 4.4-rc5 Setting trap flag inside nmi handler results in HARD LOCKUP Jeff Merkey <linux.mdb@gmail.com> - 2015-12-16 22:50 +0100
    Re: 4.4-rc5 Setting trap flag inside nmi handler results in HARD LOCKUP Jeff Merkey <linux.mdb@gmail.com> - 2015-12-16 23:10 +0100
  Re: 4.4-rc5 Setting trap flag inside nmi handler results in HARD LOCKUP Jeff Merkey <linux.mdb@gmail.com> - 2015-12-17 08:30 +0100

csiph-web