Bug 272802 - graphics/drm-510-kmod with x11/sddm: sometimes, after stopping SDDM, the system becomes unusable
Summary: graphics/drm-510-kmod with x11/sddm: sometimes, after stopping SDDM, the syst...
Status: Open
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-x11 (Nobody)
URL:
Keywords: crash
Depends on:
Blocks:
 
Reported: 2023-07-29 19:45 UTC by Graham Perrin
Modified: 2023-12-30 06:57 UTC (History)
1 user (show)

See Also:
grahamperrin: maintainer-feedback? (x11)

Attachments
relevant lines from sddm.log (6.02 KB, text/plain)
2023-07-29 19:45 UTC, Graham Perrin 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Graham Perrin 2023-07-29 19:45:06 UTC 
Created attachment 243694 [details]
relevant lines from sddm.log

Not consistently reproducible, however this bugged me twice in a short period of time, so it's worth reporting. 

Steps: 

 1. use SDDM to start Plasma (X11)

 2. use Plasma for a while

 3. log out

 4. await appearance of the SDDM dialogue

 5. Control-Alt-F2 for ttyv1

 6. login as root

 7. service sddm stop

Expected: 

 8. a fairly short waiting period, then ttyv0 console

Actual result: 

 8. endless blankness/blackout, with a movable pointer

 9. no response to HID input

Workaround: 

10. press the power button (hw.acpi.power_button_state: S5).

Probed after the most recent occurrence: 

-  <https://bsd-hardware.info/?probe=2619fadb11>

Tail of the attached log file: 

[19:46:02.559] (WW) DAEMON: Signal received: SIGTERM
[19:46:02.581] (II) DAEMON: Greeter stopping...
[19:46:02.581] (WW) HELPER: Signal received: SIGTERM
[19:46:07.581] (II) DAEMON: Socket server stopping...
[19:46:07.582] (II) DAEMON: Socket server stopped.
[19:46:07.582] (II) DAEMON: Display server stopping...
[19:46:07.688] (II) DAEMON: Display server stopped.
[19:46:07.688] (II) DAEMON: Running display stop script  ("/usr/local/share/sddm/scripts/Xstop")
[19:46:07.695] (II) DAEMON: Greeter stopping...
[19:46:07.695] (WW) DAEMON: Error from greeter session: "Process crashed"
[19:46:07.695] (WW) DAEMON: Auth: sddm-helper (--socket /tmp/sddm-auth-05d71555-bd74-4e6c-b296-b0a0addea625 --id 4 --start /usr/local/bin/sddm-greeter --socket /tmp/sddm-:0-yVgxKr --theme /usr/local/share/sddm/themes/breeze --user sddm --greeter) crashed (exit code 1)
[19:46:07.695] (WW) DAEMON: Error from greeter session: "Process crashed"
[19:46:07.695] (WW) DAEMON: Auth: sddm-helper exited with 9
[19:46:07.842] (II) DAEMON: Greeter stopped. SDDM::Auth::HelperExitStatus(9)


Maybe worth mentioning: 

a) a scrub of a pool on a mobile hard disk drive on USB began yesterday

b) it feels, to me, as if this bug is more likely to bite after a long and/or
   intensive desktop session.
Comment 1 Graham Perrin 2023-12-30 06:57:20 UTC 
Comment 0 was with 14.0-CURRENT on an HP EliteBook 8570p. From <https://bsd-hardware.info/?probe=2619fadb11&log=pkglist>: 

> unknown-repository graphics/drm-510-kmod 5.10.163_7

Since moving the internal disk to an HP ZBook 17 G2 (Intel graphics disabled, x11/nvidia-driver-470 alone in use): no recurrence of the bug. 

All things considered – not only what's mentioned in comment 0 – I'm inclined to treat this as a drm-kmod issue (not kde@ -specific). 

There's the possibility/likelihood of me enabling Intel graphics, however I can't guess when this will happen (NVIDIA-related issues are my greater priority).