On Tue, 17 Feb 2009, Michael Meskes wrote: > Does the bug still exist? I still cannot see how acpid itself can cause this > problem. However, I could see a module being the culprit, although it should > not stop when acpid is stopped then.
Still exists (kernel 2.6.30) > Anyway, if the problem is still there, could you please disable automatic > module loading by acpid (/etc/default/acpid, should be disabled in newer > version anyway). Yep, that's the case here. > Also, if stopping acpid stops that behaviour, does it come back if you restart > acpid with an empty /etc/acpi? Now it gets confusing. If I stop acpid, then the bug still exists now. I haven't tried freshly booting without allowing acpid to start. I could have sworn this was the case in the past, and now I can't find any processes running that I would point a suspicious finger towards. Also, it doesn't happen on a nearly identical install (but concievably I could have hacked acpi in a different way there) on a differnt dell laptop (dell vostro 1710 doesn't change its clock, whereas an dell inspiron 1520 does) Well, I don't know that this is an acpid bug, but damned if I know what's at fault, and my workaround still works... -- TimC We are no longer the knights who say "ni" We are the knights who say "icky icky (Comet) Ikeya-Zhang zoooboing!" --Lord Ender on /. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org