PDA

View Full Version : FC4 - gdm.binary & syslogd == CPU 100%

Ropeburn
17th May 2005, 05:15 PM
Hello,
I just installed FC4 on my dell box. The system is very unresponsive
due to gdm.binary and syslogd spinning and consuming my 100% of
the cpu cycle. Is there a way to prevent this?
Thomas.
AndyGreen
17th May 2005, 05:26 PM
service syslog stop

then try Ctrl-Alt-F1 and see if the problem was a spew of log messages from gdm? IIRC they should spew on tty1 when there is no syslog up.
Ropeburn
18th May 2005, 05:40 AM

Thank you. I did stop the syslogger as you suggested. My cpu is still at a 100% by the gdm.binary and I am not seeing many messages on tty1. The only messages I am seeing are from cron every 5 minutes or so. Any more suggestions?
RahulSundaram
18th May 2005, 07:31 AM
Thank you. I did stop the syslogger as you suggested. My cpu is still at a 100% by the gdm.binary and I am not seeing many messages on tty1. The only messages I am seeing are from cron every 5 minutes or so. Any more suggestions?

You are aware that FC4 has not been released and this is only a test version. right?. Try initiating a discussion in fedora-test list or filing a bug report in bugzilla.redhat.com

Rahul
Red Hat Inc
zhiping_mei
19th May 2005, 02:44 AM
The same problem also exists in FC3. As I openned open office file, the cpu and memory uses rushed to 100%. Most of the CPU was taken away by genome-setting-daemon, and nautilus, and sometimes genome-panel, genome-vfs-daemon. I hope this problem should not last to FC4.

By the way, my computer: IBM laptop, A20 m, CPU: Celeron 500 mHz, memory: 125 mb. HD: 12 g,
SlowJet
19th May 2005, 05:03 PM
FC4T3 had updates yesterday to fix gdm and a new kernal and 10 more fixes.
After those my system was very stable and smooth.
I still have to use yum as up2date has not worked for me since the 11th.

SJ
RahulSundaram
19th May 2005, 05:05 PM
The problem with up2date on the test releases is well known. Just use yum for now

Rahul

Red Hat Inc
SlowJet
19th May 2005, 05:12 PM
Oh,in what news paper did you see that story? :)

SJ
RahulSundaram
19th May 2005, 05:17 PM
Subsribe to the fedora-test release to keep yourself informed

Rahul

Red Hat Inc
SlowJet
19th May 2005, 05:44 PM
I did, and have been reading the digest for weeks.

All I ever saw was that up2date needed to be yum updated from .17 to .18.
It worked one time after that.

What's your offical bug informat telling you? ;)

SJ
RahulSundaram
19th May 2005, 05:46 PM
That it is not fixed and you should use yum instead

Rahul
Red Hat Inc
SlowJet
19th May 2005, 05:54 PM
Because you say, or because there is no other choice? lol

What is the problem and where did you read the source definition of a new problem after the 11th?

SJ
RahulSundaram
19th May 2005, 05:59 PM
Ok. I dont want to use this forum like an IRC channel so I am not inclined to continue this discussion anymore but here is one bugzilla on this as an example

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=158095

Rahul
Red Hat Inc
Red Hat Inc
SlowJet
19th May 2005, 06:09 PM
Translated, you don't know anymore than the next user. ;)
Bugzilla is hardly a widely (or easy to ingest) medium.
The tester-list is a chat session.
There is no widely anything for test releases.

But, I'll look at the bug repot and read it with my doughtnut and coffee. ;)
SJ
cybrjackle
19th May 2005, 06:14 PM
SlowJet,

up2date has been pounded and pounded over and over in the list and every else, besides, up2date just isn't as cool as yum :P
SlowJet
19th May 2005, 06:21 PM
So, not the point in this case.

The pounding mostly comes from nobs and parrots. :)
Up2date for FC3 has always worked for me, less the repo's or network hosed.

Can't blame Sendmail or SELinux, how about the CCG4 compiler? :)

Oh, it must be KDE blacklist. That's it Up2date is on the KDE blacklist.

SJ
RahulSundaram
19th May 2005, 06:23 PM
Translated, you don't know anymore than the next user. ;)
Bugzilla is hardly a widely (or easy to ingest) medium.
The tester-list is a chat session.
There is no widely anything for test releases.

But, I'll look at the bug repot and read it with my doughtnut and coffee. ;)
SJ

There is no requirement for any sort of "translation". I never claimed that I had any special internal knowledge on up2date bugs of any bug for that matter. You could do a simple search against up2date and it would list all the known bugs against it. If I get to know a new one I just use bugzilla to get it across to relevant developer/maintainer.Any other process to do it is a broken idea. Anything except maybe a few embargoed security issues (determined by user when filing it) are always out in the open in bugzilla.redhat.com for Fedora. . If only developers know about bugs, people who invest valuable testing out releases and identifying bugs do not get the respect they require and if only users get to know the bugs, developers wouldnt be able to get a chance to fix the problem so it works both ways.

fedora-test list is definitely used for discussions and it helps act as a medium for interaction between users themselves and with developers.

Rahul
Red Hat Inc
SlowJet
19th May 2005, 06:32 PM
Yep, and us end users are just ground cover and beggers. :)

SJ
cybrjackle
19th May 2005, 06:42 PM
SlowJet,

I found a link that might help you out.

Click me for all the answers to your problems!!!! (http://en.wikipedia.org/wiki/Internet_troll)

:cool:
AndyGreen
19th May 2005, 07:13 PM
lol "ground cover"... going to file that one next to "mouthbreather".

So: Alan Cox... no[o]b or parrot?

http://forums.fedoraforum.org/forum/showpost.php?p=251646&postcount=9