From: kernel-stuff@comcast.net
To: Zwane Mwaikambo <zwane@linuxpower.ca>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: 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 19:03:06 +0000 [thread overview]
Message-ID: <111820041903.1235.419CF1EA000B12B3000004D3220588601400009A9B9CD3040A029D0A05@comcast.net> (raw)
I haven't tried Andi's patch with noapic yet. Will do that to see if it fixes the NMI and DMA timeouts.
And I have the latest available BIOS update applied.
May be related - once in 10 reboots (approx.) I get the K8 Errata #93 missing warning even with the updated BIOS - it's not consistent.
> 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 reply other threads:[~2004-11-18 19:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 19:03 kernel-stuff [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-22 15:11 X86_64: Many Lost ticks 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 17:19 kernel-stuff
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
2004-11-19 15:57 ` Zwane Mwaikambo
2004-11-20 0:17 ` kernel-stuff
2004-11-20 2:39 ` Alan Cox
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=111820041903.1235.419CF1EA000B12B3000004D3220588601400009A9B9CD3040A029D0A05@comcast.net \
--to=kernel-stuff@comcast.net \
--cc=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).