Hide Forgot
Created attachment 559048 [details] xorg log with xorg-x11-drv-intel 2.17.0 Description of problem: Since update from xorg-x11-drv-intel to 2.17.0-8.fc16, I'm suffering from spurious switches to the VT. Pressing ctrl-alt-F1 brings me back to the graphical desktop. Version-Release number of selected component (if applicable): 2.17.0-8.fc16 How reproducible: always Steps to Reproduce: 1. Nothing to do, it'll happen sporadically 2. 3. Actual results: Spurious switch to VT Expected results: Stays on graphical Additional info: 00:02.0 VGA compatible controller: Intel Corporation 82Q33 Express Integrated Graphics Controller (rev 02) 00:02.0 0300: 8086:29d2 (rev 02) (prog-if 00 [VGA controller]) Subsystem: 103c:281e Flags: bus master, fast devsel, latency 0, IRQ 42 Memory at f0100000 (32-bit, non-prefetchable) [size=512K] I/O ports at 1240 [size=8] Memory at e0000000 (32-bit, prefetchable) [size=256M] Memory at f0000000 (32-bit, non-prefetchable) [size=1M] Expansion ROM at <unassigned> [disabled] Capabilities: <access denied> Kernel driver in use: i915 Kernel modules: i915 It happens with both kernel kernel-3.2.2-1.fc16.i686 and kernel-3.2.1-3.fc16.i686 Machine is fully up to date.
Created attachment 559049 [details] xorg log with xorg-x11-drv-intel 2.16.0
It might not be the intel driver. I'm back home now and have the same spurious switch to the VT with a radeon card. Fully uptodate F16.
Created attachment 559133 [details] xorg log extract Here is what I have on each VT switch in the xorg log.
anything in dmesg any sign of an oops?
I wasn't able to reproduce during the week end on the radeon system. However, back in the office on the intel system, I found something in the /var/log/messages. Seems the issue is actually related to systemd, I got a lot of lines like this : systemd[1]: getty holdoff time over, scheduling restart.
That's probably bug #782087 then.
(In reply to comment #6) > That's probably bug #782087 then. Yes, it very much look like it, thanks a lot for the pointer. *** This bug has been marked as a duplicate of bug 782087 ***