https://bugzilla.novell.com/show_bug.cgi?id=752296 https://bugzilla.novell.com/show_bug.cgi?id=752296#c17 --- Comment #17 from Boris Ostrovsky <boris.ostrovsky@amd.com> 2012-03-21 10:48:54 UTC --- (In reply to comment #16)
(In reply to comment #14)
I was able to reproduce this (although it's a bit difficult to be sure what "this" is)
"this" is a pretty clear and obvious BUG() instance visible in the logs: ..
but nomodeset argument seems to fix the problem. Going over the comments I don't think this argument was ever tested.
"nomodeset" was tried, albeit together with "x11failsafe", as indicated by the filenames (kmsg_with*_nomodeset_and_x11failsafe) in the attachment in the original description.
Then what I (and I believe Conny) saw is different. There are way too many logs here to see what exactly is the problem. I saw a couple of screenshots that were similar to what I observed.
I rather think that you or we need to debug it on an affected machine (possibly paired with identifying how far back in the kernel history the problem reaches, particularly whether e.g. SLE11 SP2's 3.0-based kernel is also affected).
Is there a description of that system, other than looking at dmesgs? Like lspci and dmidecode? (Again, it may be already there and I just don't see it) (I am out of office until Monday) -- 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.