Bryce Harrington, le Thu 08 Oct 2009 00:39:09 -, a écrit :
On Wed, Oct 07, 2009 at 11:46:20PM -, Samuel thibault wrote:
Bryce Harrington, le Wed 07 Oct 2009 23:31:46 -, a ??crit :
On Wed, Oct 07, 2009 at 10:44:02PM -, Samuel thibault wrote:
Bryce Harrington, le Wed 07 Oct
Same problem here with a old Acer Aspire 3690
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS,
943/940GML Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML
Express Integrated Graphics Controller
Same problem on ASUS M50VC with GeForce 9300M G Videocard.
--
[karmic] Xorg 100% CPU utilization -- only after first login
https://bugs.launchpad.net/bugs/439138
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
On уто, 2009-10-06 at 23:25 +, Bryce Harrington wrote:
Try this out:
https://edge.launchpad.net/~bryceharrington/+archive/yellow
I have rebooted once with the updated xorg-server from above PPA and it
seems to have helped.
--
[karmic] Xorg 100% CPU utilization -- only after first
Bryce's GDM fixes the issue for me as well.
--
[karmic] Xorg 100% CPU utilization -- only after first login
https://bugs.launchpad.net/bugs/439138
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
Bryce: please also add a dependency on the console configuration
scripts, as while waiting for acpi probably helps to wait for the
console configuration, it'd be better to really make sure gdm doesn't
start before it.
--
[karmic] Xorg 100% CPU utilization -- only after first login
On Wed, Oct 07, 2009 at 09:56:10PM -, Martin Albisetti wrote:
Bryce's GDM fixes the issue for me as well.
Could you clarify? The fix I posted was to xorg-server, not GDM. Are
you referring to that, or to the GDM changes proposed by someone else in
this thread?
Bryce
--
[karmic] Xorg
On Wed, Oct 07, 2009 at 10:13:20PM -, Samuel thibault wrote:
Bryce: please also add a dependency on the console configuration
scripts, as while waiting for acpi probably helps to wait for the
console configuration, it'd be better to really make sure gdm doesn't
start before it.
Hi Samuel,
On Wed, Oct 07, 2009 at 01:01:57PM -, Michael Lazarev wrote:
Same problem on ASUS M50VC with GeForce 9300M G Videocard.
It is not necessary for further confirmations on this bug.
If you do decide to add confirmations anyway, please at least attach
your Xorg.0.log from your failed session,
On Wed, Oct 7, 2009 at 7:21 PM, Bryce Harrington
br...@bryceharrington.org wrote:
On Wed, Oct 07, 2009 at 09:56:10PM -, Martin Albisetti wrote:
Bryce's GDM fixes the issue for me as well.
Could you clarify? The fix I posted was to xorg-server, not GDM. Are
you referring to that, or to
Bryce Harrington, le Wed 07 Oct 2009 22:30:13 -, a écrit :
On Wed, Oct 07, 2009 at 10:13:20PM -, Samuel thibault wrote:
Bryce: please also add a dependency on the console configuration
scripts, as while waiting for acpi probably helps to wait for the
console configuration, it'd be
Bryce Harrington wrote:
On Wed, Oct 07, 2009 at 09:56:10PM -, Martin Albisetti wrote:
Bryce's GDM fixes the issue for me as well.
I'm still seeing the issue after disabling ACPI in the X server. The
only thing it does is get rid of the warning in xorg.conf, since the
acpi initialization
Bryce Harrington, le Wed 07 Oct 2009 23:31:46 -, a écrit :
On Wed, Oct 07, 2009 at 10:44:02PM -, Samuel thibault wrote:
Bryce Harrington, le Wed 07 Oct 2009 22:30:13 -, a ??crit :
On Wed, Oct 07, 2009 at 10:13:20PM -, Samuel thibault wrote:
Bryce: please also add a
Thought I'd give my input. I have a five year old laptop with intel
graphics. On Monday October 5th (...to be fair I believe it was this
Monday) I made the brave move to upgrade from 9.04 to 9.10 beta. Things
worked fine. It was after one of the later updates from the default
repositories when I
On Wed, Oct 07, 2009 at 11:46:20PM -, Samuel thibault wrote:
Bryce Harrington, le Wed 07 Oct 2009 23:31:46 -, a ??crit :
On Wed, Oct 07, 2009 at 10:44:02PM -, Samuel thibault wrote:
Bryce Harrington, le Wed 07 Oct 2009 22:30:13 -, a ??crit :
On Wed, Oct 07, 2009 at
What's this got to do with Upstart?
Why *should* X be able to tcflush() ?
** Changed in: upstart (Ubuntu Karmic)
Status: New = Invalid
--
[karmic] Xorg 100% CPU utilization -- only after first login
https://bugs.launchpad.net/bugs/439138
You received this bug notification because you
the switch of gdm to upstart seemed to be a possible reason for this behaviour
change. maybe it's something else though..
anyway, the use of tcflush() in X was added by:
commit 446d9443cea31e493d05c939d0128a8116788468
Author: Adam Jackson a...@redhat.com
Date: Wed Nov 5 11:51:06 2008 -0500
On Tue, 2009-10-06 at 14:36 +, Julien Cristau wrote:
the switch of gdm to upstart seemed to be a possible reason for this
behaviour change. maybe it's something else though..
anyway, the use of tcflush() in X was added by:
commit 446d9443cea31e493d05c939d0128a8116788468
Author: Adam
See xf86OpenConsole at
http://cgit.freedesktop.org/xorg/xserver/tree/hw/xfree86/os-support/linux/lnx_init.c
the console is /dev/ttyN, where N is the vt X runs on.
--
[karmic] Xorg 100% CPU utilization -- only after first login
https://bugs.launchpad.net/bugs/439138
You received this bug
Scott James Remnant wrote:
What's this got to do with Upstart?
X is started too early during bootup when the console isn't ready yet.
Where we don't know yet what ready means. There's also this:
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or
directory)
So we need a dependency
acpid doesn't matter, X will run just fine without it. Not sure what
the console isn't ready means...
--
[karmic] Xorg 100% CPU utilization -- only after first login
https://bugs.launchpad.net/bugs/439138
You received this bug notification because you are a member of Ubuntu-X,
which is
I'm also affected by this bug. It make my system completely unusable. I
have no SSD, only a HDD, and logging out and in again does not fix the
issue for me.
I have no idea what hardware I have, but as that is apparently not
relevant, I can try to give any other info you need.
--
[karmic] Xorg
I had similar problems (100% cpu load, no console switching possible)
after kdm start had been ported to upstart. I solved the problem by
modifying the upstart configuration file for kdm:
start on (filesystem
++and stopped udev-finish
and started hal)
This ensures that the
** Changed in: upstart (Ubuntu Karmic)
Importance: Undecided = High
** Changed in: upstart (Ubuntu Karmic)
Status: Invalid = Confirmed
--
[karmic] Xorg 100% CPU utilization -- only after first login
https://bugs.launchpad.net/bugs/439138
You received this bug notification because you
Still nothing to do with Upstart.
I would like to know *what* X is doing with that tcflush() and why it is
apparently unable to cope with it returning an error. What is that
trying to access, why isn't there a graceful fallback for it not
existing, etc.
Let's figure this out, rather than just
The kdm fix from jsiebold works also for gdm (/etc/init/gdm.conf)
--
[karmic] Xorg 100% CPU utilization -- only after first login
https://bugs.launchpad.net/bugs/439138
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
On Tue, 2009-10-06 at 18:31 +, Rob van Vliet wrote:
The kdm fix from jsiebold works also for gdm (/etc/init/gdm.conf)
This fix is wrong.
Just so you know.
Let's work out what the real fix should be.
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
[karmic] Xorg 100% CPU utilization
I'm not sure this is the same bug - but the timing and symptoms are the
same. In my case though DRM is failing. It says:
[1.698032] [drm:drm_fill_in_dev] *ERROR* Cannot initialize the agpgart
module.
[1.698157] [drm:intelfb_restore] *ERROR* Failed to restore crtc
configuration: -22
[
It has *nothing* to do with tcflush(). As I said above, If I revert the
patch that introduced the tcflush() call, I can still reproduce this
problem. This is just the semantics of select(): If a fd is in an error
state, then a subsequent read() or write() won't block (since they will just
return
Tom, I can't see anything besides this tcflush() thing adding the
console fd to the set we select() on. What do you mean by the console
fd dies?
Teodor, it's not the same bug.
--
[karmic] Xorg 100% CPU utilization -- only after first login
https://bugs.launchpad.net/bugs/439138
You received
You're right, I actually forgot to install the package, so you don't
have 100% CPU anymore after reverting the commit. But this really
doesn't fix the underlying problem, we still have an invalid console fd
floating around, which for example is preventing us from switching
virtual terminals.
Tom Jaeger, did you actually notice switching VT not working? Could
you get an strace of that happening?
Could people getting the error check /proc/`pidof X`/status? Here I
have
SigIgn: 10301000
The important part is the 3. If the 3 is not there it's normal that
tcflush() return EIO
Samuel thibault wrote:
Tom Jaeger, did you actually notice switching VT not working? Could
you get an strace of that happening?
Yes, I did. The issue comes and goes; and unfortunately I can't
reproduce it right now. This is the system call that failed, though
Mmm, ok, this can only happen when the ioctl handler is
hung_up_tty_ioctl, i.e. the tty got hung up after Xorg opened it, most
probably because with the parallel start in upstart the console may
get tinkered with after Xorg gets started. After an Xorg restart (or
equivalently, login/logout), no
Try this out:
https://edge.launchpad.net/~bryceharrington/+archive/yellow
--
[karmic] Xorg 100% CPU utilization -- only after first login
https://bugs.launchpad.net/bugs/439138
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
Samuel thibault wrote:
Could people getting the error check /proc/`pidof X`/status? Here I
have
SigIgn: 10301000
The important part is the 3. If the 3 is not there it's normal that
tcflush() return EIO for the console: because X starts its own session
alone, it is an orphaned
Tom Jaeger, le Wed 07 Oct 2009 00:29:13 -, a écrit :
Samuel thibault wrote:
Could people getting the error check /proc/`pidof X`/status? Here I
have
SigIgn: 10301000
The important part is the 3. If the 3 is not there it's normal that
tcflush() return EIO for the
I'm having this issue using the intel driver. My system is nearly
unusable because of it.
--
[karmic] Xorg 100% CPU utilization -- only after first login
https://bugs.launchpad.net/bugs/439138
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
In general, xorg 100% cpu bugs are rarely actually X bugs. X is a
server process that serves client requests. Client applications can
send X an endless series of requests, and this will drive the X cpu
utilization through the roof, but it is the client application which is
bugged; the X server
Oh, given how many people have 'me-too'd on this bug, it feels like a
regression that maybe occurred pretty recently. Check your
/var/log/dpkg.log to see what packages were changed. I don't think
there were any notable changes in X around the end of Sept when this was
first reported, so that
Thomas emailed me off-bug with some additional insights:
I'd like to bring your attention to bug #439138 [1], which I think
affects a large group of people and is important to get fixed before the
final release. The issue seems to be that on fast systems (for example
systems with an SSD in it),
The behavior of VT switching points toward a low-level bug, rather than
an application bug (cf. #437607):
0. After first login: X consumes 100% CPU
1. Alt+SysRQ+R (release KB, the VT switching seems to be disabled in default
configuration?)
2. Alt+F1 (switch to VT1)
3. Something (Xorg?) causes
The problem appears to be localized to the new upstart boot stuff. X is
trying to call tcflush() to flush the console of any unwritten output,
but is getting an EIO error now. Since the console doesn't get flushed,
that's leaving stuff there and makes the console fd appear to still be
readable
Question's to you keybuk... why is X not able to tcflush() during
bootup, and what's the right way to deal with the error?
** Also affects: upstart (Ubuntu)
Importance: Undecided
Status: New
--
[karmic] Xorg 100% CPU utilization -- only after first login
Stil happens after updating today to the latest kernel and libmesa.
--
[karmic] Xorg 100% CPU utilization -- only after first login
https://bugs.launchpad.net/bugs/439138
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
It looks like a duplicate of #407309
--
[karmic] Xorg 100% CPU utilization -- only after first login
https://bugs.launchpad.net/bugs/439138
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
This one doesn't make the system slow and unresponsive at all -- it's
barely noticable at all, except for the fan ramping up. But I agree,
some of the 'me too' replies are clearly instances of this bug.
--
[karmic] Xorg 100% CPU utilization -- only after first login
Same problem here. Clean installation of Karmic beta:
HDD
GF 8600GS (no Nvidia drivers)
This is significant issue for notebook users - it eats battery.
--
[karmic] Xorg 100% CPU utilization -- only after first login
https://bugs.launchpad.net/bugs/439138
You received this bug notification
** Changed in: xorg-server (Ubuntu)
Status: New = Confirmed
--
[karmic] Xorg 100% CPU utilization -- only after first login
https://bugs.launchpad.net/bugs/439138
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
Bryce, Could you please take a look and advise?
** Changed in: xorg-server (Ubuntu)
Assignee: (unassigned) = Bryce Harrington (bryceharrington)
** Changed in: xorg-server (Ubuntu)
Importance: Undecided = High
** Changed in: xorg-server (Ubuntu)
Milestone: None = ubuntu-9.10
** Tags
I can confirm this bug, 100% usage on 1 core, log out and back in solves it
no ssd, but I do have a raid 10 config
Started after installing the nvidia restricted drivers (version 185)
--
[karmic] Xorg 100% CPU utilization -- only after first login
https://bugs.launchpad.net/bugs/439138
You
btw, I have a amd phenom II X4 9100 cpu
GA-MA790XT-UD4P mobo
and nvidia 6600gt graphics card
--
[karmic] Xorg 100% CPU utilization -- only after first login
https://bugs.launchpad.net/bugs/439138
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Exactly same symptoms: xorg at 100% after first login. logout than login
again is ok. I have a very ordinary configuration with nvidia restricted
drivers. Latest updates applied.
--
[karmic] Xorg 100% CPU utilization -- only after first login
https://bugs.launchpad.net/bugs/439138
You received
This happens to me with the nvidia, the nv, and the nouveau driver.
Here's another thing I noticed: when I have the issue, xorg is not able to open
the acpid socket:
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or
directory)
If I log out and log back in, things go back to normal:
** Summary changed:
- [karmic] Xorg 100% CPU utilization after startup on SSDs
+ [karmic] Xorg 100% CPU utilization -- only after first login
--
[karmic] Xorg 100% CPU utilization -- only after first login
https://bugs.launchpad.net/bugs/439138
You received this bug notification because you are
55 matches
Mail list logo
