 |
| Prev-20 | Home | Next-20 |
| Prev-20 | Home | Next-20 |
| Prev-Msg | Prev-Thread | Suse-linux-e | May-2008 | Next-Thread | Next-Msg |
| Subject: | Re: [opensuse] Unstable system - culprit identified |
| Group: | Suse-linux-e |
| From: | David C. Rankin |
| Date: | 6 May 2008 |
> Per Jessen wrote:
>> David C. Rankin wrote:
>>> Per Jessen wrote:
>>>> Hi David
>>>>
>>>> I think I did reply (a little late though) on-list, but it seems to me
>>>> that the key thing is that you're not doing anything to provoke the
>>>> lockups.
>>>>
>>> Per,
>>>
>>> I have been doing a little more investigation under the guidance of,
>>> and with the help of, master kernel builder, Sir Engelhardt. (I hope I
>>> remembered that right ;-)
>>
>> Nope, I'm sure he's German so he can't be a Sir - maybe a Herr? - sounds
>> very similar :-)
>>
>>> One issue that looks promising as the culprit is the nvidia module.
>>> Were you by chance also loading the nvidia module on your Gigabyte
>>> system? What video card were you using?
>>
>> No, I've got an ATI Radeon card and I'm using the AMD drivers.
>>
>>> Also, what is a good torture test to run to see if I can make the
>>> system lock. IIRC you were using mprime. Any other simple ones you know
>>> of? Thanks.
>>
>> mprime is the best stress test I know. It just seems to be able to get
>> into all the corners where you'd normally never go.
>>
>>
>> /Per
>>
>
> Well we have plenty of mcelog errors before removing the nvidia driver
> and using the stock "nv" driver, we have not seen any since. That's
> running mprime while running XP with it downloading and installing
> updates as well. The combination of removing the nvidia driver and
> passing "acpi_use_timer_override" seems to have taken care of 99% of the
> problem. However the mce errors are hardware errors, so it looks like
> the nvidia 8600GT card causes real problems when the full proprietary
> nvidia kernel module is loaded. Hmm, no more compiz until this is resolved.
>
> Thanks for your response
>
For those of you that recall the thread, I thought I would provide the list
with a closing chapter in the MCE hell I went through with the latest Tyan
S2856ANRF and Opteron 180 box I built. After struggling for weeks with "machine
check events" and replacing virtually everything in the box, trying both nVidia
and ATI video cards (with and without the propriety drivers), rma'ing the ram
back to OCZ, I finally rma'ed the motherboard back to Tyan on 4/12.
I received a replacement (not new) board back last Friday and rebuilt the
system. So far it has been running without a single mce through all matters or
torture. (mprime -t, etc.) The primary torture that would cause mce's before
replacement was accessing a vnc session and starting virtual box with a copy of
winXP running across the remote vnc session. That works just fine now without a
singe mce.
So I guess, case closed. It was a faulty motherboard. Thanks again for all
those that helped with the diagnosis.
--
David C. Rankin, J.D., P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com
--
To unsubscribe, e-mail: opensuse+unsubscribe
For additional commands, e-mail: opensuse+help
| Prev-Msg | Prev-Thread | Suse-linux-e | May-2008 | Next-Thread | Next-Msg |