From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010726 Netscape6/6.1 Description of problem: When using roswell on a DELL C600 i come across a problem that after resuming from an apm monitor shutdown within a few minutes the whole pc freezes and i have to hard shutdown. By default the 2.4.6 kernel doesn't recognize the acpi system on this laptop so it defaults to apm for powermanagement (which is also enabled under kde to monitor battery juice) I manually compiled 2.4.7 with ACPI and ACPI management so apm doesn't load and i don't have this problem anymore. (kernel module, bug in 2.4.6 or??) is there a later kernel i can load from redhat or just stick with my custom one? How reproducible: Always Steps to Reproduce: 1.boot into xfree86 2.let apm shutdown monitor 3.use for a few minutes, 4. letp apm kick in 5. pc freezes Actual Results: lockup - looks like verything is normnal, but no response from keyboard, mouse or pointing devices (touchpad, usb mouse and keyboard) Expected Results: resume from apm Additional info: dell c600 p3 1000mhz 256 megs ram
We (Red Hat) should really try to fix this before next release.
I've been working on resume problems on a Dell inspiron 8000 recently (a coworker has one) and fixed several things in the resume code in the kernel. Once kernel 2.4.7-2.4 or later enters Rawhide, could you try with that ?
I am downloading rawhide right now. I will give it a shot and keep both releases on my laptop to see how it works. One question, with the new ACPI power management features in 2.4.7 or higher kernels should i even bothere with APMD? It looks like the new ACPI stuff works with the cpu temp, monitor disable, spin down, spin up and all that good stuff
ACPI is currently disabled, and will be for quite some time. The reason for that is that ACPI executes bios code in kernelmode (and lots of it) and most bioses have SO many bugs in it that it's unworkable.
Oh and I'm not sure -2.4 is in rawhide yet; iirc -2.0 is in there; rawhide is only updated once a week or so and I fixed this yesterday