linux-kernel - Re: Bug report for kernel v4.15-rc8+

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]

Message-ID: <877dgtql9v.ffs@tglx>
Date:   Tue, 10 Aug 2021 19:09:32 +0200
From:   Thomas Gleixner <tglx@...utronix.de>
To:     blinkin@...il.it
Cc:     linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Bug report for kernel v4.15-rc8+

On Tue, Aug 10 2021 at 16:05, blinkin@...il.it wrote:
> The general symptom is a slow and unresponsive system (e.g. on gnome
> there's a delay before displaying typed characters, up to 3-5
> seconds. Animations are jittering, mouse clicks sometimes are missed).
> 3D games are now impossible to play due to poor performance.
>
> System feels as if the CPU is always busy (htop shows one core at ~
> 90% most of the time both with and without the workaround, not sure
> it's correlated)

That's definitely wrong. What is consuming CPU time?

> It's running OpenSuse Leap 15.2 (the bug came out when upgrading from
> 15.1, thus going from kernel 4.12 to 5.3) I suspect the same bug is
> responsible for making me switch to suse after failing to upgrade
> debian from 9 (kernel 4.9) to 10 (kernel 4.19)
>
> The workaround is to pass irqaffinity=0 on boot.
>
> Attached: dmesg output with and without the irqaffinity parameter,
> lspci output, /proc/cpuinfo contents.
>
> Let me know what else is needed.

1) You're booting with an out of tree module:

   > [   17.080069] vboxdrv: loading out-of-tree module taints kernel.

   Please reproduce without this.

2) Please provide information what is consuming 90% of a CPU

3) Please provide the output of /proc/interrupts for both boot scenarios

   Take a snapshot right after boot and another one a minute later.

Thanks,

        tglx