mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel-stuff <kernel-stuff@comcast.net>
To: Andi Kleen <ak@suse.de>
Cc: Zwane Mwaikambo <zwane@linuxpower.ca>,
	linux-kernel@vger.kernel.org, acurrid@nvidia.com
Subject: Re: X86_64: Many Lost ticks
Date: Thu, 18 Nov 2004 20:56:02 -0500	[thread overview]
Message-ID: <200411182056.03184.kernel-stuff@comcast.net> (raw)
In-Reply-To: <20041118184904.GN17532@wotan.suse.de>

Andi / Zwane
Ignore my earlier mail about the DMA timeouts and NMI errors after applying 
the ACPI timer override patch.  My bad.  I forgot to recompile the modules 
after I applied your patch - and I believe thats what caused those errors. 
I recompiled and reinstalled the modules this time and no errors [well, apart 
from those lost ticks, which anyway is a separate issue]  with the ACPI Timer 
override for NVIDIA chipset. 

Alan - Needless to say you should keep Andi's NVIDIA ACPI Timer override patch 
in -ac. It works.

Sorry for the confusion!

Parry

On Thursday 18 November 2004 13:49, Andi Kleen wrote:
> On Thu, Nov 18, 2004 at 05:02:37PM +0000, kernel-stuff@comcast.net wrote:
> > I tried all the newer kernels including -ac. All have the same problem.
> >
> > Andi -  On a side note, your change  "NVidia ACPI timer override" present
> > in 2.6.9-ac8 breaks on my laptop - I get some NMI errors ("Do you have a
> > unusual power management setup?") and DMA timeouts - happens regularly.
>
> Hmm, I was told Timer overrides are always bogus on Nvidia and
> that it was the last remaining known apic bug.
> But perhaps there are other APIC bugs in there.
>
> Can you submit a full boot.msg of the problem?
>
> -Andi

  reply	other threads:[~2004-11-19  2:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-18 17:02 kernel-stuff
2004-11-18 17:08 ` Zwane Mwaikambo
2004-11-18 17:10 ` Alan Cox
2004-11-18 18:24   ` Zwane Mwaikambo
2004-11-18 18:50   ` Andi Kleen
2004-11-18 18:49 ` Andi Kleen
2004-11-19  1:56   ` kernel-stuff [this message]
2004-11-19 15:57     ` Zwane Mwaikambo
2004-11-20  0:17       ` kernel-stuff
2004-11-20  2:39     ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2004-11-22 15:11 Chuck Ebbert
2004-11-19  8:19 Chuck Ebbert
2004-11-19 16:11 ` Zwane Mwaikambo
2004-11-18 19:30 kernel-stuff
2004-11-18 19:03 kernel-stuff
2004-11-18 17:19 kernel-stuff
2004-11-18  4:14 kernel-stuff
2004-11-18  4:02 kernel-stuff
2004-11-18  5:06 ` Andi Kleen
2004-11-18 15:54   ` Zwane Mwaikambo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200411182056.03184.kernel-stuff@comcast.net \
    --to=kernel-stuff@comcast.net \
    --cc=acurrid@nvidia.com \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zwane@linuxpower.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome