Red Hat Bugzilla – Bug 210277
Compiz and xen crashes
Last modified: 2007-11-30 17:11:45 EST
Description of problem:
Trying to start compiz crashes when my computer is booted with a xen kernel.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot computer using a xen kernel
2. Try starting compiz
Either the computer freezes so hard I've got to use the power switch to fix it,
or it simply reboots by itself.
System works perfectly nice when booted with non xen kernel. It also works very
nice in xen mode when using metacity (exactly same xorg config).
This is on a Znote6015WD laptop with Core2Duo processor running x86_64 Fedora.
Is there any way that I can extract any more useful information?
Hmm. If you have a serial port on the laptop then serial console ought to be
helpful. If not, then netconsole may work, depending on what sort of ethernet
controller it has.
A modern laptop with a serial port? ;-)
I think I need some help with getting the netconsole to work. I've done the
On the laptop (10.11.22.102):
# modprobe netconsole
...and disabled the firewall for udp 6666
On my other machine (10.11.22.52):
# nc -u -l 6666
...and likewisely disabled the firewall
This does not seem to do the trick.
I've got no kernel source installed. Where do I find the netlogging.txt file?
Looks like you did the netconsole options on a separate line. Try again like this:
# modprobe netconsole
That might work better. Unless it was just a typo on this bz comment.
Also, test out the logging with a "echo m > /proc/sysrq-trigger"
You can get the netconsole documentation from the kernel source at kernel.org.
It's in Documentation/networking/netconsole.txt. I don't know about a
Make sure the options and modprobe of netconsole are on the same line ( I should
have put a backslash there). Like
# modprobe netconsole \
I'd just like to note that I'll probably not get any useful debug output out
from this computer. The only way I have got my network to work is using
NetworkManager, and I can't seem to get NetworkManager to put the net up in any
other way than using the nm-applet. And I can't reach the nm-applet without X,
which doesn't work. Which is also different from what I first reported, because
then I succeeded to start X. Well, whatever. I'm quite sure now that this bug is
a dupe of 207432, since what Naoki describes fits perfectly well on my system
right now. Closing.
*** This bug has been marked as a duplicate of 207432 ***
I'm not running compiz though, and 207432 is listed as a duplicate of this ticket.
(In reply to comment #7)
> I'm not running compiz though, and 207432 is listed as a duplicate of this ticket.
I'm quite sure now that it had nothing with Compiz to do. It's just simply X
being very unstable and happened to crash while I was starting Compiz twice.
And no, 207432 is not listed as a duplicate of this, it's the other way. Makes a
world of difference ;-)