From: Jamie Lokier <jamie@shareable.org>
To: Ross Dickson <ross@datscreative.com.au>
Cc: linux-kernel@vger.kernel.org, Ian Kumlien <pomac@vapor.com>,
Jesse Allen <the3dfxdude@hotmail.com>
Subject: Re: Nforce2 apic timer ack delay
Date: Mon, 9 Feb 2004 12:33:55 +0000 [thread overview]
Message-ID: <20040209123355.GB1738@mail.shareable.org> (raw)
In-Reply-To: <200402082141.09693.ross@datscreative.com.au>
Ross Dickson wrote:
> I was just writing you to tell you how well it prevented lockups
> when my system experienced a hard lockup in a slightly different
> form. Firstly mplayer bailed complaining about misuse of cpu ram
> etc, which is an abnormal failure for this system. I then swapped
> desktops back to continue my email and then no mouse or anything
> else just like one of the original hard lockups.
Well, that's a different form of lockup so it might be a different
culprit. What was the mplayer error?
> A bit early to draw conclusions but could it be that the bios also
> executes a hlt instruction in a System Management Interrupt??
> Perhaps on detecting a hot cpu or something??
Perhaps. Are you using APM or ACPI? I think they override
"idle=poll" and call into the BIOS for idling.
-- Jamie
prev parent reply other threads:[~2004-02-09 12:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-21 9:17 Updated Lockup Patches, 2.6.0 Nforce2, apic timer ack delay, ioapic edge for NMI debug Ross Dickson
2003-12-21 16:29 ` Craig Bradney
2003-12-22 18:50 ` Daniel Drake
2003-12-22 23:56 ` Ross Dickson
2003-12-24 15:41 ` Daniel Drake
2003-12-24 17:49 ` really bensoo_at_soo_dot_com
2004-02-07 14:55 ` Nforce2 apic timer ack delay Jamie Lokier
2004-02-08 11:41 ` Ross Dickson
2004-02-09 12:33 ` Jamie Lokier [this message]
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=20040209123355.GB1738@mail.shareable.org \
--to=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pomac@vapor.com \
--cc=ross@datscreative.com.au \
--cc=the3dfxdude@hotmail.com \
/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