The last two days, without GDB, again it worked with no issues, so the
glitch, hardware or software, seems disappeared.
I spoken too early. Well, this time I was able to get a backtrace,
don't know if useful:
Program received signal SIGINT, Interrupt.
0xb7f0b424 in __kernel_vsyscall ()
#0
Andrea Vettorello wrote:
The last two days, without GDB, again it worked with no issues, so the
glitch, hardware or software, seems disappeared.
I spoken too early. Well, this time I was able to get a backtrace,
don't know if useful:
Program received signal SIGINT, Interrupt.
On Wed, 2008-08-06 at 12:53 +0200, Brice Goglin wrote:
Andrea Vettorello wrote:
The last two days, without GDB, again it worked with no issues, so the
glitch, hardware or software, seems disappeared.
I spoken too early. Well, this time I was able to get a backtrace,
don't know if
On Wed, Aug 6, 2008 at 12:53 PM, Brice Goglin [EMAIL PROTECTED] wrote:
[...]
Did you check that Xorg was actually stuck in there ?
Well, not completely stuck but as reported earlier, 100% CPU usage by
X process, mouse pointer responding to movements but not buttons
press, keyboard not
All last week I've used X attached to GDB trying to get a useful
backtrace, but I was not able to replicate the hangs with current Sid
packages.
The last two days, without GDB, again it worked with no issues, so the
glitch, hardware or software, seems disappeared.
--
Andrea
--
To
I can reproduce the original report relatively precisely. It appears to
be related to 3D acceleration.
I'm using the most recent packages in Lenny on AMD64, with a PCIE ATI
Radeon X800XT.
Using the default XAA acceleration, not EXA. Start an X session
(without compiz, tested in Gnome and
Package: xorg
Version: 1:7.3+12
Severity: important
Hello,
since a few days, xorg occassionally occupies the whole available CPU time,
which makes the system unusable. It is even impossible to stop the xorg process
with kill -9 ...!
In /var/log/Xorg.0.log.old I see the following last messages:
On Wed, Jul 9, 2008 at 18:32:29 +0200, Juergen Kosel wrote:
since a few days, xorg occassionally occupies the whole available CPU time,
which makes the system unusable. It is even impossible to stop the xorg
process
with kill -9 ...!
In /var/log/Xorg.0.log.old I see the following last
8 matches
Mail list logo
