<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"><div dir="ltr">I bisected today.</div><div dir="ltr"><br></div><div dir="ltr">git clone https://gitlab.freedesktop.org/drm/kernel a</div><div dir="ltr"><br></div><div dir="ltr">git bisect start</div><div dir="ltr"><br></div><div dir="ltr">git bisect good 2f29b5c231011b94007d2c8a6d793992f2275db1</div><div dir="ltr">(Good: video: screen_info: Relocate framebuffers behind PCI bridges)</div><div dir="ltr"><br></div><div dir="ltr">git bisect bad f62408efc8669b82541295a4611494c8c8c52684</div><div dir="ltr">(Bad: drm/xe/vf: Disable CSC support on VF)</div><div dir="ltr"><br></div><div dir="ltr">4d4c10f763d7808fbade28d83d237411603bca05 is the first bad commit</div><div dir="ltr">commit 4d4c10f763d7808fbade28d83d237411603bca05</div><div dir="ltr">Author: Mario Limonciello <mario.limonciello@amd.com></div><div dir="ltr">Date: Wed Apr 23 23:31:32 2025 -0500</div><div dir="ltr"><br></div><div dir="ltr"> PCI: Explicitly put devices into D0 when initializing</div><div dir="ltr"><br></div><div dir="ltr"> AMD BIOS team has root caused an issue that NVMe storage failed to come</div><div dir="ltr"> back from suspend to a lack of a call to _REG when NVMe device was probed.</div><div dir="ltr"><br></div><div dir="ltr"> 112a7f9c8edbf ("PCI/ACPI: Call _REG when transitioning D-states") added</div><div dir="ltr"> support for calling _REG when transitioning D-states, but this only works</div><div dir="ltr"> if the device actually "transitions" D-states.</div><div dir="ltr"><br></div><div dir="ltr"> 967577b062417 ("PCI/PM: Keep runtime PM enabled for unbound PCI devices")</div><div dir="ltr"> added support for runtime PM on PCI devices, but never actually</div><div dir="ltr"> 'explicitly' sets the device to D0.</div><div dir="ltr"><br></div><div dir="ltr"> To make sure that devices are in D0 and that platform methods such as</div><div dir="ltr"> _REG are called, explicitly set all devices into D0 during initialization.</div><div dir="ltr"><br></div><div dir="ltr"> Fixes: 967577b062417 ("PCI/PM: Keep runtime PM enabled for unbound PCI devices")</div><div dir="ltr"> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com></div><div dir="ltr"> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com></div><div dir="ltr"> Tested-by: Denis Benato <benato.denis96@gmail.com></div><div dir="ltr"> Tested-By: Yijun Shen <Yijun_Shen@Dell.com></div><div dir="ltr"> Tested-By: David Perry <david.perry@amd.com></div><div dir="ltr"> Reviewed-by: Rafael J. Wysocki <rafael@kernel.org></div><div dir="ltr"> Link: https://patch.msgid.link/20250424043232.1848107-1-superm1@kernel.org</div><div dir="ltr"><br></div><div dir="ltr"> drivers/pci/pci-driver.c | 6 ------</div><div dir="ltr"> drivers/pci/pci.c | 13 ++++++++++---</div><div dir="ltr"> drivers/pci/pci.h | 1 +</div><div dir="ltr"> 3 files changed, 11 insertions(+), 9 deletions(-)</div><div dir="ltr"><br></div><div dir="ltr">I bisected with a ATi Radeon 7000 / VE (-device ati-vga,model=rv100) :-)</div></div><div dir="ltr"><br><blockquote type="cite">On 04 August 2025 at 06:26 pm, mad skateman <madskateman@gmail.com> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div dir="auto">I am using the R580 chip which is the Radeon X1950 XT.<div dir="auto"><br></div><div dir="auto">The board i am using is a T1042 PowerPC based one with e5500 core.</div><div dir="auto"><br></div><div dir="auto">I also lost the ability to start Xorg and therefore just a blank screen.</div><div dir="auto"><br></div><div dir="auto">Dave</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">Op ma 4 aug 2025, 18:04 schreef Christian Zigotzky <<a href="mailto:chzigotzky@xenosoft.de">chzigotzky@xenosoft.de</a>>:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br> On 04 August 2025 at 04:42 pm, Alex Deucher wrote:<br> > On Sun, Aug 3, 2025 at 11:28 AM Christian Zigotzky<br> > <<a href="mailto:chzigotzky@xenosoft.de" target="_blank" rel="noreferrer">chzigotzky@xenosoft.de</a>> wrote:<br> >><br> >> Hello,<br> >><br> >> I have the same issue on another machine either. Blank screen during the<br> >> boot. The Radeon graphics framebuffer device doesn't work anymore.<br> >><br> >> Here is the modifed code from the DRM updates (drm-next-2025-07-30):<br> >><br> >> -<br> >> <a href="https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/drivers/gpu/drm/radeon/radeon_fbdev.c?id=260f6f4fda93c8485c8037865c941b42b9cba5d2" rel="noreferrer noreferrer" target="_blank">https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/drivers/gpu/drm/radeon/radeon_fbdev.c?id=260f6f4fda93c8485c8037865c941b42b9cba5d2</a><br> >> -<br> >> <a href="https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/drivers/gpu/drm/radeon/radeon_drv.c?id=260f6f4fda93c8485c8037865c941b42b9cba5d2" rel="noreferrer noreferrer" target="_blank">https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/drivers/gpu/drm/radeon/radeon_drv.c?id=260f6f4fda93c8485c8037865c941b42b9cba5d2</a><br> > <br> > This change just bumps the driver version it shouldn't affect the fbdev.<br> > <br> >> -<br> >> <a href="https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/drivers/gpu/drm/radeon/radeon_display.c?id=260f6f4fda93c8485c8037865c941b42b9cba5d2" rel="noreferrer noreferrer" target="_blank">https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/drivers/gpu/drm/radeon/radeon_display.c?id=260f6f4fda93c8485c8037865c941b42b9cba5d2</a><br> >> -<br> >> <a href="https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/drivers/gpu/drm/radeon/evergreen_cs.c?id=260f6f4fda93c8485c8037865c941b42b9cba5d2" rel="noreferrer noreferrer" target="_blank">https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/drivers/gpu/drm/radeon/evergreen_cs.c?id=260f6f4fda93c8485c8037865c941b42b9cba5d2</a><br> > <br> > This only affects acceleration, it should not affect fbdev.<br> > <br> > What chip are you using? Can you attach your full dmesg output? Can<br> > you bisect? This cultrit could be a core drm change.<br> > <br> > Alex<br> > <br> >><br> >> Do you have a patch for reverting these modifications? I would like to<br> >> revert these modifications for testing.<br> >><br> >> Thanks in advance,<br> >> Christian<br> >><br> >> On 03 August 2025 at 1:35 pm, Christian Zigotzky wrote:<br> >>> Hello,<br> >>><br> >>> Xorg doesn't work after the DRM updates drm-next-2025-07-30.<br> >>><br> >>> Error messages:<br> >>><br> >>> [dr:.radeon_fbdev_river_fbdev_proe] *ERROR* failed to initialize<br> >>> framebuffer -22<br> >>> radeon 0000:01:0.0: [drm] *ERRO* fbdev: Failedto setup emulaton (ret=-22)<br> >>> brd module loadedm<br> >>> lop: module loadd<br> >>> mpt3ss version 52.10.00.00 loaded<br> >>> nve nvme0: pci fuction 0002:04:0.0<br> >>> fsl-sata ffe20000.sata: SataFSL Platform/CS Driver init<br> >>> scs host0: sata_fs<br> >>> ta1: SATA max DMA/133 irq 68 pm-pol 0<br> >>> ;21;39mfsl-sat ffe221000.sata Sata FSL Platfrm/CSB Driver iit<br> >>> ata1: Signatue Update detectd @ 0 msecs<br> >>> scsihost1: sata_fsl[0m<br> >>> ta2: SATA max UMA/133 irq 69 lm-pol 0<br> >>> nvme nvm0: 4/0/0 defaul/read/poll queus<br> >>> nvme0n1: p1 p p3 p4 p5 p6 p7[0m<br> >>> drm:.radeon_fbdv_driver_fbdev_robe] *ERROR* filed to initialze<br> >>> framebuffer 22<br> >>> fsl_dpaa_mac fe4e6000.ethernt: of_get_mac_adress(/soc@ffe00000/<br> >>> fman@40000/ethernet@e6000 failed<br> >>> radeon 000:01:00.0: [dr] *ERROR* fbdev Failed to setu emulation (ret-22)<br> >>> fsl_dpaa_ma ffe4e6000.ethenet: FMan MEMAC[0m<br> >>> sl_dpaa_mac ffee6000.ethernet:Using random MA address: 0e<br> >>><br> >>> Could you please check the latest DRM updates?<br> >>><br> >>> Thanks,<br> >>> Christian<br> >>><br> >><br> <br> Hello Alex,<br> <br> Thanks for your answer.<br> <br> I use a BARTS chip (Radeon HD6870). I would like to bisect but I don't <br> have time for it currently. Sorry<br> <br> There are some other user reports:<br> <br> - <a href="https://forum.hyperion-entertainment.com/viewtopic.php?p=60606#p60606" rel="noreferrer noreferrer" target="_blank">https://forum.hyperion-entertainment.com/viewtopic.php?p=60606#p60606</a><br> - <a href="https://forum.hyperion-entertainment.com/viewtopic.php?p=60595#p60595" rel="noreferrer noreferrer" target="_blank">https://forum.hyperion-entertainment.com/viewtopic.php?p=60595#p60595</a><br> <br> They use other Radeon graphics chips.<br> <br> Bug report: <a href="https://github.com/chzigotzky/kernels/issues/15" rel="noreferrer noreferrer" target="_blank">https://github.com/chzigotzky/kernels/issues/15</a><br> <br> What do you think about the following commit?<br> <br> Link: <br> <a href="https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0e7d5874fb6b80c44be3cfbcf1cf356e81d91232" rel="noreferrer noreferrer" target="_blank">https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0e7d5874fb6b80c44be3cfbcf1cf356e81d91232</a><br> <br> @Hypex<br> Could you please attach your full dmesg output?<br> <br> Thanks,<br> Christian<br> </blockquote></div> </div></blockquote></body></html>