Hide Forgot
Created attachment 525604 [details] screenshot of the kernel backtrace Description of problem: I was doing some tests in X11 with the linux spice client going in and out of fullscreen (it's quite buggy and often leaves X with black screen or messed up screen positions) when I got this BUG in a VT Version-Release number of selected component (if applicable): This is a f16 system I upgraded this morning, the kernel was Linux teriyaki 3.1.0-0.rc8.git0.0.fc16.x86_64 #1 SMP Wed Sep 28 01:31:14 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux The X11 driver intel is xorg-x11-drv-intel-2.16.0-2.fc16.x86_64 The GPU is 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device 215a Flags: bus master, fast devsel, latency 0, IRQ 43 Memory at f2000000 (64-bit, non-prefetchable) [size=4M] Memory at d0000000 (64-bit, prefetchable) [size=256M] I/O ports at 1800 [size=8] Expansion ROM at <unassigned> [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 Kernel modules: i915 How reproducible: First time I hit this, though I've had gnome-shell switching to fallback mode several times during my tests, so maybe I didn't notice the BUG message. Steps to Reproduce: 1. start a (windows or linux) VM with SPICE enabled 2. log into the VM using spicec 3. go in and then out of fullscreen (shift+f11) 4. shutdown the VM (by using the guest OS controls, eg start/shutdown) Actual results: 5. due to a spice bug, the screens should turn black, and sometimes this BUG will be triggered Expected results: 5. the spice bug is still there and the screen are black, but I don't get a BUG :) Additional info:
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please add drm.debug=0x04 to the kernel command line, restart computer, and attach * your X server config file (/etc/X11/xorg.conf, if available), * X server log file (/var/log/Xorg.*.log*; check with grep Backtrace /var/log/Xorg* which logs might be the most interesting ones, send us at least Xorg.0.log) * output of the dmesg command, and * system log (/var/log/messages) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Created attachment 526075 [details] output of dmesg
Created attachment 526076 [details] Xorg.0.log (couldn't find a log with Backtrace in it)
Created attachment 526078 [details] /var/log/messages
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.