On Thu, 2006-11-02 at 09:40 -0500, Stephen Clark wrote:No interrupt assignments are the same - but what about the hi-res timer the lapic is
Sergio Monteiro Basto wrote:
On Wed, 2006-11-01 at 22:03 -0500, Dave Jones wrote:Loading the correct kernel arch 686 - fixes my powernow problems - this is a mobile duron.
On Wed, Nov 01, 2006 at 08:08:31PM -0500, Stephen Clark wrote:This story of trying enable lapic when BIOS don't, has been triggered on
booting without lapic allowed it to boot but now I getThe Duron had powernow ?
...
Local APIC disabled by BIOS -- you can enable it with "lapic"
...
Local APIC not detected. Using dummy APIC emulation.
which means more processor overhead - right?
also cpuspeed doesn't work anymore - I don't have a cpufreq dir
kernel2.6.18, but in my opinion is not a bug if lapic on those computers
don't work.
If you boot without enable lapic, you will see cat /proc/interrupts with
interrupts in XT-PIC.
if you try enable lapic, somehow IRQ routing should change and if /proc/interrupts still the same, with IRQs in XT-PIC.
I think, lapic still not enabled and the most you can get it's problems.
Unless you know that lapic works (it is programmed and BIOS wrongly
disable it), you shouldn't try enable lapic because it is probable that
just give problems, to you. Historically: In 2002/3 was a very common bug, when kernel was compiled
to support lapic and try enable lapic (even when BIOS don't) and
computer hangs on boot.
Booting with lapic worked fine on fc5 kernel-2.6.18-2200 but it causes fc6 kernel-2.6.18-2798
to hang.
With lapic boot option enabled, have you a different /proc/interrupts ? have you lapic working ?