Messages in this thread | | | Date | Fri, 12 Sep 97 23:37 MET DST | From | (Hans-Joachim Baader) | Subject | Re: pre-patch-2.0.31-9 OOPSs |
| |
In article <m0x920i-000CdYC@nevets.oau.org> you write: >Someone mentioned that my old gcc (2.7.2) might be the cause of my OOPS's, >so today I compiled the kernel on a RedHat 4.2 machine with gcc 2.7.2.1, >and of course, I got a huge oops as soon as I started up trn. I'm running >inn 1.5.1-6 and trn locally. Inn is fed via rnews via uucp batch. [...] >Meanwhile, my system has locked up when I wasnt home several times, so >I'd declare at least this patched version of 2.0.31 very unstable. I
Hmm, this is just a wild guess, but take the following rule into account:
RULE 1. If your system appears very unstable, try slower DRAM timings.
hjb
-- Uncle Ed's Rule of Thumb: Never use your thumb for a rule. You'll either hit it with a hammer or get a splinter in it.
| |