From: Ian Kumlien <pomac@vapor.com>
To: linux-kernel@vger.kernel.org
Cc: ross@datscreative.com.au
Subject: NForce2 and AMD, disconnect.
Date: Wed, 10 Dec 2003 02:20:31 +0100 [thread overview]
Message-ID: <1071019231.1670.35.camel@big.pomac.com> (raw)
In-Reply-To: <1071007478.5293.11.camel@athlonxp.bradney.info>
[-- Attachment #1: Type: text/plain, Size: 977 bytes --]
Hi, again.
I did some reading on amd's site, and if the disconnect + apic fixed the
same problem as the ~500ns delay, then it could be as i suspect...
I suspect that something goes wrong with apic ack when the cpu is
disconnected and according to the amd docs we could check the
Northbridge's CLKFWDRST or isn't that avail on the outside?
(It would be interesting to see if that fixes the problem as well.)
http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/26237.PDF
I don't really have the knowledge but it would sure be nicer to fix this
by checking this than to just disable it. I dunno if there is something
we could do from within the kernel aswell with the sending of HLT but i
doubt it.
Anyways, we need a generalized patch that does better checking on the
NMI bit (like Ross' patch).
PS. Anyone that can point me to northbridge tech docks? and CC
--
Ian Kumlien <pomac () vapor ! com> -- http://pomac.netswarm.net
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-12-10 1:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-07 19:58 Fixes for nforce2 hard lockup, apic, io-apic, udma133 covered Ian Kumlien
2003-12-07 20:59 ` Jesse Allen
2003-12-07 20:56 ` Ian Kumlien
2003-12-08 2:07 ` Ross Dickson
2003-12-08 2:23 ` Ian Kumlien
2003-12-09 18:12 ` Catching NForce2 lockup with NMI watchdog Ian Kumlien
2003-12-09 22:04 ` Craig Bradney
2003-12-09 23:13 ` Ian Kumlien
2003-12-10 1:20 ` Ian Kumlien [this message]
2003-12-10 6:14 ` Bob
2003-12-10 7:51 ` Craig Bradney
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=1071019231.1670.35.camel@big.pomac.com \
--to=pomac@vapor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ross@datscreative.com.au \
/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).