I saw my previous one line fix for fast clock problems under 32 bits,
included in 2.4 kernel,
but not on 2.6 yet. Please apply the following patch.
This patch will avoid clock running too fast on many ATI IXP and nforce boards.
Firstly, motherboard and bios should give the right irq pin info, but if it fails
It should be tweaked inside kernel by chipset id and etc, but if it fails,
my patch will works as a general purpose fail safe.
Under amd 64 bits, many people have been already working on tweaking
irq pins detection and seems to be ok on most motherboard now,
but not so many people working on 32 bits or 2.4 kernel.
I have ATI IXP chipset with Pentium M CPU, so the fast clock problem is not
AMD64 specific.
It is not a optimal solution to use i8259A IRQ, but better than not working right.
On Fri, 25 Nov 2005 02:49:19 +0900
Akira Tsukamoto <[email protected]> mentioned:
>
> Ingo Molnar <[email protected]> mentioned:
> >
> > * Akira Tsukamoto <[email protected]> wrote:
> >
> > > This one line patch adds upper bound testing inside timer_irq_works()
> > > when evaluating whether irq timer works or not on boot up.
> > >
> > > It fix the machines having problem with clock running too fast.
> > >
> > > What this patch do is, if timer interrupts running too fast through
> > > IO-APIC IRQ then falls back to i8259A IRQ.
> >
> > thanks - looks good to me.
> >
> > Acked-by: Ingo Molnar <[email protected]>
> >
> > Ingo
>
> Thanks,
> I regenerated my patch to the latest kernel.
>
> Signed-off-by: Akira Tsukamoto <[email protected]>
>
> --- linux-2.6.15-rc2-atiix/arch/i386/kernel/io_apic.c.orig 2005-11-20 12:25:03.000000000 +0900
> +++ linux-2.6.15-rc2-atiix/arch/i386/kernel/io_apic.c 2005-11-25 02:43:40.000000000 +0900
> @@ -1877,7 +1877,7 @@ static int __init timer_irq_works(void)
> * might have cached one ExtINT interrupt. Finally, at
> * least one tick may be lost due to delays.
> */
> - if (jiffies - t1 > 4)
> + if (jiffies - t1 > 4 && jiffies - t1 < 16)
> return 1;
>
> return 0;
>
>
>
>
> --
> Akira Tsukamoto <[email protected]> <>
>
>
> -
> 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/
--
Akira Tsukamoto <[email protected]> <[email protected]>
-
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]
