Click to See Complete Forum and Search --> : Laptop lid problem with 2.6.6


cybertron
06-09-2004, 10:43 PM
This came up in another thread but it didn't belong there so here's a new one for it.

I have a small but annoying problem since I compiled the 2.6.6 kernel. Every time that I shut the lid on my laptop the events/0 process starts hogging the CPU to the point where MPlayer stops for a few seconds if it's playing. It also caused a kernel compile to take over 8 hours (which is why it came up in the first place) because I closed the lid before going to bed. This only happens in my custom 2.6.6 kernel and not in the stock Mdk 2.6.3 one.

I haven't been able to find much out about events/0 either. Obviously it has something to do with the ACPI event for closing my laptop, but I'm not sure what part of the kernel config could cause this, especially since in another 2.6 kernel it works fine. I've also removed the lid script from /etc/acpi/events to make sure something wasn't going on with that. At the suggestion of Icarus in the other thread I also removed APM which I had accidentally left in my kernel config, but that didn't fix it either.

Like I said, this isn't a huge problem, but it would be nice to be able to shut my laptop at night and leave things running knowing that they'll finish before morning:eek: Plus it seems like this could kill my battery if I shut it while not plugged in.

JohnT
06-09-2004, 11:00 PM
See my thread on "Starting and Sutting down with 2.6.6".....there's a link in the post......m/b it'll help........on the homepage now.

cybertron
10-14-2004, 01:16 PM
Ah, it turns out that this is a kernel bug. Passing acpi=off in the kernel params will get rid of the problem, although obviously that will also disable ACPI. I'm planning to setup two different LILO options, one with ACPI for when I'm not plugged in and want a battery monitor, and one without for when I'm in my room and want to be able to leave my laptop closed without having to worry about frying the processor. Of course, now I'll probably install folding@home on it and nothing will have changed, but at least my cpu cycles will be put to good use:)

Must be my week for replying to my own old questions. This is the second random thing I've run across that turned out to be a kernel bug that has been bugging (oooh, bad pun;)) me for a while.

BTW, thanks for the reply earlier JohnT. I should have posted back again about it then.:rolleyes: