From: Zwane Mwaikambo <zwane@linuxpower.ca>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: kernel-stuff@comcast.net, Andi Kleen <ak@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: X86_64: Many Lost ticks
Date: Thu, 18 Nov 2004 11:24:38 -0700 (MST) [thread overview]
Message-ID: <Pine.LNX.4.61.0411181122480.4034@musoma.fsmlabs.com> (raw)
In-Reply-To: <1100797816.6019.24.camel@localhost.localdomain>
On Thu, 18 Nov 2004, Alan Cox wrote:
> On Iau, 2004-11-18 at 17:02, 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.
>
> Ok ACPI timer override probably goes back into the broken bucket and out
> of -ac in -ac11 then.
I think it's more a broken system, booting with noapic (as is what
happened before) should get things back to normal. Parry, have you updated
the BIOS on your laptop?
Thanks,
Zwane
next prev parent reply other threads:[~2004-11-18 18:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 17:02 X86_64: Many Lost ticks kernel-stuff
2004-11-18 17:08 ` Zwane Mwaikambo
2004-11-18 17:10 ` Alan Cox
2004-11-18 18:24 ` Zwane Mwaikambo [this message]
2004-11-18 18:50 ` Andi Kleen
2004-11-18 18:49 ` Andi Kleen
2004-11-19 1:56 ` kernel-stuff
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=Pine.LNX.4.61.0411181122480.4034@musoma.fsmlabs.com \
--to=zwane@linuxpower.ca \
--cc=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=kernel-stuff@comcast.net \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).