From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 0B87CEFCD9F for ; Tue, 10 Mar 2026 09:03:29 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 6771310E6A0; Tue, 10 Mar 2026 09:03:28 +0000 (UTC) Authentication-Results: gabe.freedesktop.org; dkim=pass (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.b="ZTccsKyW"; dkim-atps=neutral Received: from tor.source.kernel.org (tor.source.kernel.org [172.105.4.254]) by gabe.freedesktop.org (Postfix) with ESMTPS id E72F810E6A0 for ; Tue, 10 Mar 2026 09:03:27 +0000 (UTC) Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by tor.source.kernel.org (Postfix) with ESMTP id 3A6D960054 for ; Tue, 10 Mar 2026 09:03:27 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPS id A4D37C19423 for ; Tue, 10 Mar 2026 09:03:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1773133406; bh=9S9/pHuNhzfs9MSgVuzRSW33i4D3wx8NmCW6lgMmU7k=; h=From:To:Subject:Date:From; b=ZTccsKyWBkUNQjBlR2MLAa5wieQZlXn1iB9oLdvbPmJMjgXY3LlxvrH7uk+nqSBVm Q0m17KYXLgcw2GmFAsy+dhkjVR287jYWG2RH4cOmpx2rf9mpweDY+xZWAMqf7u9G18 Mub3ItnFLRTUE33Yihe52uXxaXUQku/e74EldZ5kUMMfEDg5SMtz4HckHkgmVrf/OM JrDYLREEmTzzIBoMAU1fFOAXsLf9anBfLRAFBla+QIKcnuIBvTJO1+vuiGudw4r1jl o97tBxx1zCFl62sf8a9qeBjk8yq7qJYp5YDK+jd88avG4ees03hV0fM3DA8yISgo36 01IgrXYKgeGeQ== Received: by aws-us-west-2-korg-bugzilla-1.web.codeaurora.org (Postfix, from userid 48) id 9AFB3C41612; Tue, 10 Mar 2026 09:03:26 +0000 (UTC) From: bugzilla-daemon@kernel.org To: dri-devel@lists.freedesktop.org Subject: [Bug 221202] New: DisplayPort monitor (Samsung Odyssey G65B) sometimes wakes with invalid EDID and only exposes 640x480 until monitor power-cycle (NVIDIA + Wayland) Date: Tue, 10 Mar 2026 09:03:26 +0000 X-Bugzilla-Reason: None X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: AssignedTo drivers_video-dri@kernel-bugs.osdl.org X-Bugzilla-Product: Drivers X-Bugzilla-Component: Video(DRI - non Intel) X-Bugzilla-Version: 2.5 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: uitham@gmail.com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: drivers_video-dri@kernel-bugs.osdl.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cf_regression attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugzilla.kernel.org/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: dri-devel@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Direct Rendering Infrastructure - Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" https://bugzilla.kernel.org/show_bug.cgi?id=3D221202 Bug ID: 221202 Summary: DisplayPort monitor (Samsung Odyssey G65B) sometimes wakes with invalid EDID and only exposes 640x480 until monitor power-cycle (NVIDIA + Wayland) Product: Drivers Version: 2.5 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P3 Component: Video(DRI - non Intel) Assignee: drivers_video-dri@kernel-bugs.osdl.org Reporter: uitham@gmail.com Regression: No Created attachment 309601 --> https://bugzilla.kernel.org/attachment.cgi?id=3D309601&action=3Dedit Archive containing .txt outputs of commands Kernel: Linux 6.18.9-arch1-2 GPU: NVIDIA RTX 5080 Driver: nvidia-open-dkms 590.48.01-6 (nvidia-drm.modeset=3D1) Desktop: KDE Plasma (Wayland) Connection: DisplayPort Monitor: Samsung Odyssey G65B Problem: After the system or monitor wakes from sleep, the Odyssey G65B sometimes appears connected but exposes only a single fallback mode (640x480). The monitor remains detected but its EDID appears unreadable or corrupted until= the monitor is power-cycled. Power-cycling the monitor immediately restores the correct EDID and full mo= de list without rebooting the system or reconnecting cables. Observed behavior: kscreen-doctor shows DP-3 connected but only a single mode: Output: DP-3 Modes: 640x480@59.94* xrandr --verbose shows only fallback modes: DP-3 connected 640x480 640x480 *current +preferred 320x240 640x400 320x200 640x350 Kernel / userspace logs show EDID read failures: Checking EDID failed after 2 tries Unable to read EDID for /dev/i2c-20 Failed to find connector name for /dev/i2c-20 KWin also reports invalid EDID colorimetry: EDID colorimetry xy(...) is invalid EDID comparison: When the monitor is working normally, the EDID decodes correctly and identi= fies the display as: Monitor name: Odyssey G65B The EDID includes valid CTA extension blocks and detailed timings including: - 2560x1440 @ ~60 Hz - 1920x1080 @ 120 Hz - HDR metadata When the problem occurs, the monitor appears to return an invalid or trunca= ted EDID and only legacy fallback modes are exposed. Reproduction pattern (intermittent): 1. System runs normally with monitor connected over DisplayPort 2. Monitor enters sleep 3. Wake the monitor/system 4. Occasionally the display returns with only 640x480 available 5. Power-cycle the monitor 6. Correct EDID and full mode list return immediately Notes: The connector remains detected during the failure (DP-3 shows as connected), but EDID reads fail on the corresponding I=C2=B2C bus (/dev/i2c-20). This s= uggests a wake/reprobe issue in the DisplayPort EDID detection path rather than a configuration issue in user space. This system uses the NVIDIA open kernel modules (nvidia-open-dkms), which provide the nvidia-drm DRM/KMS driver. The issue may therefore be within the nvidia-drm driver stack. I am reporting it here in case the problem involves generic DRM / DisplayPort EDID detection or wake-up handling. Attachments: - kscreen-doctor output (failed state) - xrandr --verbose (failed state) - journalctl EDID errors - EDID decode (failed vs working state) --=20 You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.=