| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 19 Jun 2019 20:19:38 +0100 From: Chris Wilson <chris@...is-wilson.co.uk> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: Linux List Kernel Mailing <linux-kernel@...r.kernel.org> Subject: Re: NMI hardlock stacktrace deadlock [was Re: Linux 5.2-rc5] Quoting Linus Torvalds (2019-06-19 19:49:37) > On Wed, Jun 19, 2019 at 5:40 AM Chris Wilson <chris@...is-wilson.co.uk> wrote: > > > > I haven't bisected this, but with the merge of rc5 into our CI we > > started hitting an issue that resulted in a oops and the NMI watchdog > > firing as we dumped the ftrace. > > Do you have the oops itself at all? An example at https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6310/fi-kbl-x1275/dmesg0.log https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6310/fi-kbl-x1275/boot0.log The bug causing the oops is clearly a driver problem. The rc5 fallout just seems to be because of some shrinker changes affecting some object reaping that were unfortunately still active. What perturbed the CI team was the machine failed to panic & reboot. -Chris
Powered by blists - more mailing lists