> On Wed, 28 May 2003 13:42:13 -0400, Zwane Mwaikambo wrote:
> >
> > I submitted a patch for nolapic before...
>
> Did you get any response as to whether it was going to be accepted into
> the kernel or not?
Considering the dalay, i'll resend and give it another go, but generally
it means it's not going anywhere.
> The unfortunate thing is that even this sort of fix will not help my
> situation. The reason being (which I only discovered by accident when I
> set "dont_enable_local_apic = 1" rather than "dont_use_local_apic_timer"
> and it didn't correct the booting problem) is that it seems that even if
> the local apic is set disabled by setting dont_enable_local_apic = 1 in
> arch/i386/kernel/apic.c, setup_APIC_clocks() is still called.
How did you determine that? printks? Was this with my patch applied? I
originally did this patch for the exact same problem (buggy local APIC
implimentation).
(much snipped)
Linux version 2.5.70-mm1 (zwane@montezuma.mastecende.com) (gcc version
Kernel command line: nolapic nmi_watchdog=2 ro root=/dev/hda1 profile=2
debug console=tty0 cons0
kernel profiling enabled
Initializing CPU#0
CPU0: Intel Celeron (Mendocino) stepping 05
per-CPU timeslice cutoff: 365.65 usecs.
task migration cache decay timeout: 1 msecs.
SMP motherboard not detected.
Local APIC not detected. Using dummy APIC emulation.
Starting migration thread for cpu 0
> So the jist is that using the local apic timer feature is not dependent on
> using the local apic, as per the dont_enable_local_apic and
> dont_use_local_apic_timer flags in arch/i386/kernel/apic.c. Maybe this is
> wrong, I dunno unfortunately.
>
> I don't know anything about this APIC stuff so I don't know if that is
> correct or not, but it is what happens.
>
> Thanx for the input though, much appreciated,
You're welcome,
Zwane
-- function.linuxpower.ca - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/