can't kill -9 Xorg
hans at beastielabs.net
Tue Jun 12 17:29:37 UTC 2012
On 06/12/12 16:55, Anton Shterenlikht wrote:
> On Tue, Jun 12, 2012 at 02:13:17PM +0200, Hans Ottevanger wrote:
>> On 06/12/12 10:24, Anton Shterenlikht wrote:
>>> On Tue, Jun 12, 2012 at 09:13:06AM +0100, Anton Shterenlikht wrote:
>>>> On Tue, Jun 12, 2012 at 12:07:06AM +0530, Subhro Sankha Kar wrote:
>>>>> What happens if you run without a xorg.conf? Xorg has become pretty good
>>>>> at guessing correct settings these days.
>>>> No change.
>>>> I removed /etc/X11/xorg.conf completely.
>>> Anyway, I can understand my X setup is fucked, no problem.
>>> What worries me more is the the fact that a process ignores
>>> kill -9. Doesn't it indicate a problem with the OS?
>>> I think potentially this is a security vulnerability.
>> I had a similar issue with my desktop system a while ago, also using a
>> Radeon adaptor. In my case the system ended up with a frozen image or
>> black screen and was only accessible remotely. It appeared that the X
>> server took 100% of a CPU and was looping in the driver in kernel space
>> and thus unkillable. If a remember well a PCIE register seemed to be
>> inaccessible after returning from the screen saver and the driver kept
>> looping on this.
>> I finally worked around the problem by removing the (barely documented)
>> option DynamicPM from my xorg.conf. This could have consequences for
>> power saving on a laptop however, but it could be worth trying.
>> Kind regards,
> Thank you for the explanation.
> I my case
> Option "DRI" "off"
> helped. With DRI off I get X working (nearly) as expected.
> However, I'm now thinking that DRI not
> working is perhaps a bug? I'm using
> Driver "radeon"
> VendorName "Advanced Micro Devices [AMD] nee ATI"
> BoardName "RS690M [Radeon X1200 Series]"
Here I have:
VendorName "ATI Technologies Inc"
BoardName "RV370 5B60 [Radeon X300 (PCIE)]"
which actually is from an xorg.conf initially generated with "Xorg
-configure" quite a while ago and only slightly edited afterwards. If I
generate a new xorg.conf in this way it is virtually identical.
As I understand from your original post you only got this problem after
the png upgrade. Did Xorg work correctly before that time and did you
have the same version of Xorg that you have now? The
xorg-server-1.7.7_5,1 itself does not even depend on png, so you should
be able to run Xorg without hanging kernel driver.
You could do a forced rebuild of all X packages, also those that do
depend on png.
> Maybe I should ask in x11@?
Not a bad idea at all, if you fully specify your problem (as you did in
your original posting) and keep in mind that response times can be
somewhat longer there.
More information about the freebsd-questions