[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#536240: marked as done (linux-image-2.6.30-1-686: kacpid & kacpi_notify use CPU cycles when lid closed on Acer Aspire One)

Your message dated Tue, 2 Mar 2010 23:35:37 +0100
with message-id <20100302223537.GC4502@galadriel.inutil.org>
and subject line Re: Bug#536240: linux-image-2.6.30-1-686: kacpid & kacpi_notify use CPU cycles when lid closed on Acer Aspire One
has caused the Debian Bug report #536240,
regarding linux-image-2.6.30-1-686: kacpid & kacpi_notify use CPU cycles when lid closed on Acer Aspire One
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
536240: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=536240
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.30-1-686
Version: 2.6.30-1
Severity: normal

When the lid is closed on my Acer Aspire One (D150-1577), kacpid and kacpi_notify both make very active use of the CPU.

I cannot find any evidence of a repeating lid event in my logs as suggested by similar problems had by others.  Also, my DSDT appears to have the relevant clause to prevent this.

This happens with 2.6.29 and 2.6.30 images from debian unstable, as well as my own 2.6.30.1 kernel.  I have the latest acpi packages, and it was happening with slightly older ones too.


-- Package-specific info:

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.30.1-nimloth (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.30-1-686 depends on:
ii  debconf [debconf-2.0]         1.5.26     Debian configuration management sy
ii  initramfs-tools [linux-initra 0.93.3     tools for generating an initramfs
ii  module-init-tools             3.9-2      tools for managing Linux kernel mo

Versions of packages linux-image-2.6.30-1-686 recommends:
ii  libc6-i686                    2.9-19     GNU C Library: Shared libraries [i

Versions of packages linux-image-2.6.30-1-686 suggests:
ii  grub                          0.97-53    GRand Unified Bootloader (Legacy v
pn  linux-doc-2.6.30              <none>     (no description available)

-- debconf information:
  linux-image-2.6.30-1-686/preinst/lilo-has-ramdisk:
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.30-1-686/postinst/old-initrd-link-2.6.30-1-686: true
  linux-image-2.6.30-1-686/postinst/create-kimage-link-2.6.30-1-686: true
  linux-image-2.6.30-1-686/postinst/depmod-error-2.6.30-1-686: false
  linux-image-2.6.30-1-686/postinst/old-system-map-link-2.6.30-1-686: true
  linux-image-2.6.30-1-686/prerm/would-invalidate-boot-loader-2.6.30-1-686: true
  linux-image-2.6.30-1-686/preinst/overwriting-modules-2.6.30-1-686: true
  linux-image-2.6.30-1-686/preinst/lilo-initrd-2.6.30-1-686: true
  linux-image-2.6.30-1-686/postinst/old-dir-initrd-link-2.6.30-1-686: true
  linux-image-2.6.30-1-686/preinst/failed-to-move-modules-2.6.30-1-686:
  linux-image-2.6.30-1-686/postinst/bootloader-test-error-2.6.30-1-686:
  linux-image-2.6.30-1-686/preinst/abort-install-2.6.30-1-686:
  linux-image-2.6.30-1-686/postinst/bootloader-error-2.6.30-1-686:
  linux-image-2.6.30-1-686/preinst/initrd-2.6.30-1-686:
  linux-image-2.6.30-1-686/prerm/removing-running-kernel-2.6.30-1-686: true
  linux-image-2.6.30-1-686/postinst/kimage-is-a-directory:
  linux-image-2.6.30-1-686/preinst/abort-overwrite-2.6.30-1-686:
  linux-image-2.6.30-1-686/preinst/elilo-initrd-2.6.30-1-686: true
  linux-image-2.6.30-1-686/preinst/bootloader-initrd-2.6.30-1-686: true
  linux-image-2.6.30-1-686/postinst/depmod-error-initrd-2.6.30-1-686: false

--- End Message ---
--- Begin Message --- 
On Sat, Feb 27, 2010 at 02:40:14PM -0500, ???????????????? ?????????????????? wrote:
> On 25 February 2010 13:28, Moritz Muehlenhoff <jmm@inutil.org> wrote:
> > On Sat, Feb 13, 2010 at 12:22:43PM +0100, maximilian attems wrote:
> >> On Wed, 08 Jul 2009, ???????????????? ?????????????????? wrote:
> >>
> >> >
> >> > When the lid is closed on my Acer Aspire One (D150-1577), kacpid and kacpi_notify both make very active use of the CPU.
> >> >
> >> > I cannot find any evidence of a repeating lid event in my logs as suggested by similar problems had by others.  Also, my DSDT appears to have the relevant clause to prevent this.
> >> >
> >> > This happens with 2.6.29 and 2.6.30 images from debian unstable, as well as my own 2.6.30.1 kernel.  I have the latest acpi packages, and it was happening with slightly older ones too.
> >>
> >> can you reproduce that with 2.6.32 latest from unstable?
> >>
> >> if yes please notify upstream in bugzilla.kernel.org and let us know the
> >> bugnr. thanks for your report.
> >
> > Did you report this at bugzilla.kernel.org ?
> >
> > Cheers,
> >        Moritz
> >
> 
> I think I did report it to the kernel developers, but I can't find it
> anywhere there.  I can't get the bug report system to let me see most
> of the bugs I've been CCed on--maybe because they've been closed?
> 
> The bug does pop up on Ubuntu's forums at
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/364592  and
> elsewhere at http://mindspill.net/computing/linux-notes/acpi/continuous-acpi-lid-events-and-100-cpu-usage.html
> .
> 
> I do know that this bug stopped being a problem a while ago, and I
> think it might be because I applied someone's custom DSDT (which was
> customised to solve another problem too, iirc), and I think it was
> from bugzilla.kernel.org.

It was http://bugzilla.kernel.org/show_bug.cgi?id=13802

The ACPI developers traced it down to a BIOS bug and stated it cannot
be fixed in the kernel. We're closing this bug as well, then.

Cheers,
        Moritz

--- End Message ---
Reply to: