Message boards :
Technical News :
Horizontal Hold (Jun 14 2007)
Message board moderation
Previous · 1 · 2
Author | Message |
---|---|
Pepo Send message Joined: 5 Aug 99 Posts: 308 Credit: 418,019 RAC: 0 |
One theory is the bad CPU screwed up the previous kernel, which might explain why it suddenly had problems when it was fine for weeks before that. Then again.. how does a bad CPU permanently screw up a kernel image? Quite possible - some years ago our Win server had one buggy (non-ECC) memory module. After a sudden crash, a plenty of files in C:\\WINDOWS\\system32\\ (and somewhere else too) got some errorneous characters (more exactly, few bits) in their names and the system refused to boot. The solution was to locate and replace the bad memory module, install the same system on some other machine, compare the directory trees and rename the broken file names - everything was then running fine. Peter |
Dr. C.E.T.I. Send message Joined: 29 Feb 00 Posts: 16019 Credit: 794,685 RAC: 0 |
One theory is the bad CPU screwed up the previous kernel, which might explain why it suddenly had problems when it was fine for weeks before that. Then again.. how does a bad CPU permanently screw up a kernel image? [off topic] Welcome back to the Boards Peter . . . ;O [on topic] BOINC Wiki . . . Science Status Page . . . |
Scarecrow Send message Joined: 15 Jul 00 Posts: 4520 Credit: 486,601 RAC: 0 |
Are Scarecrow's cowboys capable of handling both types of endians? Tell the big ones to line up, and the little ones to bunch up.... we'll whoop 'em all. How's it going, Peter? |
Pepo Send message Joined: 5 Aug 99 Posts: 308 Credit: 418,019 RAC: 0 |
Are Scarecrow's cowboys capable of handling both types of endians? I see you have them under controll. How's it going, Peter? Yippeeeeeee! Less time recently for virtual life, just scratching some projects' boards. But still enough interest for the area. Peter |
KWSN THE Holy Hand Grenade! Send message Joined: 20 Dec 05 Posts: 3187 Credit: 57,163,290 RAC: 0 |
[snip] One possibility is that the "bad" CPU overwrote part of the kernal in memory, in a "swapping" module (it comes into memory and gets re-written to disk, repeatedly) and the error propigated (like, maybe, it was a disk drive driver routine...) I've seen this happen, in my experience. (in much older OS's - IBM's DOS/MS, OSMVT, etc.) Finding the cause was always frustrating, and quite slow... . Hello, from Albany, CA!... |
Uioped1 Send message Joined: 17 Sep 03 Posts: 50 Credit: 1,179,926 RAC: 0 |
[snip] Also remember that software raid is the norm there, (a conscious decision.) |
Matt Lebofsky Send message Joined: 1 Mar 99 Posts: 1444 Credit: 957,058 RAC: 0 |
Also remember that software raid is the norm there, (a conscious decision.) In this case, hardware RAID. There's no "norm" as much as what works best with what we got. - Matt -- BOINC/SETI@home network/web/science/development person -- "Any idiot can have a good idea. What is hard is to do it." - Jeanne-Claude |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.