Re: IO-APIC on nforce2 [PATCH] + [PATCH] for nmi_debug=1 + [PATCH]for idle=C1halt, 2.6.5
From: Prakash K. Cheemplavam
Date: Tue May 04 2004 - 03:30:27 EST
Bartlomiej Zolnierkiewicz wrote:
On Tuesday 04 of May 2004 00:09, Allen Martin wrote:
I'm happy to be able to make this information public to the Linux
community. This information has been previously released to BIOS /
board vendors as an appnote, but in the interest of getting a workaround
into the hands of users the quickest we're making it public for possible
inclusion into the Linux kernel.
This is a great news! Below is an untested patch to address this issue.
Yes it works!!!! Finally the nforce2 issue has been fixed. I still can't
believe it.
Dear Allen, it is nice that after all Nvidia decided to give out
information about this issue. I would have been so nice, if this had
been doen about 6 months ago, where I originally discovered the
connection between apic instability and cpu disconnect. But I guess I
shouldn't scold Nvidia but the mainboard manufacturers who were still
sleeping, like in my case: Abit. Till today the didn't manage to fix
this issue and the timer issue (and they released a new bios a few days
ago...)
Maybe Nvidia should scold the board manufacturers to keep their bioses
updated. After all it is Nvidia getting a bad image if everybody thinks
"Nvidia boards are unstable and they don't care to resplve it." So it
would be in Nvidia's own interest to push the manufacturers to integrate
such critical fixes ASAP.
The only issues left for me are
a) semi-stable nvidia binary driver
b) higher idle temperature with nvidia driver (I guess). I may also be a
sensors probelm as Abit's reading is known as not to be very precise and
read something else after every reboot thanks to new recalibration.
c) missing driver for nforce2 apu...
Thanx after all.
Prakash
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/