You are not logged in.
This has only started in the last few days and I don't know what might have caused it.
If I close my laptop lid, nothing happens until another ACPI event happens, such as pressing the power button or un/plugging the A/C cord. Then it will suspend and wake up immediately (because the lid is actually open by this point).
Does anyone know why the acpi event is getting stuck in the tubes? Better yet, why is this happening now when it has been working perfectly for months?
Offline
BUMP?
I have tried downgrading acpi and acpid. I've also tried upgrading my kernel to 2.6.39-ck from 2.6.38.8
Last edited by pogeymanz (2011-06-22 01:01:00)
Offline
This reminds me of Schrödinger's cat. With the lid closed, how can you know ??
Anything interesting in dmesg or the acpi logs?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
This reminds me of Schrödinger's cat.
Totally off topic. Sorry. I realize it's a thought experiment describing a paradox, but I've always wondered if some college student has actually tried something like this. Hmmm?
Last edited by stlarch (2011-06-22 04:02:13)
Offline
I can tell with the lid closed because of which lights are on.
Anyway, I don't see anything interesting at all in the logs. This is so weird.
EDIT: I'm thinking that it might be conflicting kernel modules. For example I have phc-intel and acpi-cpufreq. Plus I'm using the CK kernel. So when I get home today, I'll first try removing phc-intel, then acpi-cpufreq, then I'll try stock kernel.
Last edited by pogeymanz (2011-06-22 17:32:56)
Offline
Well, I don't think it's any of those things...
Does any body have a clue as to what might mess up acpi signals? Other modules or settings or something?
Offline