From nobody Mon Nov 25 15:05:21 2024 X-Original-To: bugs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Xxpss5RPFz5dkrk for ; Mon, 25 Nov 2024 15:05:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Xxpss3Jd1z41g5 for ; Mon, 25 Nov 2024 15:05:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1732547121; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=g1iZNwK3NF1bg/EQoO0XVa13xchSQ1z8s6QpAIIE4Hs=; b=CaG+/YkFQ4zzPDn7+iYeo9JgPx1UIV4fPHZpF6M6VDtLIqhgpkMzdrR86v8TJkWO9OoC1i rpvwsGa4hCJb1BPU1wxOcdGa8Q4Ojdm8yqOgUNtkTSuzJGdf+TyE955YZz4ZMQBXXw6o89 /ZeRu+FECpzWi/CdgdvThqks+CJt4gf408kWabF5tGPL9ysKPzCbKvhOCv6rC2vH6//pZ3 axs84g1CTdchtfOoeF8TYmUxC9m40Lt6JXKGgKaABJcSWlTR43vD1rzYWEhnNLNCaLYkVI t1z1iN3H7a8awTT7+EwrnkkS4379bR8SdCe7SKpabBxLsF/BZtEhaApAAoYXxQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1732547121; a=rsa-sha256; cv=none; b=BxuxjhB1q9wllj13gDIw4yW/qdGW1Ak/tpVQED8K2Bm0F5mrZ3UzBtEQh6aMONk1ti8u1o PCQCwpz6mK1+6hNOI28S5LhhBr6FsPz1weyWKeGUCeq76jen9Mct5WdL91E3yS16w9hPy4 l2SXxlYwCLLM0eHhiMamMR1uLRLg6QjUW1EmaPcDte3cCC7IekJuPC3fBBm0C3imNNTSkX fmtu8wXHLsfJP/lX30WjD8RIdAuSbXUtMKL0wpg+K4flJI4GajGW8bjiNnrB8KalLvRe5d xlY2lh1owwGLZmdN6ycMIaV3lg0/vK082MCXr82KqWMZiwrnynVw2PUUHQd3sQ== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4Xxpss2nqrzkV9 for ; Mon, 25 Nov 2024 15:05:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 4APF5LkG039343 for ; Mon, 25 Nov 2024 15:05:21 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 4APF5LbE039342 for bugs@FreeBSD.org; Mon, 25 Nov 2024 15:05:21 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 282964] efifb does not reactivate the screen after resuming from S3 Date: Mon, 25 Nov 2024 15:05:21 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 15.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: keivan@motavalli.me X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.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 Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D282964 Bug ID: 282964 Summary: efifb does not reactivate the screen after resuming from S3 Product: Base System Version: 15.0-CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: keivan@motavalli.me Hello, I'm trying to troubleshoot some acpi issues on systems I own. I noticed that all of them (a 7th gen i9 with an rtx 3060 gpu and no onboard graphics, a laptop running an 6th gen i7 cpu with onboard graphics, a ryzen= 3 desktop with only onboard graphics, a 12th gen i5 laptop with onboard graph= ics and a secondary nvidia gpu not wired to the screen) present the same proble= m: when issuing acpiconf -s 3 from the console, they enter acpi s3, and when resuming they don't turn the screen back on (it stays not illuminated if integrated in the laptop, or powered off if external). all of them are booting in UEFI mode and using efifb as the VT driver: "VT(efifb): resolution 3440x1440" all of them are however still responsive and fully usable via SSH while in = that post-resume display off state. having the kernel resume vector try to reset the screen by setting first hw.acpi.reset_video=3D1 does not work. However, on each of them, installing and using the appropriate driver from drm-kmod or the nvidia-drm-kmod driver (on the dedicated gpu desktop) solves the display-off-on-resume issue, both when in a cli environment and when an= X11 session is active/in use. I think the issue might be with how efifb deals with hardware reactivation. I tried adding some debug printfs in vt and efifb and can confirm the the kernel suspend/resume hooks get set by vt, and that when suspending and resuming efifb successfully has vt_suspend() and vt_resume() from vt_core.c executed without error. So maybe some hardware init/reset that is necessary on those systems is not getting done by vt/efifb, while the drm helpers called when other drivers a= re in use succeed. I see that suspend/resume support to efifb was initially added when solving= the #237050 pr, but only signalling Xorg to release/reacquire the display was considered (with X and the proprietary nvidia driver in use as the use case= ). I don't know how to troubleshoot the problem further, but in case additional output is needed I'd be testing under the i9-7980XE/geforce rtx 3060/asus P= RIME X299-A rev 1 motherboard desktop PC for convenience, since that system is already running 15-CURRENT --=20 You are receiving this mail because: You are the assignee for the bug.=