[Bug 477363] New: X taking 100% CPU after factory update
https://bugzilla.novell.com/show_bug.cgi?id=477363 Summary: X taking 100% CPU after factory update Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs@forge.provo.novell.com ReportedBy: fred.blaise@gmail.com QAContact: xorg-maintainer-bugs@forge.provo.novell.com Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.6) Gecko/2009012700 SUSE/3.0.6-2.5 Firefox/3.0.6 Just updated to factory as of Feb 18th. The problem first arose with nvidia drivers, and a bunch of the following message in the X log file: EQ overflowing. The server is probably stuck in an infinite loop. So I switched to nv. While I do not see these messages anymore, X is tying up one of my CPU core at 100%. Nothing much in the Xorg log file: scoomoon:/var/log # grep '(EE)' Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found) Please let me know what can be done. Thanks. Reproducible: Always Steps to Reproduce: Just be in init 5 or startx. Actual Results: X process taking 100% or one CPU core Expected Results: Would like to see X not taking so much CPU -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=477363
User markgray+to-suse@puck.nac.net added comment
https://bugzilla.novell.com/show_bug.cgi?id=477363#c1
Mark Gray
https://bugzilla.novell.com/show_bug.cgi?id=477363
Mark Gray
https://bugzilla.novell.com/show_bug.cgi?id=477363
User fred.blaise@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=477363#c2
--- Comment #2 from Fred Blaise
https://bugzilla.novell.com/show_bug.cgi?id=477363
User fred.blaise@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=477363#c3
--- Comment #3 from Fred Blaise
https://bugzilla.novell.com/show_bug.cgi?id=477363
User fred.blaise@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=477363#c4
--- Comment #4 from Fred Blaise
https://bugzilla.novell.com/show_bug.cgi?id=477363
User fred.blaise@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=477363#c5
--- Comment #5 from Fred Blaise
https://bugzilla.novell.com/show_bug.cgi?id=477363
User fred.blaise@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=477363#c6
Fred Blaise
https://bugzilla.novell.com/show_bug.cgi?id=477363
Mark Gray
https://bugzilla.novell.com/show_bug.cgi?id=477363
Mark Gray
https://bugzilla.novell.com/show_bug.cgi?id=477363
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=477363#c7
Stefan Dirsch
EQ overflowing. The server is probably stuck in an infinite loop.
We do not support the proprietary driver in any kind.
(EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
Make sure to uninstall the nvidia driver before you switch to nv driver. ==> INVALID -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=477363
User fred.blaise@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=477363#c8
Fred Blaise
https://bugzilla.novell.com/show_bug.cgi?id=477363
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=477363#c9
Stefan Dirsch
The nvidia module is blacklisted. Therefore, I think this bug is valid. Re-opening.
I don't talk about any kernel module. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=477363
User fred.blaise@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=477363#c10
Fred Blaise
https://bugzilla.novell.com/show_bug.cgi?id=477363
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=477363#c11
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=477363
User fred.blaise@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=477363#c12
Fred Blaise
https://bugzilla.novell.com/show_bug.cgi?id=477363
User fred.blaise@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=477363#c13
--- Comment #13 from Fred Blaise
https://bugzilla.novell.com/show_bug.cgi?id=477363
User fred.blaise@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=477363#c14
--- Comment #14 from Fred Blaise
https://bugzilla.novell.com/show_bug.cgi?id=477363
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=477363#c15
--- Comment #15 from Stefan Dirsch
Created an attachment (id=274195) --> (https://bugzilla.novell.com/attachment.cgi?id=274195) [details] New Xorg log after nvidia uninstall
Here is the new logfile.
Nothing obvious apart from some process constantly doing DDC probing. Is krandrtray doing its probing for new displays connected again ?!? :-( -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=477363
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=477363#c16
Stefan Dirsch
Created an attachment (id=274201) --> (https://bugzilla.novell.com/attachment.cgi?id=274201) [details] gdm logs, after launching a second instance of gdmflexiserver
I manually launched a 2nd gdmflexiserver, and ended up with 2 X processes, now each consuming each CPU core.
Anyways, I am attaching the GDM logs as well.
Sorry, don't know what I should do with gdm logs.
Also, there is no option on the GDM login screen to choose a failsafe session.
gdm is really crap. Ok, let's do it manually. rcxdm stop X -ac & sleep 2; DISPLAY=:0.0 xterm (In reply to comment #14)
Restarted with x11failsafe option specified at boot in grub, but same issue.
x11failsafe boot option means vesa or fbdev driver. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=477363
User fred.blaise@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=477363#c17
Fred Blaise
https://bugzilla.novell.com/show_bug.cgi?id=477363
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=477363#c18
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=477363
User fred.blaise@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=477363#c19
--- Comment #19 from Fred Blaise
https://bugzilla.novell.com/show_bug.cgi?id=477363
User kasievers@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=477363#c20
Kay Sievers
https://bugzilla.novell.com/show_bug.cgi?id=477363
User thoenig@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=477363#c21
--- Comment #21 from Timo Hoenig
https://bugzilla.novell.com/show_bug.cgi?id=477363
User fred.blaise@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=477363#c22
--- Comment #22 from Fred Blaise
https://bugzilla.novell.com/show_bug.cgi?id=477363
User vuntz@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=477363#c23
Vincent Untz
After today's factory upgrade, things actually got worse... X hangs, or get <defunct>.
This is likely something else. Please open a new bug against X. (it's generally not a good idea to re-use the same bug since it will mislead the people working n the bug) -- 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.
participants (1)
-
bugzilla_noreply@novell.com