You are not logged in.
After upgrading to 2.3.4-2 my T23 freezes when resuming from either suspension/hibernation. Slim loads fine, and slimlock unlocks/works as expected but once the desktop (using openbox as main one right now) is shown it freezes. The only thing that seems to have resumed fine is Tint2 whereas wbar appears corrupted/hidden (as if it needed to be refreshed if you know what I mean) and conky does not even show up. But of course the whole thing is hard locked as said.
Today I upgraded from 2.3.4-1 to 2.3.5-1 but still the same happens.
Anyone else is experiencing this?
As soon as I downgrade to 2.3.4-1 everything is back to normal.
Last edited by root (2012-07-12 20:29:21)
\(o_X)/
'Cause I wanna be an Archy - An Archy in the UK // Sex Pistols
Offline
Checked with my secondary DE (XFCE) and even if it took longer to hard lock, it let me move the mouse pointer and multiple of them appeared on screen (in case that hints what the problem may be), it still ends up that way.
\(o_X)/
'Cause I wanna be an Archy - An Archy in the UK // Sex Pistols
Offline
During my latest tests I did not even have to access the desktop in order for the hard lock to take place. Just typing in the password in slimlock (during the typing there is a strange 'jumpy' effect when displaying the hidden password dots as if the password box was refreshing over and over - which does not happen when the laptop is started normally, including after upgrading the xf86-video-savage driver to the latest version), deleting it with backspace and moving the mouse (again multiple cursors occur just as during my test with XFCE) and that's it, hard locked.
I still think that multiple cursors displaying may hint me somewhere but right now I can't think of any concrete place to take a peek.
\(o_X)/
'Cause I wanna be an Archy - An Archy in the UK // Sex Pistols
Offline
I have run
dmesg |grep agpAnd noticed that this is shown with the xf86-video-savage 2.3.4-1 driver installed
[ 8.015831] Linux agpgart interface v0.103
[ 8.289850] agpgart-intel 0000:00:00.0: Intel 830M Chipset
[ 8.312468] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xd0000000whereas with the 2.3.5-1 one installed it shows
[ 8.015831] Linux agpgart interface v0.103
[ 8.289850] agpgart-intel 0000:00:00.0: Intel 830M Chipset
[ 8.312468] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xd0000000
[ 625.319029] agpgart-intel 0000:00:00.0: AGP 2.0 bridge
[ 625.319058] agpgart-intel 0000:00:00.0: putting AGP V2 device into 1x modeIs it possible for this mode switching to be causing my resume problems?
I have searched the forums and the net but did not find any resume issue related concretely to this 'switching to 1x mode' message.
\(o_X)/
'Cause I wanna be an Archy - An Archy in the UK // Sex Pistols
Offline
In the end I could switch to tty1 just in time in order to avoid the X freeze.
A look at the Xorg.0.log (or Xorg.0.log.old as that is where in the end the info was) gave me the following error messages:
(EE) SAVAGE(0): restarting S3 graphics engine reset 1 ...
(EE) SAVAGE(0): restarting S3 graphics engine reset 2 ...
(EE) SAVAGE(0): restarting S3 graphics engine reset 3 ...
(EE) SAVAGE(0): restarting S3 graphics engine reset 4 ...
(EE) SAVAGE(0): restarting S3 graphics engine reset 5 ...
(EE) SAVAGE(0): restarting S3 graphics engine reset 6 ...
(EE) SAVAGE(0): restarting S3 graphics engine reset 7 ...
(EE) SAVAGE(0): restarting S3 graphics engine reset 8 ...
(EE) SAVAGE(0): restarting S3 graphics engine reset 9 ...After finding some old messages reporting possible resume/suspend with SuperSavage cards, which wasn't my actual problem, I stumbled over this,
Bug 5569 - savage: glxgears only shows monochrome flicker
Still nothing related to my problem but one of the suggested fixes (the ShadowStatus one - instead of 'off' set to 'false' as it is a boolean one though I do not know if both formats would work - as I do not have a DmaMode entry in my xorg.conf) works just fine in my case.
\(o_X)/
'Cause I wanna be an Archy - An Archy in the UK // Sex Pistols
Offline