CyberOrg wrote:
On Tue, May 6, 2008 at 11:47 AM, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
So I guess, case closed. It was a faulty motherboard. Thanks again for all those that helped with the diagnosis.
That is what was told to you when the bug was closed, you should have listened then and saved everyone time, including valuable time kernel developers like GKH wasted on that bug[1]
Logs don't lie and devs closing bugs know what they are doing ;)
Cheers
-J
That's precisely what I did. I'm sure the last time you had mce problems, you knew right off the bat that it was the motherboard, not the memory, not the memory controller, not the software that CAN incorrectly flag mces, not the video hardware or driver, etc.... I tore every piece of hardware apart on this machine. Surely you're not saying I ignored the possibility it was hardware, are you? The devs were right this time and I graciously told them so. See: https://bugzilla.novell.com/show_bug.cgi?id=376165. However, that it not always the case as we learned in spades pulling back the ugly cover on the mce error reporting scheme. -- 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@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org