Your message dated Sun, 30 May 2010 14:42:56 +0200
with message-id <20100530124256.GQ2398@galadriel.inutil.org>
and subject line Re: linux-image-3.6.26-1-686, bug on ACPI?
has caused the Debian Bug report #497051,
regarding linux-image-3.6.26-1-686, bug on ACPI?
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.)
--
497051: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497051
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

Package: linux-image-2.6.26-1-686
Version: 2.6.26-3
Severity: normal
Hi all!
Yesterday (8-28-08) I upgraded Debian Lenny to the lastest kernel in
the repository. Exactly, the 2.6.26-1-686 kernel.
I started to install the Ati Catalyst and the MadWifi driverson the
new kernel, when I found a problem that looked familiar for me (I
suffered it on the old 2.6.24-x-486 kernel. I don't remember the
number where "x". This kernel was the default on the netinst for
32bits. The kernel on this occasion dissapeared by installing the
2.6.24-x-686 kernel).
Ok, let's go with the problem (using 2.6.26-1-686 kernel):
When I start the system, I have to press all time a key on my keyboard
(for example "Alt") for the system continues booting up. If I don't
press any key the system looks frozen and the booting stops (when I'm
running X occurs the same. I have to move the mouse or press all time
a key for the system continues running normally) and continues booting
when I press a key again. If I stop pressing a key when a proccess is
running (or starting during the boot up), this proccess continues
running until the end of the operation.
At the moment the solutions are the following:
1) Boot up with acpi=off makes the system running normally. But
with this I don't have wifi, battery status, sensors, etc.
2)Stay with the previous kernel. The version 2.6.25-2-686. This
kernel works perfect for me. (I use this solution at the moment).
My system is: Acer Aspire 5102WLMi (AMD Turion X2 @ 1.6GHz, 1GB DDR
memory) running Debian Lenny up to date. Now I use 2.6.25-2-686
kernel instead the 2.6.26-1-686 kernel.
I think the problem is related to the ACPI.
Sorry for my bad English and thank you.
Goodbye.
-- Package-specific info:
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.25-2-686 (SMP w/2 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6.26-1-686 depends on:
ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy
ii initramfs-tools [linux-initra 0.92f tools for generating an initramfs
ii module-init-tools 3.4-1 tools for managing Linux kernel mo
Versions of packages linux-image-2.6.26-1-686 recommends:
ii libc6-i686 2.7-13 GNU C Library: Shared libraries [i
Versions of packages linux-image-2.6.26-1-686 suggests:
ii grub 0.97-46 GRand Unified Bootloader (Legacy v
pn linux-doc-2.6.26 <none> (no description available)
-- debconf information:
linux-image-2.6.26-1-686/preinst/abort-overwrite-2.6.26-1-686:
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.26-1-686/postinst/bootloader-error-2.6.26-1-686:
linux-image-2.6.26-1-686/postinst/depmod-error-initrd-2.6.26-1-686: false
linux-image-2.6.26-1-686/prerm/removing-running-kernel-2.6.26-1-686: true
linux-image-2.6.26-1-686/postinst/old-system-map-link-2.6.26-1-686: true
linux-image-2.6.26-1-686/preinst/abort-install-2.6.26-1-686:
linux-image-2.6.26-1-686/preinst/lilo-has-ramdisk:
linux-image-2.6.26-1-686/preinst/bootloader-initrd-2.6.26-1-686: true
linux-image-2.6.26-1-686/prerm/would-invalidate-boot-loader-2.6.26-1-686: true
linux-image-2.6.26-1-686/preinst/elilo-initrd-2.6.26-1-686: true
linux-image-2.6.26-1-686/postinst/kimage-is-a-directory:
linux-image-2.6.26-1-686/postinst/old-dir-initrd-link-2.6.26-1-686: true
linux-image-2.6.26-1-686/postinst/create-kimage-link-2.6.26-1-686: true
linux-image-2.6.26-1-686/preinst/lilo-initrd-2.6.26-1-686: true
linux-image-2.6.26-1-686/postinst/old-initrd-link-2.6.26-1-686: true
linux-image-2.6.26-1-686/preinst/overwriting-modules-2.6.26-1-686: true
linux-image-2.6.26-1-686/postinst/depmod-error-2.6.26-1-686: false
linux-image-2.6.26-1-686/postinst/bootloader-test-error-2.6.26-1-686:
linux-image-2.6.26-1-686/preinst/failed-to-move-modules-2.6.26-1-686:
linux-image-2.6.26-1-686/preinst/initrd-2.6.26-1-686:

On Thu, Feb 18, 2010 at 08:55:07PM +0100, Moritz Muehlenhoff wrote:
> On Fri, Aug 29, 2008 at 04:25:31PM +0200, Carlos Álvarez Martín wrote:
> > Package: linux-image-2.6.26-1-686
> > Version: 2.6.26-3
> > Severity: normal
> >
> > Hi all!
> >
> > Yesterday (8-28-08) I upgraded Debian Lenny to the lastest kernel in
> > the repository. Exactly, the 2.6.26-1-686 kernel.
> >
> > I started to install the Ati Catalyst and the MadWifi driverson the
> > new kernel, when I found a problem that looked familiar for me (I
> > suffered it on the old 2.6.24-x-486 kernel. I don't remember the
> > number where "x". This kernel was the default on the netinst for
> > 32bits. The kernel on this occasion dissapeared by installing the
> > 2.6.24-x-686 kernel).
> >
> > Ok, let's go with the problem (using 2.6.26-1-686 kernel):
> >
> > When I start the system, I have to press all time a key on my keyboard
> > (for example "Alt") for the system continues booting up. If I don't
> > press any key the system looks frozen and the booting stops (when I'm
> > running X occurs the same. I have to move the mouse or press all time
> > a key for the system continues running normally) and continues booting
> > when I press a key again. If I stop pressing a key when a proccess is
> > running (or starting during the boot up), this proccess continues
> > running until the end of the operation.
> >
> > At the moment the solutions are the following:
> > 1) Boot up with acpi=off makes the system running normally. But
> > with this I don't have wifi, battery status, sensors, etc.
> > 2)Stay with the previous kernel. The version 2.6.25-2-686. This
> > kernel works perfect for me. (I use this solution at the moment).
> >
> > My system is: Acer Aspire 5102WLMi (AMD Turion X2 @ 1.6GHz, 1GB DDR
> > memory) running Debian Lenny up to date. Now I use 2.6.25-2-686
> > kernel instead the 2.6.26-1-686 kernel.
> >
> > I think the problem is related to the ACPI.
> >
> > Sorry for my bad English and thank you.
>
> Sorry for the very late followup :-/
>
> The next release of Debian (6.0, code name Squeeze) will be based
> on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell
> us whether the problem persists. If so, we should report it upstream
> to the kernel.org developers.
>
> The 2.6.32 kernel is available from packages.debian.org and can
> be installed in both Debian stable, testing and unstable
> installations.
No further feedback, closing the bug.
If this can be reproduced with current kernels, please reopen this bug.
Cheers,
Moritz