Bug 2250996 - HiDPI, 120hz monitors cause GNOME to dump core on RPi 4b SBC
Summary: HiDPI, 120hz monitors cause GNOME to dump core on RPi 4b SBC
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 39
Hardware: aarch64
OS: Linux
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL: https://discussion.fedoraproject.org/...
Depends On:
TreeView+ depends on / blocked
Reported: 2023-11-22 07:36 UTC by Benny Powers
Modified: 2023-11-22 07:36 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Last Closed:
Type: ---

Attachments (Terms of Use)
kernel log (58.33 KB, text/plain)
2023-11-22 07:36 UTC, Benny Powers
no flags Details

Description Benny Powers 2023-11-22 07:36:14 UTC
1. Please describe the problem:

Booting the "Raspberry Pi 4b" single board computer with a "UPERFECT 2k 120hz" HDMI monitor attached, GNOME dumps core when logging in from GDM. More elaboration in the linked fedora discussion. This issue is not present using the hardware manufacturer's in-house operating system. It may be that patches which address this problem, made by the hardware manufacturer have yet to be applied to the upstream kernel, as discussed in this issue: https://github.com/raspberrypi/linux/issues/4575

2. What is the Version-Release number of the kernel:


3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :


4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

1. plug the monitor in to the SBC's 1st HDMI port
2. plug in power
3. set the system tree to ACPI+DeviceTree in firmware settings
4. boot the OS
5. log in at GDM prompt

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:

I don't know

6. Are you running any modules that not shipped with directly Fedora's kernel?:


7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

Reproducible: Always

Comment 1 Benny Powers 2023-11-22 07:36:55 UTC
Created attachment 2000849 [details]
kernel log

Note You need to log in before you can comment on or make changes to this bug.