Your message dated Thu, 18 Oct 2007 07:46:31 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#446820: Re : Re : Bug#446820: Re : Bug#446820: xorg: X
freezes on screensaver or strace
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: xorg
Version: 1:7.3+2
Severity: grave
Justification: causes non-serious data loss
Recently I restarted my X server and took into account the last
upgrade. Now it appears that when I go away and come back to unlock the
screensaver, nothing responds. /usr/bin/X takes 99% of the CPU. I wanted
to investigate, but attaching the process with strace -p XXXX freezes
X in the same way (nothing at all is output by the strace). Then it
needs to be killed with a SIGKILL.
I reproduced the problem on a vanilla 2.6.23 kernel. Of course, this is
annoying because all my session and open work are lost...
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i586)
Kernel: Linux 2.6.23-grsec
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
Pierre Ynard wrote:
>> Can you try adding
>> Option "BusType" "PCI"
>> in the Device section of your xorg.conf?
>>
>> Also, you could try changing AGP speed settings. Either in the BIOS, or
>> in the Device section of xorg.conf with
>> Option "AGPMode" "1"
>> (1, 2, 4 and 8 are the possible values).
>>
>
>
> Bus type PCI fixes the problem. So do AGP modes 1 and 2, but 4 and 8
> crash. (There is no such AGP setting in my BIOS.)
>
Ok so you seem to have an AGP hardware (I think it's the AGP bridge)
that does not really like high-speed AGP things. You should probably
keep one of the above options in your config for ever since the driver
will probably never be able to detect such behavior automatically.
I am closing this bug now since it seems hardware-only related.
thanks,
Brice
--- End Message ---
