Working nforce2, was Re: Fixes for nforce2 hard lockup, apic, io-apic, udma133 covered
<snip>
Quoted 10 lines
Quoted 10 lines
I decided to wait till this morning, to try the BIOS "C1 Disconnect" set to enabled. Still no lockups under this kernel. Tried a vanilla kernel, no lockups (but timer and watchdog messed up still). Now that I read your message Bob, I understand what you are saying. Luckily, the updated BIOS changelog states "Add C1 disconnect item." And this exact version seems to have fixed it, and now we have an exact fix (another one?) to refer to.
So the fix was absolutely a BIOS fix.
<snip>
==That's why I'm trying to contact shuttle.
Jesse
Good Work Jesse, I hope shuttle give up some info - especially as I have pheonix bioses and they are doing ?? about it?
Quoted 6 lines
...but we're stuck looking at smoke and mirrors, when the kernel might be able to work around bioses that have not been "updated". Or to put it another way, "voodoo" may be done by kernel if not done by bios. Whatever is being tweaked may be accessible to kernel code.
<snip>
Bob
Please ignore the following if you are already up to speed on SMM. Some readers may not know why we cannot do all that the bios can do aside from a lack of information.
Agreed but the keywords are might and may. I remember doing dos based data acquisition with 486SX laptops and then Intel brought out the 486Sl and our pulse counting went bad because of the power saving core. I got the data book from Intel and was very dismayed to see that bios code was being executed when I thought our code was running and there was not a darn thing I could do about it and keep the laptop warranty intact.
Its offspring as you may already know is SMM. It is a priviledged mode that we can do pretty much squat about. It can pop up anywhere in the middle of our code and the only thing we will know about it aside from missing time is when it has stuffed something up - like setting registers back to the wrong values. Think of it like a kernel within our kernel with permissions set so it can hack us but we cannot hack it.
Maciej recently writes of its continuing effect on NMI debug here.
http://linux.derkeiler.com/Mailing-Lists/Kernel/2003-12/2940.html
Regards
Ross.
Quoted 10 lines · Ross Dickson
Quoted 4 lines
Quoted 4 lines
So the fix was absolutely a BIOS fix.
<snip>
==That's why I'm trying to contact shuttle.
Jesse
R> Good Work Jesse, I hope shuttle give up some info - especially as I have pheonix bioses and they are doing ?? about it? -Ross
B> I was expecting to hear that.
I have an Award bios on MSI nforce2 mboard. Their bios flash file begins with
"w" for Award w6570nms.760(W6570 v760 bios flash file) "p" phoenix
"a" ami
also appears at boot but goes by in a flash
and appears on first cmos setup page
So Award bios has a fix for the nforce2.
How about Jesse's bios that can fix the
problem without a kernel patch, as my
Award bios is doing? What kind of bios
is that you have, Jesse?
My Award bios does not make any way for
me to have ioapic edge timer turn on,
though. I need a patch to get that on.
Also I don't have a cpu disconnect choice in
setup and by running temp range 41C to 48C
I guess cpu disconnect is not on. 48C once in
a while does not hurt anything though. -Bob
Quoted 21 lines
Quoted 3 lines
...but we're stuck looking at smoke and mirrors, when the kernel might be able to work around bioses that have not been "updated". Or to put it another way, "voodoo" may be done by kernel if not done by bios. Whatever is being tweaked may be accessible to kernel code.
<snip>
BobPlease ignore the following if you are already up to speed on SMM. Some readers may not know why we cannot do all that the bios can do aside from a lack of information.
Agreed but the keywords are might and may. I remember doing dos based data acquisition with 486SX laptops and then Intel brought out the 486Sl and our pulse counting went bad because of the power saving core. I got the data book from Intel and was very dismayed to see that bios code was being executed when I thought our code
was running and there was not a darn thing I could do about it and keep the
laptop warranty intact.Its offspring as you may already know is SMM. It is a priviledged mode that we can
do pretty much squat about. It can pop up anywhere in the middle of our code and the only thing we will know about it aside from missing time is when it has stuffed something up - like setting registers back to the wrong values. Think of
it like a kernel within our kernel with permissions set so it can hack us but we
cannot hack it.
Quoted 9 lines
Maciej recently writes of its continuing effect on NMI debug here.
http://linux.derkeiler.com/Mailing-Lists/Kernel/2003-12/2940.html
Regards
Ross
Thanks for explaining. We got some new functionality just by turning nmi_watchdog on but I don't know if anybody has learned anything from the extra debug
have they, as far as this nforce2 timing thing? -Bob