linux-kernel - Re: [Bug 199965] New: Memory management: BUG in kernel

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Sun, 10 Jun 2018 08:53:40 +0200
From:   Mateusz Lenik <mlen@...n.pl>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     Andrew Morton <akpm@...ux-foundation.org>,
        bugzilla-daemon@...zilla.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [Bug 199965] New: Memory management: BUG in kernel_restart

On Sat, Jun 09, 2018 at 04:07:26PM +0200, Greg Kroah-Hartman wrote:
> Here's the full callstack, but yeah, it's not very obvious as to what
> device is having the problem, which isn't good.  I don't know what to
> suggest here.

I think it is related to amdgpu -- when the script that unbinds the 
second GPU from host is not executed, there are no issues during reboot.

I found out that amdgpu leaves i2c-dev and hwmon device nodes after 
unbind, which seems to be a bug in that driver.  In 4.16, it only left 
stale hwmon node.

Best,
Mateusz

-- 
mlen

Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)