On Sun, Oct 23, 2016 at 8:10 PM, Federico Giannici wrote:
> Since I upgraded my PC to 6.0 (amd64) the X server has began to crash almost
> once a day, usually after a while of minutes (it's variable, usually around
> 30-60 minutes after the boot).
>
> Video card is an "ATI Radeon HD 4350". No custom X configuration file.
> Before the upgrade to 6.0 (from 5.9) it never crashed in many years of
> usage, so I don't thing it's an hardware issue.
Have you tried a clean install of 5.9 to verify that it still works
fine? Was the move to 6.0 done via upgrade, and if so, have you tried
a clean install of 6.0? Probably also try a clean install of -stable
for good measure.
>
> I upgraded the kernel to a standard 6.0-stable comprehensive of the "011:
> SECURITY FIX: October 4, 2016" patches of the X library, but nothing
> changed.
>
> Here you can find the complete Xorg log and the dmesg:
>
> http://www.neomedia.it/tmp/Xorg.0.log
> http://www.neomedia.it/tmp/dmesg
>
> Here are the last lines of the Xorg log:
>
> [ 159.840] (II) RADEON(0): Modeline "1440x900"x0.0 88.75 1440 1488 1520
> 1600 900 903 909 926 +hsync -vsync (55.5 kHz e)
> [ 159.840] (II) RADEON(0): Modeline "1600x900"x60.0 119.00 1600 1696
> 1864 2128 900 901 904 932 -hsync +vsync (55.9 kHz e)
> [ 159.840] (II) RADEON(0): Modeline "1680x1050"x0.0 119.00 1680 1728
> 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
> [ 2039.854] (EE) Segmentation fault at address 0x1f8cf548b000
> [ 2039.854] (EE)
> Fatal server error:
> [ 2039.854] (EE) Caught signal 11 (Segmentation fault). Server aborting
> [ 2039.854] (EE)
> [ 2039.854] (EE)
> Please consult the The X.Org Foundation support
> at http://wiki.x.org
> for help.
> [ 2039.854] (EE) Please also check the log file at "/var/log/Xorg.0.log"
> for additional information.
> [ 2039.854] (EE)
> [ 2039.854] (EE) ws: /dev/wsmouse: unknown command 4
> [ 2039.854] (II) AIGLX: Suspending AIGLX clients for VT switch
> [ 2039.854] (EE) Server terminated with error (1). Closing log file.
>
> Do you think that the "/dev/wsmouse: unknown command 4" is a consequence of
> the crash or it could be the cause?
At first I'd say consequence, but considering the fact that everything
appears to have happened all at once... without knowing more about X,
I couldn't say with any degree of confidence.
>
> Any suggestions?
>
> Thanks.
>
--
Aaron Mason - Programmer, open source addict
I've taken my software vows - for beta or for worse
