I upgraded to kernel version 6.16.7, but the same issue still persists. When will this problem be fixed, or where should I report this bug?

Have you given the 6.17 kernels a try? https://koji.fedoraproject.org/koji/buildinfo?buildID=2827240

(In reply to Justin M. Forbes from comment #2)
> Have you given the 6.17 kernels a try?
> https://koji.fedoraproject.org/koji/buildinfo?buildID=2827240

I tried kernel version 6.17 from the link you provided, and then 6.16.8, but I'm getting the same error. I've even tried different distributions and I'm still getting the same error. What can I do about this?

I tried the 6.16.9 and 6.17 kernels, but I keep getting the same error. How can this error be fixed? Is there light at the end of the tunnel?

inxi -Fzxx
System:
  Kernel: 6.14.0-63.fc42.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 15.0.1
  Desktop: GNOME v: 48.4 tk: GTK v: 3.24.49 wm: gnome-shell dm: GDM
    Distro: Fedora Linux 42 (Workstation Edition)
Machine:
  Type: Laptop System: GAME GARAJ product: SLAYER 5XL v: REV:1.0
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: GAME GARAJ model: SLAYER 5XL v: REV:1.0 serial: <superuser required>
    part-nu: 140 UEFI: American Megatrends LLC. v: E17S3IE2.10B date: 05/12/2025
Battery:
  ID-1: BAT1 charge: 83.1 Wh (95%) condition: 87.4/87.4 Wh (100%) volts: 17.18
    min: 15.4 model: MSI BIF0_9 serial: N/A charging: status: not charging
    cycles: N/A
CPU:
  Info: 24-core model: Intel Core Ultra 9 275HX bits: 64 type: MCP
    arch: Arrow Lake rev: 2 cache: L1: 2.4 MiB L2: 40 MiB L3: 36 MiB
  Speed (MHz): avg: 800 min/max: 800/5400:5300:4700:6500 cores: 1: 800
    2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 800
    12: 800 13: 800 14: 800 15: 800 16: 800 17: 800 18: 800 19: 800 20: 800
    21: 800 22: 800 23: 800 24: 800 bogomips: 147456
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Arrow Lake-S [Intel Graphics] vendor: Micro-Star MSI
    driver: i915 v: kernel arch: Xe2-LPG ports: active: eDP-1 empty: none
    bus-ID: 00:02.0 chip-ID: 8086:7d67
  Device-2: NVIDIA GB205M [GeForce RTX 5070 Ti Mobile]
    vendor: Micro-Star MSI driver: nvidia v: 580.82.09 arch: Lovelace pcie:
    speed: 32 GT/s lanes: 8 ports: active: none empty: DP-1, DP-2, HDMI-A-1,
    eDP-2 bus-ID: 01:00.0 chip-ID: 10de:2f18
  Device-3: Bison FHD Camera driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 bus-ID: 3-4:2 chip-ID: 5986:1193
  Display: wayland server: Xwayland v: 24.1.8 compositor: gnome-shell
    driver: X: loaded: nvidia gpu: i915 display-ID: 0
  Monitor-1: eDP-1 model: AU Optronics 0x84a6 res: 2560x1600 dpi: 178
    diag: 431mm (17")
  API: OpenGL v: 4.6 vendor: intel mesa v: 25.1.9 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: Mesa Intel Graphics (ARL) device-ID: 8086:7d67
    display-ID: :0.0
  API: Vulkan v: 1.4.313 surfaces: N/A device: 0 type: integrated-gpu
    driver: mesa intel device-ID: 8086:7d67 device: 1 type: discrete-gpu
    driver: nvidia device-ID: 10de:2f18 device: 2 type: cpu
    driver: mesa llvmpipe device-ID: 10005:0000
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
  Info: Tools: api: clinfo, glxinfo, vulkaninfo gpu: gputop, intel_gpu_top,
    lsgpu, nvidia-settings, nvidia-smi x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
  Device-1: NVIDIA driver: snd_hda_intel v: kernel pcie: speed: 32 GT/s
    lanes: 8 bus-ID: 01:00.1 chip-ID: 10de:2f80
  Device-2: Intel vendor: Micro-Star MSI driver: sof-audio-pci-intel-mtl
    bus-ID: 80:1f.3 chip-ID: 8086:7f50
  API: ALSA v: k6.14.0-63.fc42.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.4.8 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
Network:
  Device-1: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169
    v: kernel pcie: speed: 5 GT/s lanes: 1 port: 3000 bus-ID: 83:00.0
    chip-ID: 10ec:8125
  IF: enp131s0 state: down mac: <filter>
  Device-2: Intel Wi-Fi 7 AX1775 /AX1790 /BE20 /BE401/BE1750 2x2
    vendor: Rivet Networks driver: iwlwifi v: kernel pcie: speed: 16 GT/s
    lanes: 1 bus-ID: 84:00.0 chip-ID: 8086:272b
  IF: wlp132s0f0 state: down mac: <filter>
  Device-3: Ralink MT7601U Wireless Adapter driver: mt7601u type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-8:4 chip-ID: 148f:7601
  IF: wlp128s20f0u8 state: up mac: <filter>
  IF-ID-1: lxdbr0 state: up speed: 10000 Mbps duplex: unknown mac: <filter>
  IF-ID-2: vethc4346b47 state: up speed: 10000 Mbps duplex: full
    mac: <filter>
Bluetooth:
  Device-1: Intel BE200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 bus-ID: 3-14:6 chip-ID: 8087:0036
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.4
    lmp-v: 13
Drives:
  Local Storage: total: 1.82 TiB used: 57.97 GiB (3.1%)
  ID-1: /dev/nvme0n1 vendor: Kingston model: SNV3S2000G size: 1.82 TiB
    speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 34.9 C
Partition:
  ID-1: / size: 1.82 TiB used: 57.62 GiB (3.1%) fs: btrfs dev: /dev/nvme0n1p3
  ID-2: /boot size: 973.4 MiB used: 342.3 MiB (35.2%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 598.8 MiB used: 19.3 MiB (3.2%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 1.82 TiB used: 57.62 GiB (3.1%) fs: btrfs
    dev: /dev/nvme0n1p3
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 45.2 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 64 GiB available: 62.2 GiB used: 5.28 GiB (8.5%)
  Processes: 545 Power: uptime: 53m wakeups: 0 Init: systemd v: 257
    target: graphical (5) default: graphical
  Packages: 71 pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 57
    pm: snap pkgs: 14 Compilers: clang: 20.1.8 alt: 15 gcc: 15.2.1 Shell: Bash
    v: 5.2.37 running-in: ptyxis-agent inxi: 3.3.39

Come on guys, let’s not sleep, let’s get up and work, and finally fix this error already, if you don’t mind. The error has gotten so old that it’s almost going to become an antique and extremely valuable—I might even have to sell it to an antique dealer :) Just to remind you, our error is: kernel: i915 0000:00:02.0: [drm] ERROR [CRTC:88:pipe A] DSB 0 poll error

When I tried to boot my notebook using a Fedora Live USB, the screen showed the following error:
[0.860432] dracut-cmdline[489]: //lib/dracut/hooks/cmdline/29-parse-livenet.sh: line 6: get_url_handler: command not found
When I tested the same Live USB on my older notebook with an AMD processor, Fedora 43 Beta booted and worked without any issues.

the same issue persists with the 6.17.4-200.fc42.x86_64 kernel and header versions; I also tested it on Ubuntu 25.10, and it shows the same problem. On Ubuntu in particular, the system startup sound plays, but there’s no display — it gets stuck on the splash screen. Fedora 43 beta live USB doesn’t boot at all and throws an error. When I plug the same USB drives into my older notebook, they boot perfectly fine, so the USBs themselves are not the issue. In short, the same error continues to occur — I wanted to bring this to your attention.

When I connect my notebook to a TV via HDMI, the display works fine there, but on the notebook’s own monitor, the backlight is on yet the screen stays black with no image. The kernel version is 6.17, and my monitor specifications are as follows: 



sudo hwinfo --monitor

37: None 00.0: 10002 LCD Monitor                                
  [Created at monitor.125]
  Unique ID: rdCR.EYu2Y2EPnt0
  Parent ID: _Znp.5nkn8U25YC6
  Hardware Class: monitor
  Model: "B170QAN01.2 LCD Monitor"
  Vendor: AUO "B170QAN01.2"
  Device: eisa 0x84a6 
  Serial ID: "0"
  Resolution: 2560x1600@60Hz
  Size: 366x228 mm
  Year of Manufacture: 2022
  Week of Manufacture: 23
  Detailed Timings #0:
     Resolution: 2560x1600
     Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync
       Vertical: 1600 1610 1615 1640 (+10 +15 +40) -vsync
    Frequencies: 267.65 MHz, 98.40 kHz, 60.00 Hz
  Driver Info #0:
    Max. Resolution: 2560x1600
    Vert. Sync Range: 60-240 Hz
    Hor. Sync Range: 139-139 kHz
    Bandwidth: 267 MHz
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #34 (VGA compatible controller)

Created attachment 2115019 [details]
Kernel logs

I'm also affected by this bug, it seems. I've got a Dell Pro 13 Premium (PB13250) running Fedora 43 with Kernel 6.17.8. External monitors work without issue, as the OP said. Additionally, if you let the system boot with the frozen screen, and then suspend and wake up the laptop (by either closing the lid, or pressing the power button), the built-in display starts working again and you can log in and use the laptop without issue (until the next reboot, of course).

(In reply to Anton Gonzalez from comment #10)
> Created attachment 2115019 [details]
> Kernel logs
> 
> I'm also affected by this bug, it seems. I've got a Dell Pro 13 Premium
> (PB13250) running Fedora 43 with Kernel 6.17.8. External monitors work
> without issue, as the OP said. Additionally, if you let the system boot with
> the frozen screen, and then suspend and wake up the laptop (by either
> closing the lid, or pressing the power button), the built-in display starts
> working again and you can log in and use the laptop without issue (until the
> next reboot, of course).

When I suspend and resume, the backlight of the built-in monitor also turns off and the screen becomes completely dark.

The problem was solved when I installed the Linux kernel version 6.18.0-65.

This message is a reminder that Fedora Linux 42 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '42'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 42 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Fedora Linux 42 entered end-of-life (EOL) status on 2026-05-27.

Fedora Linux 42 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.