Created an attachment (id=12642)
Xorg-log after crash
Same problem here, tested with
- Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller
- Gentoo system
- xorg-server-1.4-r2
- xf86-video-i810 2.1.0, 2.1.1, 2.1.99 and current git version
- kernel 2.6.22 and 2.6.23
- with framebuffer (vesa, uvesa) and without
Steps to reproduce:
1. Boot system (drm and i915 unloaded)
2. Start X (everything's ok)
3. Use xterm or switch back to VT
4. s2ram
5. Resume
X will crash as soon it is activated.
It does not matter if you exit X and unload drm and i915 before suspending! X will crash when you try to restart it after resume.
Other way to reproduce:
1. Start system (without X)
2. s2ram
3. resume
4. Start X -> everything is OK
5. Quit X
6. s2ram
7. resume
8. Start X -> Crash
So I don't think this might be a kernel problem.
Interesting line from the logfile:
> space: 130800 wanted 131064
This value varies from time to time, so it seems to be a memory allocation problem?
Created an attachment (id=12642)
Xorg-log after crash
Same problem here, tested with
- Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller
- Gentoo system
- xorg-server-1.4-r2
- xf86-video-i810 2.1.0, 2.1.1, 2.1.99 and current git version
- kernel 2.6.22 and 2.6.23
- with framebuffer (vesa, uvesa) and without
Steps to reproduce:
1. Boot system (drm and i915 unloaded)
2. Start X (everything's ok)
3. Use xterm or switch back to VT
4. s2ram
5. Resume
X will crash as soon it is activated.
It does not matter if you exit X and unload drm and i915 before suspending! X will crash when you try to restart it after resume.
Other way to reproduce:
1. Start system (without X)
2. s2ram
3. resume
4. Start X -> everything is OK
5. Quit X
6. s2ram
7. resume
8. Start X -> Crash
So I don't think this might be a kernel problem.
Interesting line from the logfile:
> space: 130800 wanted 131064
This value varies from time to time, so it seems to be a memory allocation problem?