RE: nforce2 bugs?

From: Andy Currid (ACurrid_at_nvidia.com)
Date: 09/30/04

  • Next message: Chiaki: "Re: FSCK message suppressed during booting? (2.6.9-rc2)" 
    Date:	Thu, 30 Sep 2004 08:43:05 -0700
To: "Maciej W. Rozycki" <macro@linux-mips.org>, "Prakash K. Cheemplavam" <prakashkc@gmx.de>, "Allen Martin" <AMartin@nvidia.com>

    I'm taking a look at the patches discussed in other recent emails on the
    list, but I'm curious about the timer issue that Maciej notes here. In
    systems running in IOAPIC mode where this problem has been observed, is
    ACPI enabled?

    I strongly suspect that it is. Some BIOSes on nForce systems contain an
    incorrect INT override for the timer interrupt in their ACPI tables,
    indicating that in IOAPIC mode the timer interrupts on IRQ2 rather than
    IRQ0. The kernel honors the override, then notices the timer interrupt
    isn't working and subsequently rescues the situation by configuring the
    timer in ExtInt mode. That recovers the timer interrupt but I suspect
    that configuration may be responsible for the "noisy" behavior (it's a
    faulty configuration).

    The workaround for the faulty override in IOAPIC/ACPI mode is to specify
    acpi_skip_timer_override as a boot parameter.

    If anyone has a system that is exhibiting the noisy behavior, I'd be
    interested to hear if this workaround addresses the problem. I haven't
    seen this specific behavior on my own nForce2 systems.

    Regards

    Andy 

    --
Andy Currid, NVIDIA Corporation 
acurrid@nvidia.com   408 566 6743
> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org 
> [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of 
> Maciej W. Rozycki
> Sent: Thursday, September 30, 2004 07:24
> To: Prakash K. Cheemplavam; Allen Martin
> Cc: Alan Cox; white phoenix; Linux Kernel Mailing List
> Subject: Re: nforce2 bugs?
> 
> 
> On Thu, 30 Sep 2004, Prakash K. Cheemplavam wrote:
> 
> > The only problem is the apic timer thing. It just gets 
> activated if the
> > correct BIOS Version is found (see the dmi scan thingie). 
> So I just pass
> > acpi_skip_timer_override to the kernel to be sure.
> 
>  There appears to be another timer problem, too -- at least for some
> boards the system timer (the 8254 PIT) has a noisy output.  
> When routed to
> an I/O APIC input it makes the system time go fast enough the 
> NTP daemon
> isn't able to compensate (it's a few minutes per day fast).  
> The problem
> goes away when routing it to the 8259A PIC, presumably 
> because the 8259A
> inputs are not "sticky" in the edge-triggered mode -- at the worst you
> only get spurious interrupts reported in /proc/interrupts in the "ERR"
> counter.
> 
>  An nVidia feedback would be appreciated.  Allen?
> 
>   Maciej
> -
> 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/
> 
-
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/
  • Next message: Chiaki: "Re: FSCK message suppressed during booting? (2.6.9-rc2)"

    Relevant Pages

    • [PATCH -rt] Resolve -rt OMAP conflicts
      ... This patch removes all the OMAP clocksource/clockevent stuff from the ... * Last processed system timer interrupt ... * Returns elapsed usecs since last system timer interrupt ... When dynamic tick is enabled, ...
      (Linux-Kernel)
    • Re: [PATCH] I/O APIC: Timer through 8259A revamp
      ... was that even a lot of relatively modern systems fall into the fallback ... The new burst of breakage came with the invention of ACPI and its tables ... Old MP tables coming from the MP spec used to get the timer interrupt ...
      (Linux-Kernel)
    • RE: [PATCH][2.6][5/5]Support for HPET based timer
      ... I experimented with HPET in native APIC routing mode. ... During boot up kernel expects to receive timer interrupt much before ...
      (Linux-Kernel)
    • Re: 8051 Timer 0, Mode 0
      ... a tickle before that time so I've been working on the assumption I ... timer) and let it do it's work. ... So I set the watchdog I/O pin one way within the timer interrupt, and set it the other way at the top of my round-robin loop. ...
      (comp.arch.embedded)
    • Re: fixed time slices?
      ... Hardware timer interrupts can be programmed by the HAL for different ... NEVERTHELESS, as soon as a higher priority thread becomes ready to run, it ... Scheduler "ticks" only ... timer interrupt for a specific delay for the purpose of changing tasks ...
      (microsoft.public.win32.programmer.kernel)