From: "Prakash K. Cheemplavam" <prakashkc@gmx.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: white phoenix <white.phoenix@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: nforce2 bugs?
Date: Thu, 30 Sep 2004 11:25:55 +0200 [thread overview]
Message-ID: <415BD123.8020608@gmx.de> (raw)
In-Reply-To: <1096496263.16768.12.camel@localhost.localdomain>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Alan Cox schrieb:
| On Mer, 2004-09-29 at 23:42, white phoenix wrote:
|
|>[x86] fix lockups with APIC support on nForce2
|
|
| Looks reasonable (anyone from Nvidia care to ack any of these)
As far as I could see, none of the posted patches are needed, or rather
the correct one(s) is already included in the kernel. The older ones
were workarounds, not needed anymore, thus obsolete.
The only problem is the apic timer thing. It just gets activated if the
correct BIOS Version is found (see the dmi scan thingie). So I just pass
acpi_skip_timer_override to the kernel to be sure.
|>Add PCI quirk to disable Halt Disconnect and Stop Grant Disconnect
|>(based on athcool program by Osamu Kayasono).
|
|
| Is this always safe - if not why does the BIOS not do it.
It is safe but makes your CPU hotter. Thus the real fix just changes the
disconnect intervall (or alike). Look into arch/i386/pci/fixup.h and
search for nforce2.
Prakash
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBW9EjxU2n/+9+t5gRAhKPAKDHnBuJs9bN4ZeQwCa9r4hu3woTcgCfbWmB
4yz7q8RBHXeodlkrpwYUH8w=
=Ipiu
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-09-30 9:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-29 22:42 nforce2 bugs? white phoenix
2004-09-29 22:17 ` Alan Cox
2004-09-30 0:32 ` white phoenix
2004-09-30 9:25 ` Prakash K. Cheemplavam [this message]
2004-09-30 14:24 ` Maciej W. Rozycki
-- strict thread matches above, loose matches on Subject: below --
2004-09-30 15:43 Andy Currid
2004-09-30 16:59 ` Maciej W. Rozycki
2004-10-01 3:41 ` Ross Dickson
2004-10-01 11:16 ` Jesse Stockall
2004-10-02 2:13 Jesse Allen
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=415BD123.8020608@gmx.de \
--to=prakashkc@gmx.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=white.phoenix@gmail.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