Hi,
after about a dozen reboots and half a dozen fscks, I finally was
able to pinpoint the reason of why my laptop (ThinkPad X22 (2662XXK))
wasn't able to resume after suspend.
The DRM module 'radeon.o' somehow prevents a successful resume (but
not the suspend). Only after I made that module unavailable to the
modutils, my laptop now successfully completes suspend/resume cycles.
I noticed also that the radeon.o module sometimes refuses to
be removed claiming that some resources were still busy (while
I wasn't aware of using DRM).
Software:
vanilla Linux Kernel + FreeSWAN patch 2.4.19 as well as 2.4.20
Debian 3.0
modutils 2.4.21
binutils 2.12.90.0.1 20020307
gcc 2.95.4
Hardware:
IBM ThinkPad X22 (2662XXK)
ATI Radeon Mobility M6 LY
Please let me know, if I can help solving this issue by providing
more information or otherwise. I'm actually OK with how things
are right now (I don't use DRM), but this should be documented.
Maybe the kernel build system should prevent one from choosing
to build the radeon DRM as module, if CONFIG_APM is set?
Guenther
On Sat, Dec 14, 2002 at 06:04:06PM -0800, [email protected] wrote:
> after about a dozen reboots and half a dozen fscks, I finally was
> able to pinpoint the reason of why my laptop (ThinkPad X22 (2662XXK))
> wasn't able to resume after suspend.
>
> The DRM module 'radeon.o' somehow prevents a successful resume (but
> not the suspend). Only after I made that module unavailable to the
> modutils, my laptop now successfully completes suspend/resume cycles.
http://www.google.com/search?q=dri+radeon+resume
Yields:
http://cpbotha.net/dri_resume.html
This is applicable only if you're interested in suspending/resuming with
active DRI, which it doesn't seem you are. So it's just FYI :)
--
charl p. botha http://cpbotha.net/ http://visualisation.tudelft.nl/