linux-kernel - regression in drm

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

Message-ID: <CAH2r5mu+yZv2W26dhqE2mL1JZfTuK+=8hgLZTv6TVYLwmF8aqA@mail.gmail.com>
Date:   Thu, 28 Jan 2021 11:12:50 -0600
From:   Steve French <smfrench@...il.com>
To:     LKML <linux-kernel@...r.kernel.org>
Cc:     Lyude Paul <lyude@...hat.com>,
        Daniel Vetter <daniel.vetter@...ll.ch>,
        Ville Syrjälä <ville.syrjala@...ux.intel.com>
Subject: regression in drm_blank.c?

For the last month my logs have been flooded many times a second with:

"nouveau 0000:01:00.0: [drm] *ERROR* crtc 50: Can't calculate
constants, dotclock = 0!"

(see line 641 of drm_vblank.c) which is distracting for debugging all
other kernel problems (since dmesg entries on this system are 99+%
this message).

Am running current kernel ie 5.11-rc5 (although it also was very very
noisty in 5.10), Ubuntu mainline kernel builds, Lenovo P52 Thinkpad
laptop.  Could it be due to one of the more recent changes to
drivers/gpu/drm/drm_vblank.c?

Ideas how to workaround this?

-- 
Thanks,

Steve