Bug#273474: APM broken in image-2.6.8-1 version 2.6.8-3, worked in 2.6.8-1
maks attems wrote (Tue 2004-Sep-28 22:13:32 +0200):
> > There's a difference in APIC treatment. Here is the part when
> > using 2.6.8-1 (APM working fine):
> >
> > Sep 26 13:06:51 lilith kernel: Dell Latitude with broken BIOS detected. Refusing to enable the local APIC.
> > Sep 26 13:06:51 lilith kernel: Built 1 zonelists
> > Sep 26 13:06:51 lilith kernel: Kernel command line: auto BOOT_IMAGE=Debian_default ro root=305 acpi=off
> > Sep 26 13:06:51 lilith kernel: Initializing CPU#0
> >
> > Here is the part when using 2.6.8-3:
> >
> > Sep 26 13:01:45 lilith kernel: Built 1 zonelists
> > Sep 26 13:01:45 lilith kernel: Kernel command line: BOOT_IMAGE=Debian_default ro root=305 acpi=off
> > Sep 26 13:01:45 lilith kernel: Local APIC disabled by BIOS -- reenabling.
> > Sep 26 13:01:45 lilith kernel: Found and enabled local APIC!
> > Sep 26 13:01:45 lilith kernel: Initializing CPU#0
>
> i'm a bit confused, but the 2 dmesg that you appended are both
> regarding kernel 2.6.8-1.
Yes, correct. The difference is that everything works with the
kernel/modules from version 2.6.8-1 of the package
kernel-image-2.6.8-1-686, but it doesn't work with the
kernel/modules from version 2.6.8-3 of that package. (BTW, this
_is_ confusing, is this the way version numbers are normally
done?)
> the difference seems your boot cmdline. in the second case noacpi is not
> parsed and therefor acpi enabled.
I never used a "noacpi" command, always "acpi=off". And as far
as I could see, ACPI was never turned on, only the messages
regarding (the local?) APIC were different.
> AFAIK lilo prepends "auto" before the whole cmdline what happened to the
> second?
I couldn't find out for sure when exactly the "auto" is
prepended, but I believe it happens when a "reboot" command is
issued. The "auto" command has not always been present when the
kernel from kernel-image-2.6.8-1-686=2.6.8-1 was booted.
> so your problem doesn't seem 2.6.8-1 specific.
> didn't see an apm change when going through the changelog concerning
> 2.6.8-3 versus 2.6.8-3-1.
Hm, misunderstanding regarding the versions? In bug #272177,
there are two more people with the same problem, at least one
other turned up on the debian-laptop mailing list today. And I
can revert to the working setup by only downgrading
kernel-image-2.6.8-1-686 to version 2.6.8-1.
> what bootloader are using?
lilo/testing.
Cheers, Marcus
--
Marcus C. Gottwald · <mcg@cheers.de> · http://cheers.de
Reply to: