https://bugzilla.novell.com/show_bug.cgi?id=752296
https://bugzilla.novell.com/show_bug.cgi?id=752296#c1
Jan Beulich changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P5 - None |P3 - Medium
Status|ASSIGNED |NEEDINFO
InfoProvider| |trier@rrz.uni-koeln.de
--- Comment #1 from Jan Beulich 2012-03-15 10:34:35 UTC ---
As a workaround, disable (blacklist, rename, or some such) the DRM module
(drm.ko), and configure X again. (The same effect might be achievable by
disabling acceleration when configuring X, and I understand that using
"nomodeset", possibly in combination with "x11failsafe", also allows X to come
up.)
As long as a serial port exists on (one of) the affected machine(s), we'd
absolutely need to see Xen messages (with "loglvl=all guest_loglvl=all" in
effect) too (not sure whether the non-X consoles are still usable after the
crash - if so, "xm dmesg" could of course also be used to get at those).
Further, kmsg_without_nomodeset_and_x11failsafe unfortunately appears to be
incomplete - there are fragments of messages in there, and comparing with the
-desktop kernel boot visible in /var/log/messages there are also DRM related
messages missing (and it is hence left unclear what the reason for this is).
The photo shows a panic that appears entirely unrelated (usage error on
invoking init).
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.