maximum cpu load with -sharevts

Bug #33611 reported by Michaël Witrant
6
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Xorg takes 100% of the CPU when it's run with -sharevts. Having another X server running or not doesn't change anything.

You'll need a remote access to reproduce and experiment this. Otherwise you may have to reboot very frequently.
* Log in remotely
* Kill any X server running
* Run "Xorg -sharevts &"
* Run "top" and check CPU usage

Revision history for this message
Michaël Witrant (mike-lepton) wrote : Bug fix

This patch fixes the problem.

Revision history for this message
Michaël Witrant (mike-lepton) wrote :

I've forgotten some version informations. I'm using Breezy and xorg 6.8.2-77.

Without the patch, the tty is closed when the server starts. I think this file is then scaned in a select or something, and probably raises an event continiously.
With the patch applied, the tty is closed when the server exits.

Revision history for this message
cferron (cferron) wrote :

would it be possible to have the binaries of your xorg 6.8.2-77 with this patch already applied, I have the same issue here (on my slackware box with xorg 6.9) I would like to try this binarie to see if it resolve the issue... What is the version of Xorg you applied the patch in the first place? did it include the -sharevts option already or you had to apply another patch?

Many thanks.

Claude

Revision history for this message
Michaël Witrant (mike-lepton) wrote :

You can get the binaries here : http://www.lepton.fr/misc/xserver-xorg-core_6.8.2-77_i386.deb
But I'm not sure this package will help you on your slackware.

The only patch applied is the one I submitted. Ubuntu team has already applied the sharevts patch (and many others).

Revision history for this message
cferron (cferron) wrote :

I was able to modify source code from Xorg 6.9 and compile it under Slackware 10.2 CPU load seem to be resolve.... but sometimes 1 Xorg application will start to go 100% like crazy.... I'll try to dtermine what I'm doing for it to go 100% and I'll keep posting in this forum.

Claude

Revision history for this message
Nickybatts (nickybatts) wrote :

Can this bug be closed now?

Revision history for this message
Michaël Witrant (mike-lepton) wrote :

Probably. I don't know if it's been fixed or not, but it should be submitted to xorg team anyway.

Revision history for this message
Matt Zimmerman (mdz) wrote :

Patch available for review

Changed in xorg:
assignee: nobody → fabbione
Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

Setting the status to 'In Progress' since there is a patch in the works.

Changed in xorg:
status: Unconfirmed → In Progress
Revision history for this message
Fabio Massimo Di Nitto (fabbione) wrote :

The patch doesn't apply to xserver-xorg-core in dapper and the rediff doesn't solve the problem.

Changed in xorg:
assignee: fabbione → nobody
status: In Progress → Confirmed
Revision history for this message
Fabio Massimo Di Nitto (fabbione) wrote :

ahh there it is..

Changed in xserver-xorg-core:
status: Confirmed → Fix Committed
Revision history for this message
Fabio Massimo Di Nitto (fabbione) wrote :

gone.... pkg uploaded in dapper, they will hit the archive in a few hours.

Fabio

Changed in xserver-xorg-core:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.