regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Cc: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: Regression in 5.15 in nouveau #forregzbot
Date: Tue, 21 Dec 2021 18:24:48 +0100	[thread overview]
Message-ID: <297f26ea-fff8-f2f4-6e27-35bbbb87456e@leemhuis.info> (raw)
In-Reply-To: <5dafba25-5424-3fe2-5046-ae1d4320f9c1@leemhuis.info>

Hi, this is your Linux kernel regression tracker speaking. For the record:

https://cgit.freedesktop.org/drm/drm-misc/commit/?h=drm-misc-fixes&id=67f74302f45d5d862f22ced3297624e50ac352f0

#regzbot fixed-by: 67f74302f45d5d862f22ced3297624e50ac352f0

Ciao, Thorsten

P.S.: As a Linux kernel regression tracker I'm getting a lot of reports
on my table. I can only look briefly into most of them. Unfortunately
therefore I sometimes will get things wrong or miss something important.
I hope that's not the case here; if you think it is, don't hesitate to
tell me about it in a public reply. That's in everyone's interest, as
what I wrote above might be misleading to everyone reading this; any
suggestion I gave thus might sent someone reading this down the wrong
rabbit hole, which none of us wants.

BTW, I have no personal interest in this issue, which is tracked using
regzbot, my Linux kernel regression tracking bot
(https://linux-regtracking.leemhuis.info/regzbot/). I'm only posting
this mail to get things rolling again and hence don't need to be CC on
all further activities wrt to this regression.


TWIMC: this mail is primarily send for documentation purposes and for
regzbot, my Linux kernel regression tracking bot. These mails usually
contain '#forregzbot' in the subject, to make them easy to spot and filter.

Ciao, Thorsten, your Linux kernel regression tracker.

On 06.12.21 14:19, Thorsten Leemhuis wrote:
> [TLDR: adding this regression to regzbot; most of this mail is compiled
> from a few templates paragraphs some of you will have seen aready.]
> 
> Hi, this is your Linux kernel regression tracker speaking.
> 
> Top-posting for once, to make this easy accessible to everyone.
> 
> Adding the regression mailing list to the list of recipients, as it
> should be in the loop for all regressions, as explained here:
> https://www.kernel.org/doc/html/latest/admin-guide/reporting-issues.html
> 
> To be sure this issue doesn't fall through the cracks unnoticed, I'm
> adding it to regzbot, my Linux kernel regression tracking bot:
> 
> #regzbot ^introduced 3e1ad79bf66165bdb2baca3989f9227939241f11
> #regzbot title drm: nouveau: annoying black flickering in some
> applications with KDE Plasma with Xorg
> #regzbot ignore-activity
> 
> Reminder: when fixing the issue, please add a 'Link:' tag with the URL
> to the report (the parent of this mail), then regzbot will automatically
> mark the regression as resolved once the fix lands in the appropriate
> tree. For more details about regzbot see footer.
> 
> Sending this to everyone that got the initial report, to make all aware
> of the tracking. I also hope that messages like this motivate people to
> directly get at least the regression mailing list and ideally even
> regzbot involved when dealing with regressions, as messages like this
> wouldn't be needed then.
> 
> Don't worry, I'll send further messages wrt to this regression just to
> the lists (with a tag in the subject so people can filter them away), as
> long as they are intended just for regzbot. With a bit of luck no such
> messages will be needed anyway.
> 
> Ciao, Thorsten, your Linux kernel regression tracker.
> 
> P.S.: As a Linux kernel regression tracker I'm getting a lot of reports
> on my table. I can only look briefly into most of them. Unfortunately
> therefore I sometimes will get things wrong or miss something important.
> I hope that's not the case here; if you think it is, don't hesitate to
> tell me about it in a public reply. That's in everyone's interest, as
> what I wrote above might be misleading to everyone reading this; any
> suggestion I gave they thus might sent someone reading this down the
> wrong rabbit hole, which none of us wants.
> 
> BTW, I have no personal interest in this issue, which is tracked using
> regzbot, my Linux kernel regression tracking bot
> (https://linux-regtracking.leemhuis.info/regzbot/). I'm only posting
> this mail to get things rolling again and hence don't need to be CC on
> all further activities wrt to this regression.
> 
> 
> On 04.12.21 17:40, Stefan Fritsch wrote:
>> Hi,
>>
>> when updating from 5.14 to 5.15 on a system with NVIDIA GP108 [GeForce
>> GT 1030] (NV138) and Ryzen 9 3900XT using kde/plasma on X (not wayland),
>> there is a regression: There is now some annoying black flickering in
>> some applications, for example thunderbird, firefox, or mpv. It mostly
>> happens when scrolling or when playing video. Only the window of the
>> application flickers, not the whole screen. But the flickering is not
>> limited to the scrolled area: for example in firefox the url and
>> bookmark bars flicker, too, not only the web site. I have bisected the
>> issue to this commit:
>>
>> commit 3e1ad79bf66165bdb2baca3989f9227939241f11 (HEAD)
>> Author: Christian König <christian.koenig@amd.com>
>> Date:   Sun Jun 6 11:50:15 2021 +0200
>>
>>     drm/nouveau: always wait for the exclusive fence
>>
>>     Drivers also need to to sync to the exclusive fence when
>>     a shared one is present.
>>
>>     Signed-off-by: Christian König <christian.koenig@amd.com>
>>     Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>>     Link:
>> https://patchwork.freedesktop.org/patch/msgid/20210702111642.17259-4-christian.koenig@amd.com
>>
>>
>>
>> This sounds like performance is impacted severely by that commit. Can
>> this be fixed somehow? A partial dmesg is below.
>>
>> Cheers,
>> Stefan
>>
>>
>> dmesg |grep -i -e drm -e dri -e nvidia -e nouveau -e fb
>> [    0.000000] BIOS-e820: [mem 0x00000000bc552000-0x00000000bc8fbfff]
>> reserved
>> [    0.004971] ACPI: XSDT 0x00000000BCFB0728 0000CC (v01 ALASKA A M I
>> 01072009 AMI  01000013)
>> [    0.010838] PM: hibernation: Registered nosave memory: [mem
>> 0xbc552000-0xbc8fbfff]
>> [    0.204873] Performance Events: Fam17h+ core perfctr, AMD PMU driver.
>> [    0.292761] Registering PCC driver as Mailbox controller
>> [    0.292761] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
>> [    0.518295] pci 0000:06:00.0: reg 0x10: [mem 0xfb000000-0xfbffffff]
>> [    0.519132] pci 0000:06:00.1: [10de:0fb8] type 00 class 0x040300
>> [    0.519653] pci 0000:00:03.1:   bridge window [mem
>> 0xfb000000-0xfc0fffff]
>> [    0.549101] pci 0000:00:03.1:   bridge window [mem
>> 0xfb000000-0xfc0fffff]
>> [    0.550994] pci_bus 0000:06: resource 1 [mem 0xfb000000-0xfc0fffff]
>> [    0.561285] Block layer SCSI generic (bsg) driver version 0.4 loaded
>> (major 250)
>> [    0.564152] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
>> [    0.570870] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
>> [    0.571531] AMD-Vi: AMD IOMMUv2 driver by Joerg Roedel <jroedel@suse.de>
>> [    0.988343] microcode: Microcode Update Driver: v2.2.
>> [    1.112435] ACPI: OSL: Resource conflict; ACPI support missing from
>> driver?
>> [    1.114174] usbcore: registered new interface driver usbfs
>> [    1.114331] usbcore: registered new interface driver hub
>> [    1.114599] usbcore: registered new device driver usb
>> [    2.373857] hid: raw HID events driver (C) Jiri Kosina
>> [    2.378553] usbcore: registered new interface driver usbhid
>> [    2.378641] usbhid: USB HID core driver
>> [    2.581069] ata3.00: supports DRM functions and may not be fully
>> accessible
>> [    2.582388] ata3.00: supports DRM functions and may not be fully
>> accessible
>> [    3.371574] ata5.00: supports DRM functions and may not be fully
>> accessible
>> [    3.396636] ata5.00: supports DRM functions and may not be fully
>> accessible
>> [    4.159005] sr 1:0:0:0: [sr0] scsi3-mmc drive: 48x/48x writer dvd-ram
>> cd/rw xa/form2 cdda tray
>> [    4.159120] cdrom: Uniform CD-ROM driver Revision: 3.20
>> [    5.936017] systemd[1]: Starting Load Kernel Module drm...
>> [    5.957038] systemd[1]: modprobe@drm.service: Deactivated successfully.
>> [    5.957238] systemd[1]: Finished Load Kernel Module drm.
>> [    6.104901] sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver
>> [    6.122007] usbcore: registered new device driver apple-mfi-fastcharge
>> [    6.213866] input: HDA NVidia HDMI/DP,pcm=3 as
>> /devices/pci0000:00/0000:00:03.1/0000:06:00.1/sound/card0/input8
>> [    6.236581] AMD64 EDAC driver v3.5.0
>> [    6.259473] input: HDA NVidia HDMI/DP,pcm=7 as
>> /devices/pci0000:00/0000:00:03.1/0000:06:00.1/sound/card0/input9
>> [    6.259631] input: HDA NVidia HDMI/DP,pcm=8 as
>> /devices/pci0000:00/0000:00:03.1/0000:06:00.1/sound/card0/input10
>> [    6.260559] input: HDA NVidia HDMI/DP,pcm=9 as
>> /devices/pci0000:00/0000:00:03.1/0000:06:00.1/sound/card0/input11
>> [    6.260913] input: HDA NVidia HDMI/DP,pcm=10 as
>> /devices/pci0000:00/0000:00:03.1/0000:06:00.1/sound/card0/input12
>> [    6.485220] nouveau 0000:06:00.0: vgaarb: deactivate vga console
>> [    6.486484] nouveau 0000:06:00.0: NVIDIA GP108 (138000a1)
>> [    6.612994] nouveau 0000:06:00.0: bios: version 86.08.24.00.23
>> [    6.617303] nouveau 0000:06:00.0: pmu: firmware unavailable
>> [    6.621410] nouveau 0000:06:00.0: fb: 2048 MiB GDDR5
>> [    6.653892] nouveau 0000:06:00.0: DRM: VRAM: 2048 MiB
>> [    6.653895] nouveau 0000:06:00.0: DRM: GART: 536870912 MiB
>> [    6.653897] nouveau 0000:06:00.0: DRM: BIT table 'A' not found
>> [    6.653899] nouveau 0000:06:00.0: DRM: BIT table 'L' not found
>> [    6.653900] nouveau 0000:06:00.0: DRM: TMDS table version 2.0
>> [    6.653902] nouveau 0000:06:00.0: DRM: DCB version 4.1
>> [    6.653904] nouveau 0000:06:00.0: DRM: DCB outp 00: 01800346 04600010
>> [    6.653906] nouveau 0000:06:00.0: DRM: DCB outp 01: 01000342 00020010
>> [    6.653908] nouveau 0000:06:00.0: DRM: DCB outp 02: 01011352 00020020
>> [    6.653909] nouveau 0000:06:00.0: DRM: DCB conn 00: 00001046
>> [    6.653911] nouveau 0000:06:00.0: DRM: DCB conn 01: 00002161
>> [    6.654295] nouveau 0000:06:00.0: DRM: MM: using COPY for buffer copies
>> [    6.655460] snd_hda_intel 0000:06:00.1: bound 0000:06:00.0 (ops
>> nv50_audio_component_bind_ops [nouveau])
>> [    6.828018] nouveau 0000:06:00.0: DRM: allocated 3840x2160 fb:
>> 0x200000, bo 000000001a41f1fe
>> [    6.828086] fbcon: nouveau (fb0) is primary device
>> [    6.915486] nouveau 0000:06:00.0: [drm] fb0: nouveau frame buffer device
>> [    6.939244] [drm] Initialized nouveau 1.3.1 20120801 for 0000:06:00.0
>> on minor 0
>> [   11.338075] audit: type=1400 audit(1638634273.245:6):
>> apparmor="STATUS" operation="profile_load" profile="unconfined"
>> name="nvidia_modprobe" pid=1354 comm="apparmor_parser"
>> [   11.338078] audit: type=1400 audit(1638634273.245:7):
>> apparmor="STATUS" operation="profile_load" profile="unconfined"
>> name="nvidia_modprobe//kmod" pid=1354 comm="apparmor_parser"
>> [   11.479123] RTL8226B_RTL8221B 2.5Gbps PHY r8169-500:00: attached PHY
>> driver (mii_bus:phy_addr=r8169-500:00, irq=MAC)
>> stf@k:~/comp/linux/linux$ sudo dmesg |less
>> stf@k:~/comp/linux/linux$ sudo dmesg |grep -i -e drm -e dri -e nvidia -e
>> nouveau -e fb
>> [    0.000000] BIOS-e820: [mem 0x00000000bc552000-0x00000000bc8fbfff]
>> reserved
>> [    0.004971] ACPI: XSDT 0x00000000BCFB0728 0000CC (v01 ALASKA A M I
>> 01072009 AMI  01000013)
>> [    0.010838] PM: hibernation: Registered nosave memory: [mem
>> 0xbc552000-0xbc8fbfff]
>> [    0.204873] Performance Events: Fam17h+ core perfctr, AMD PMU driver.
>> [    0.292761] Registering PCC driver as Mailbox controller
>> [    0.292761] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
>> [    0.518295] pci 0000:06:00.0: reg 0x10: [mem 0xfb000000-0xfbffffff]
>> [    0.519132] pci 0000:06:00.1: [10de:0fb8] type 00 class 0x040300
>> [    0.519653] pci 0000:00:03.1:   bridge window [mem
>> 0xfb000000-0xfc0fffff]
>> [    0.549101] pci 0000:00:03.1:   bridge window [mem
>> 0xfb000000-0xfc0fffff]
>> [    0.550994] pci_bus 0000:06: resource 1 [mem 0xfb000000-0xfc0fffff]
>> [    0.561285] Block layer SCSI generic (bsg) driver version 0.4 loaded
>> (major 250)
>> [    0.564152] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
>> [    0.570870] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
>> [    0.571531] AMD-Vi: AMD IOMMUv2 driver by Joerg Roedel <jroedel@suse.de>
>> [    0.988343] microcode: Microcode Update Driver: v2.2.
>> [    1.112435] ACPI: OSL: Resource conflict; ACPI support missing from
>> driver?
>> [    1.114174] usbcore: registered new interface driver usbfs
>> [    1.114331] usbcore: registered new interface driver hub
>> [    1.114599] usbcore: registered new device driver usb
>> [    2.373857] hid: raw HID events driver (C) Jiri Kosina
>> [    2.378553] usbcore: registered new interface driver usbhid
>> [    2.378641] usbhid: USB HID core driver
>> [    2.581069] ata3.00: supports DRM functions and may not be fully
>> accessible
>> [    2.582388] ata3.00: supports DRM functions and may not be fully
>> accessible
>> [    3.371574] ata5.00: supports DRM functions and may not be fully
>> accessible
>> [    3.396636] ata5.00: supports DRM functions and may not be fully
>> accessible
>> [    4.159005] sr 1:0:0:0: [sr0] scsi3-mmc drive: 48x/48x writer dvd-ram
>> cd/rw xa/form2 cdda tray
>> [    4.159120] cdrom: Uniform CD-ROM driver Revision: 3.20
>> [    5.936017] systemd[1]: Starting Load Kernel Module drm...
>> [    5.957038] systemd[1]: modprobe@drm.service: Deactivated successfully.
>> [    5.957238] systemd[1]: Finished Load Kernel Module drm.
>> [    6.104901] sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver
>> [    6.122007] usbcore: registered new device driver apple-mfi-fastcharge
>> [    6.213866] input: HDA NVidia HDMI/DP,pcm=3 as
>> /devices/pci0000:00/0000:00:03.1/0000:06:00.1/sound/card0/input8
>> [    6.236581] AMD64 EDAC driver v3.5.0
>> [    6.259473] input: HDA NVidia HDMI/DP,pcm=7 as
>> /devices/pci0000:00/0000:00:03.1/0000:06:00.1/sound/card0/input9
>> [    6.259631] input: HDA NVidia HDMI/DP,pcm=8 as
>> /devices/pci0000:00/0000:00:03.1/0000:06:00.1/sound/card0/input10
>> [    6.260559] input: HDA NVidia HDMI/DP,pcm=9 as
>> /devices/pci0000:00/0000:00:03.1/0000:06:00.1/sound/card0/input11
>> [    6.260913] input: HDA NVidia HDMI/DP,pcm=10 as
>> /devices/pci0000:00/0000:00:03.1/0000:06:00.1/sound/card0/input12
>> [    6.485220] nouveau 0000:06:00.0: vgaarb: deactivate vga console
>> [    6.486484] nouveau 0000:06:00.0: NVIDIA GP108 (138000a1)
>> [    6.612994] nouveau 0000:06:00.0: bios: version 86.08.24.00.23
>> [    6.617303] nouveau 0000:06:00.0: pmu: firmware unavailable
>> [    6.621410] nouveau 0000:06:00.0: fb: 2048 MiB GDDR5
>> [    6.653892] nouveau 0000:06:00.0: DRM: VRAM: 2048 MiB
>> [    6.653895] nouveau 0000:06:00.0: DRM: GART: 536870912 MiB
>> [    6.653897] nouveau 0000:06:00.0: DRM: BIT table 'A' not found
>> [    6.653899] nouveau 0000:06:00.0: DRM: BIT table 'L' not found
>> [    6.653900] nouveau 0000:06:00.0: DRM: TMDS table version 2.0
>> [    6.653902] nouveau 0000:06:00.0: DRM: DCB version 4.1
>> [    6.653904] nouveau 0000:06:00.0: DRM: DCB outp 00: 01800346 04600010
>> [    6.653906] nouveau 0000:06:00.0: DRM: DCB outp 01: 01000342 00020010
>> [    6.653908] nouveau 0000:06:00.0: DRM: DCB outp 02: 01011352 00020020
>> [    6.653909] nouveau 0000:06:00.0: DRM: DCB conn 00: 00001046
>> [    6.653911] nouveau 0000:06:00.0: DRM: DCB conn 01: 00002161
>> [    6.654295] nouveau 0000:06:00.0: DRM: MM: using COPY for buffer copies
>> [    6.655460] snd_hda_intel 0000:06:00.1: bound 0000:06:00.0 (ops
>> nv50_audio_component_bind_ops [nouveau])
>> [    6.828018] nouveau 0000:06:00.0: DRM: allocated 3840x2160 fb:
>> 0x200000, bo 000000001a41f1fe
>> [    6.828086] fbcon: nouveau (fb0) is primary device
>> [    6.915486] nouveau 0000:06:00.0: [drm] fb0: nouveau frame buffer device
>> [    6.939244] [drm] Initialized nouveau 1.3.1 20120801 for 0000:06:00.0
>> on minor 0
>> [   11.338075] audit: type=1400 audit(1638634273.245:6):
>> apparmor="STATUS" operation="profile_load" profile="unconfined"
>> name="nvidia_modprobe" pid=1354 comm="apparmor_parser"
>> [   11.338078] audit: type=1400 audit(1638634273.245:7):
>> apparmor="STATUS" operation="profile_load" profile="unconfined"
>> name="nvidia_modprobe//kmod" pid=1354 comm="apparmor_parser"
>> [   11.479123] RTL8226B_RTL8221B 2.5Gbps PHY r8169-500:00: attached PHY
>> driver (mii_bus:phy_addr=r8169-500:00, irq=MAC)
>>
> 

      parent reply	other threads:[~2021-12-21 17:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <da142fb9-07d7-24fe-4533-0247b8d16cdd@sfritsch.de>
2021-12-06 13:19 ` Regression in 5.15 in nouveau Thorsten Leemhuis
2021-12-06 13:41   ` Christian König
2021-12-06 18:37   ` [Nouveau] " Dan Moulding
2021-12-07  9:52     ` Christian König
2021-12-07 17:32       ` Karol Herbst
2021-12-07 18:30         ` Daniel Vetter
2021-12-07 19:01       ` Dan Moulding
2021-12-07 19:22         ` Stefan Fritsch
2021-12-07 20:45           ` Dan Moulding
2021-12-08 17:43             ` Stefan Fritsch
2021-12-09 10:25             ` Christian König
2021-12-21 17:24   ` Thorsten Leemhuis [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=297f26ea-fff8-f2f4-6e27-35bbbb87456e@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).