System Environment: -------------------------- Mesa: (master)ee2bcf38a4c8930d8f9cecfac580030a45c41dae Xserver: (master)xorg-server-1.15.99.902-2-g3028ae6c9aa37168e249e0d8 Xf86_video_intel: (master)2.99.911-58-gf9a279b2dc8417b6504478ac96514125d6136523 Kernel: (drm-intel-nightly)git-cf8c74 Bug detailed description: ---------------------------- VT-switch may cause “no responsive” on graph interface by 3-6 times. “no responsive”is that screen seems to be frozen, mouse and keyboard can’t work. In the meantime, console is OK. Please see dmesg log and Xorg.0.log. Reproduce steps: ------------------------- 1. start system 2. VT-switch by 3-6 times
Created attachment 97489 [details] demsg.log
Created attachment 97490 [details] Xorg.0.log
The problem exists SteamOS
Please confirm that this happens on a production release or update of a major distro (Ubuntu, Fedora, etc) in addition to Steam OS.
Hi meng, Can you try stopping acpid as suggested by Aaron there? https://github.com/ValveSoftware/SteamOS/issues/147 If that works it's a dupe of a known acpid issue in SteamOS that will be fixed sometime soon. Thanks!
(In reply to comment #4) > Please confirm that this happens on a production release or update of a > major distro (Ubuntu, Fedora, etc) in addition to Steam OS. The SteamOS version is "SteamOS GNU/Linux 1 \n \1" and it is http://repo.steampowered.com/download/.
(In reply to comment #5) > Hi meng, > > Can you try stopping acpid as suggested by Aaron there? > > https://github.com/ValveSoftware/SteamOS/issues/147 > > If that works it's a dupe of a known acpid issue in SteamOS that will be > fixed sometime soon. > > Thanks! Ater replicated the issue, stopping acpid doesn't fix the issue.
Is this still reproducible? VT switch doesn't really involve Mesa (and neither does input handling), just kernel & X server. -> moving first to X.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/202.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.