| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <200611140159.59926.len.brown@intel.com> Date: Tue, 14 Nov 2006 01:59:59 -0500 From: Len Brown <len.brown@...el.com> To: earny@...4u.de Cc: linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org Subject: Re: 2.6.19-rc[1-4]: boot fail with (lapic && on_battery) On Tuesday 31 October 2006 16:27, Ernst Herzberg wrote: > With 2.6.18.x everything works fine. > > But 2.16.19-rc does not boot if the laptop runs on battery _and_ lapic is > defined as boot parameter. > Local APIC disabled by BIOS -- you can enable it with "lapic" The BIOS is advising you here that it is a bad idea to enable the LAPIC on this system. So why are you using the "lapic" boot parameter? If you are running an CONFIG_SMP kernel with LAPIC enabled and deep C-states (such as are available on Thinkpads when on battery mode), you will run into the following bug: http://bugzilla.kernel.org/show_bug.cgi?id=7376 As this is not new, the mystery is really why you see no problems in 2.6.18. Perhaps you can forward the contents of /proc/interrupts for 2.6.18 with "lapic" and we can see if the timer and the LOC are in sync or not when on battery? /proc/acpi/processor/*/power will also tell us about the C-states -- dump it for both AC and battery mode. thanks, -Len - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists