linux-kernel - Re: kernel-4.9.270 crash

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] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 6 Sep 2021 06:59:22 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     wim <wim@....tudelft.nl>
Cc:     stable@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: kernel-4.9.270 crash

On Sun, Sep 05, 2021 at 09:00:45PM +0200, wim wrote:
> On Sun, Sep 05, 2021 at 01:52:31AM +0200, wim wrote:
> > 
> > Hello Greg,
> > 
> > from kernel-4.9.270 up until now (4.9.282) I experience kernel crashes upon
> > loading a GPU module.
> > It happens on two out of at least six different machines.
> > I can't believe that I'm the only one where that happens, but since the bug
> > is still there twelve versions later, I need to report this.
> > 
> > I run Gentoo with vanilla kernels.
> > Upon loading i915.ko (automatically or manually) my laptop freezes until
> > power-down. (Note that other machines using i915.ko have no problems here.)
> > It's an Asus laptop with Intel chipset with a peculiarity:
> > 
> >  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
> >  01:00.0 3D controller: NVIDIA Corporation GM108M [GeForce 940MX] (rev a2)
> > 
> > (It uses Intel natively and nobody knows how to make use of that Nvidia chip)
> > 
> > 
> > On an AMD desktop I get the same crash upon loading of nouveau.ko .
> > 
> > Something ugly must have been introduced in kernel-4.9.270 .
> > Strace modprobe .. only prints two lines on the screen.
> > Strace modprobe .. 2>&1 > file produces only an empty file.
> > 
> > Any ideas?

Do you have any kernel log messages when these crashes happen?

Can you use 'git bisect' to track down the offending commit?

And why are you stuck on 4.9.y for these machines?  Why not use 5.10 or
newer?

thanks,

greg k-h