> > amd_apic_timer_broken: forcing return value of 1
>
> since this makes it all work for you, it does appear that the AMD local
> timer stops in C1 even when that isn't true, and as such is not useful.
Probably messed up SMM code. Might not apply to all AMD CPUs.
> Sad. It probably means that we have to disable the local timer for *all*
> modern AMD CPU's.
I saw an APIC timer problem on a older AMD laptop too (long before RevF).
Back then I asked and it was apparently some SMM bug of that specific
BIOS.
What exact type of machine is it?
>
> Thomas/Ingo - did something change in the local apic programming? Or why
> did this work before? Was it just that we didn't use the local timer apic
We used to always use the interrupt 0 too, which woke up the CPU and
then piggy backed the APIC interrupt too which works once the CPU
is woken.
Thomas changed that then when he redid the code for clock sources
because interrupt 0/PIT isn't good for frequent reprogramming.
I did similar experiments some time ago but found it caused a lot of
problems and wasn't as brave as Thomas in working through them, so
i never pushed these patches.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
