On Sun, 2003-06-01 at 07:23, email@example.com wrote:
> I didn't follow this thread closely, but:
> 1. dont_enable_local_apic was originally only intended for those
> systems (i.e., Dell laptops) where enabling the local APIC in
> HW (via APIC_BASE MSR) causes problems due to broken BIOSen.
> It was never intended as a "Kernel, please don't use the local
> APIC even though I configured it" option. It doesn't help you
> if your machine boots with the local APIC enabled, but the
> local APIC doesn't work for some reason.
OK. I really have no experience or knowledge about this stuff to argue
> 2. The only way to reach no_apic is if we boot on a vendor/model
> combination that isn't known to have a local APIC that can be
> enabled in software. And the second patch hunk only makes a
> difference if the CPU boots with an enabled local APIC.
> So what vendor/model CPU is used in the failure case?
When the kernel boots, it detects the local APIC, however when it comes
time to calibrate the APIC timer interrupts, the kernel "stops"/hangs.
> (And if its local APIC is broken, cpu_has_apic should be cleared
> rather than setting the dont_enable flag. Post-boot code may
> access the local APIC if CONFIG_X86_LOCAL_APIC && cpu_has_apic.)
> 3. What is the exact failure? Hang or crash?
Normal boot until here:
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 1658.7651 MHz.
..... host bus clock speed is 0.0000 MHz.
cpu: 0, clocks: 0, slice: 0
> Where? UP or SMP kernel?
Brian J. Murrell <firstname.lastname@example.org>
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
-----END PGP SIGNATURE-----