Date: Sat, 15 Jan 2022 07:54:05 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 261218] graphics/drm-devel-kmod screens blacked out, system freeze, around two minutes after waking from sleep Message-ID: <bug-261218-7141@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D261218 Bug ID: 261218 Summary: graphics/drm-devel-kmod screens blacked out, system freeze, around two minutes after waking from sleep Product: Ports & Packages Version: Latest Hardware: Any URL: https://bsd-hardware.info/?probe=3D5f106ee686 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: x11@FreeBSD.org Reporter: grahamperrin@gmail.com CC: hselasky@FreeBSD.org, manu@freebsd.org, wulf@freebsd.org Flags: maintainer-feedback?(x11@FreeBSD.org) Assignee: x11@FreeBSD.org Keywords:=20 D33887, D33888, drm-kmod, graphics, LinuxKPI, radeonkms, resume, sleep, suspend, wake ---- At 23:58 yesterday, in bug 261166 comment 9:=20 > =E2=80=A6 Up for four hours, panic-free, =E2=80=A6 Three hours and twelve minutes later (03:10:24), I put the computer to sleep with a script that gracefully exports OpenZFS devices on USB:=20 * a mobile hard disk drive that comprises a non-essential pool * two small (thumb) flash drives that provide L2ARC to the boot pool =E2=80=93 then switched off a display on DisplayPort on the HP dock in whic= h this HP EliteBook 8570p rests.=20 ---- At then after 06:23, to the best of my recollection, I:=20 * woke the computer * switched on the display (a little late) * ran xrandr * disconnected then remade USB connections to the docked HP keyboard and=20 docked Kensington trackball (one after the other, I can't recall=20 which order, to work around the operating system not responding to=20 one of the two devices) * maybe also disconnected both devices then reconnected both devices * rearranged windows =E2=80=93 mostly dragging from the notebook display (l= eft) to the Philips display (right). Screens on both displays suddenly went dark (blank/black/grey) with no curs= or or pointer. I watched the front of the EliteBook for hard disk drive activity. None.=20 I have this computer set to gracefully shut down (not sleep) in response to= a press on the power button, which is separate from the keyboard. No response= to normal presses.=20 After a while, I forced off the computer, started, then shortly after the desktop environment (KDE Plasma) appeared I ran:=20 hw-probe -all -upload Result: <https://bsd-hardware.info/?probe=3D5f106ee686>; I see nothing in X.Org logs (probed, above) or /var/log/messages to indicate exactly what happened _immediately_ before the freeze occurred.=20 This absence of information is unfortunate, but does make sense, in that the freeze was sudden and complete.=20 Triage =3D=3D=3D=3D=3D=3D Tentatively graphics/drm-devel-kmod because I'm testing this in combination with the patches for (bug 261166) these two reviews:=20 =E2=9A=99 D33887 LinuxKPI: Allow spin_lock_irqsave to be called within a cr= itical section <https://reviews.freebsd.org/D33887>; =E2=9A=99 D33888 LinuxKPI: Allow wake_up to be executed within a critical s= ection <https://reviews.freebsd.org/D33888>; Cc: the author and reviewers. If this bug is irrelevant: my apologies, plea= se remove yourselves. Thank you.=20 Notes to self =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Four USB ports on the side of the dock:=20 * mobile hard disk drive (rear, upper) * trackball (front, lower) * keyboard (front, upper). Two USB ports at the rear of the dock:=20 * the lower nearly always runs to the USB hub that's integral to the=20 Philips display =E2=80=A6 yesterday, extraordinarily, I removed the cable= =20 (to rearrange things at the table) and did not replace it * L2ARC, 15G, Duracell-branded Alcor Micro Flash Drive=20 USB 058f:6387 (upper). Two ports on the left of the EliteBook:=20 * L2ARC, 29G, Kingston Technology DataTraveler 100 G3/G4/SE9 G2/50=20 USB 0951:1666 (front). --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-261218-7141>