Re: drm/msm: VT console DisplayPort regression in 6.8-rc1
[send with a reduced set of recipients, we all get enough mail already] On 27.02.24 13:40, Johan Hovold wrote: > > Since 6.8-rc1 the VT console is no longer mirrored on an external > display on coldplug or hotplug on the Lenovo ThinkPad X13s. > Thx for the report! > I've previously reported this here: > > https://gitlab.freedesktop.org/drm/msm/-/issues/50 Then let's tell regzbot about is as well, in case the ticket comes back to life now: #regzbot duplicate: https://gitlab.freedesktop.org/drm/msm/-/issues/50 Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) -- Everything you wanna know about Linux kernel regression tracking: https://linux-regtracking.leemhuis.info/about/#tldr If I did something stupid, please tell me, as explained on that page.
Re: Bug#1061449: linux-image-6.7-amd64: a boot message from amdgpu
On 27.01.24 14:14, Salvatore Bonaccorso wrote:
>
> In Debian (https://bugs.debian.org/1061449) we got the following
> quotred report:
>
> On Wed, Jan 24, 2024 at 07:38:16PM +0100, Patrice Duroux wrote:
>> Package: src:linux
>> Version: 6.7.1-1~exp1
>> Severity: normal
>>
>> Giving a try to 6.7, here is a message extracted from dmesg:
>>
>> [4.177226] [ cut here ]
>> [4.177227] WARNING: CPU: 6 PID: 248 at
>> drivers/gpu/drm/amd/amdgpu/../display/dc/link/link_factory.c:387
>> construct_phy+0xb26/0xd60 [amdgpu]
>
> Analysis showed that this appears to be a regression from b17ef04bf3a4
> ("drm/amd/display: Pass pwrseq inst for backlight and ABM"). Does that
> ring some bells?
>
> See: https://bugs.debian.org/1061449#27
>
> #regzbot introduced: b17ef04bf3a4
> #regzbot link: https://bugs.debian.org/1061449
> #regzbot title: Regression by b17ef04bf3a4 ("drm/amd/display: Pass pwrseq
> inst for backlight and ABM")
#regzbot monitor:
https://lore.kernel.org/amd-gfx/20240214184006.1356137-8-rodrigo.sique...@amd.com/
#regzbot fix: drm/amd/display: Only allow dig mapping to pwrseq in new asic
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
Re: [REGRESSION] rx7600 stopped working after "1cfb4d612127 drm/amdgpu: put MQDs in VRAM"
[TLDR: This mail in primarily relevant for Linux kernel regression tracking. See link in footer if these mails annoy you.] On 26.10.23 19:33, Alexey Klimov wrote: > #regzbot introduced: 1cfb4d612127 > #regzbot title: rx7600 stopped working after "1cfb4d612127 drm/amdgpu: put > MQDs in VRAM" > > Hi all, > > I've been playing with RX7600 and it was observed that amdgpu stopped working > between kernel 6.2 and 6.5. > Then I narrowed it down to 6.4 <-> 6.5-rc1 and finally bisect pointed at > 1cfb4d6121276a829aa94d0e32a7f5e1830ebc21 > And I manually checked if it boots/works on the previous commit and the > mentioned one. #regzbot fix: ba0fb4b48c19a #regzbot ignore-activity Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) -- Everything you wanna know about Linux kernel regression tracking: https://linux-regtracking.leemhuis.info/about/#tldr That page also explains what to do if mails like this annoy you.
Re: mainline build failure due to 7966f319c66d ("drm/amd/display: Introduce DML2")
[TLDR: This mail in primarily relevant for Linux kernel regression tracking. See link in footer if these mails annoy you.] On 04.11.23 10:42, Sudip Mukherjee wrote: > On Thu, 2 Nov 2023 at 22:53, Alex Deucher wrote: >> On Thu, Nov 2, 2023 at 1:07 PM Sudip Mukherjee >> wrote: >>> On Thu, 2 Nov 2023 at 16:52, Alex Deucher wrote: On Thu, Nov 2, 2023 at 5:32 AM Sudip Mukherjee (Codethink) wrote: >> >> Should be fixed with Nathan's patch: >> https://patchwork.freedesktop.org/patch/565675/ > > Yes, it does. Thanks. > > Tested-by: Sudip Mukherjee #regzbot fix: 6740ec97bcdbe9 #regzbot ignore-activity Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) -- Everything you wanna know about Linux kernel regression tracking: https://linux-regtracking.leemhuis.info/about/#tldr That page also explains what to do if mails like this annoy you.
Re: [Nouveau] Fwd: System (Xeon Nvidia) hangs at boot terminal after kernel 6.4.7
[TLDR: This mail in primarily relevant for Linux kernel regression tracking. See link in footer if these mails annoy you.] On 10.08.23 06:19, Thorsten Leemhuis wrote: > On 10.08.23 05:03, Bagas Sanjaya wrote: >> >> I notice a regression report on Bugzilla [1]. Quoting from it: >> >> [...] >> [1]: https://bugzilla.kernel.org/show_bug.cgi?id=217776 #regzbot link: https://gitlab.freedesktop.org/drm/nouveau/-/issues/255 #regzbot fix: 6eb4a83e612af65bab8492957cba #regzbot ignore-activity Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) -- Everything you wanna know about Linux kernel regression tracking: https://linux-regtracking.leemhuis.info/about/#tldr That page also explains what to do if mails like this annoy you.
Re: [REGRESSION] Panic in gen8_ggtt_insert_entries() with v6.5
On 19.09.23 16:08, Bagas Sanjaya wrote: > On Sat, Sep 02, 2023 at 06:14:12PM +0200, Oleksandr Natalenko wrote: >> >> Since v6.5 kernel the following HW: >> >> * Lenovo T460s laptop with Skylake GT2 [HD Graphics 520] (rev 07) >> * Lenovo T490s laptop with WhiskeyLake-U GT2 [UHD Graphics 620] (rev 02) > > #regzbot ^introduced: 0b62af28f249b9 > #regzbot title: gen8_ggtt_insert_entries() panic on Lenovo T14s (Tiger Lake) > due to folio_batch() on shmem_sg_free_table() > #regzbot link: https://gitlab.freedesktop.org/drm/intel/-/issues/9256 #regzbot fix: i915: Limit the length of an sg list to the requested length #regzbot ignore-activity Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) -- Everything you wanna know about Linux kernel regression tracking: https://linux-regtracking.leemhuis.info/about/#tldr That page also explains what to do if mails like this annoy you.
Re: mainline build failure due to 501126083855 ("fbdev/g364fb: Use fbdev I/O helpers")
[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]
On 31.08.23 20:48, Sudip Mukherjee (Codethink) wrote:
> Hi All,
>
> The latest mainline kernel branch fails to build mips jazz_defconfig with
> the error:
>
> drivers/video/fbdev/g364fb.c:115:9: error: 'FB_DEFAULT_IOMEM_HELPERS'
> undeclared here (not in a function); did you mean 'FB_DEFAULT_IOMEM_OPS'?
> 115 | FB_DEFAULT_IOMEM_HELPERS,
> | ^~~~
> | FB_DEFAULT_IOMEM_OPS
>
>
> git bisect pointed to 501126083855 ("fbdev/g364fb: Use fbdev I/O helpers").
>
> Reverting the commit has fixed the build failure.
>
> I will be happy to test any patch or provide any extra log if needed.
>
> #regzbot introduced: 5011260838551cefbf23d60b48c3243b6d5530a2
>
#regzbot fix: 8df0f84c3bb921f5aa1036223dd932bbc7df6d
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
Re: nouveau bug in linux/6.1.38-2
[TLDR: This mail in primarily relevant for Linux kernel regression tracking. See link in footer if these mails annoy you.] On 04.08.23 14:02, Thorsten Leemhuis wrote: > On 02.08.23 23:28, Olaf Skibbe wrote: >> Dear Maintainers, >> >> Hereby I would like to report an apparent bug in the nouveau driver in >> linux/6.1.38-2. > > Thx for your report. Maybe your problem is caused by a incomplete > backport. I Cced the maintainers for the drivers (and the regressions > and the stable list), maybe one of them has an idea, as they know the > driver. #regzbot fix: 98e470dc73a9b3539e5a7a3c72f6b7c01c98 #regzbot ignore-activity Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) -- Everything you wanna know about Linux kernel regression tracking: https://linux-regtracking.leemhuis.info/about/#tldr That page also explains what to do if mails like this annoy you.
Re: [PATCH v3 11/13] drm/fb-helper: Fix single-probe color-format selection
[TLDR: This mail in primarily relevant for Linux regression tracking. A change or fix related to the regression discussed in this thread was posted or applied, but it did not use a Link: tag to point to the report, as Linus and the documentation call for. Things happen, no worries -- but now the regression tracking bot needs to be told manually about the fix. See link in footer if these mails annoy you.] On 14.05.23 14:10, Linux regression tracking #adding (Thorsten Leemhuis) wrote: > On 12.05.23 15:20, Linus Walleij wrote: >> Sorry for late regression detection but this patch regresses >> the Integrator AB IMPD-1 graphics, I bisected down to this >> patch. > > #regzbot ^introduced 37c90d589dc > #regzbot title drm/fb-helper: downscaling apparently stopped to work > with pl110_impd1 > #regzbot ignore-activity #regzbot monitor: https://lore.kernel.org/all/20230515092943.1401558-1-linus.wall...@linaro.org/ #regzbot fix: drm/pl111: Fix FB depth on IMPD-1 framebuffer #regzbot ignore-activity Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) -- Everything you wanna know about Linux kernel regression tracking: https://linux-regtracking.leemhuis.info/about/#tldr That page also explains what to do if mails like this annoy you.
Re: [PATCH v3 01/13] firmware/sysfb: Fix EFI/VESA format selection
[TLDR: This mail in primarily relevant for Linux regression tracking. A change or fix related to the regression discussed in this thread was posted or applied, but it did not use a Link: tag to point to the report, as Linus and the documentation call for. Things happen, no worries -- but now the regression tracking bot needs to be told manually about the fix. See link in footer if these mails annoy you.] On 08.04.23 13:26, Linux regression tracking #adding (Thorsten Leemhuis) wrote: > > On 06.04.23 17:45, Pierre Asselin wrote: >> Thomas Zimmermann wrote: >> [...] >> Starting at linux-6.3-rc1 my simplefb picks the wrong mode and garbles >> the display This is on a 16-year old i686 laptop. I can post lshw or >> dmidecode output if it helps. >> [...] >> I bisected it to f35cd3fa77293c2cd03e94b6a6151e1a7d9309cf >> firmware/sysfb: Fix EFI/VESA format selection > > Thanks for the report. To be sure the issue doesn't fall through the > cracks unnoticed, I'm adding it to regzbot, the Linux kernel regression > tracking bot: > > #regzbot ^introduced f35cd3fa77293c2cd03e > #regzbot title firmware/sysfb: wrong mode and display garbled on 16-year > old i686 laptop > #regzbot ignore-activity #regzbot monitor: https://lore.kernel.org/lkml/20230412150225.3757223-1-javi...@redhat.com/ #regzbot ignore-activity Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) -- Everything you wanna know about Linux kernel regression tracking: https://linux-regtracking.leemhuis.info/about/#tldr That page also explains what to do if mails like this annoy you.
Re: linux-6.2-rc4+ hangs on poweroff/reboot: Bisected
On 13.02.23 10:14, Chris Clayton wrote: > On 13/02/2023 02:57, Dave Airlie wrote: >> On Sun, 12 Feb 2023 at 00:43, Chris Clayton wrote: >>> >>> >>> >>> On 10/02/2023 19:33, Linux regression tracking (Thorsten Leemhuis) wrote: On 10.02.23 20:01, Karol Herbst wrote: > On Fri, Feb 10, 2023 at 7:35 PM Linux regression tracking (Thorsten > Leemhuis) wrote: >> >> On 08.02.23 09:48, Chris Clayton wrote: >>> >>> I'm assuming that we are not going to see a fix for this regression >>> before 6.2 is released. >> >> Yeah, looks like it. That's unfortunate, but happens. But there is still >> time to fix it and there is one thing I wonder: >> >> Did any of the nouveau developers look at the netconsole captures Chris >> posted more than a week ago to check if they somehow help to track down >> the root of this problem? > > I did now and I can't spot anything. I think at this point it would > make sense to dump the active tasks/threads via sqsrq keys to see if > any is in a weird state preventing the machine from shutting down. Many thx for looking into it! >>> >>> Yes, thanks Karol. >>> >>> Attached is the output from dmesg when this block of code: >>> >>> /bin/mount /dev/sda7 /mnt/sda7 >>> /bin/mountpoint /proc || /bin/mount /proc >>> /bin/dmesg -w > /mnt/sda7/sysrq.dmesg.log & >>> /bin/echo t > /proc/sysrq-trigger >>> /bin/sleep 1 >>> /bin/sync >>> /bin/sleep 1 >>> kill $(pidof dmesg) >>> /bin/umount /mnt/sda7 >>> >>> is executed immediately before /sbin/reboot is called as the final step of >>> rebooting my system. >>> >>> I hope this is what you were looking for, but if not, please let me know >>> what you need > > Thanks Dave. [...] FWIW, in case anyone strands here in the archives: the msg was truncated. The full post can be found in a new thread: https://lore.kernel.org/lkml/e0b80506-b3cf-315b-4327-1b988d860...@googlemail.com/ Sadly it seems the info "With runpm=0, both reboot and poweroff work on my laptop." didn't bring us much further to a solution. :-/ I don't really like it, but for regression tracking I'm now putting this on the back-burner, as a fix is not in sight. #regzbot monitor: https://lore.kernel.org/lkml/e0b80506-b3cf-315b-4327-1b988d860...@googlemail.com/ #regzbot backburner: hard to debug and apparently rare #regzbot ignore-activity Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) -- Everything you wanna know about Linux kernel regression tracking: https://linux-regtracking.leemhuis.info/about/#tldr That page also explains what to do if mails like this annoy you. #regzbot ignore-activity
