> What about swap memory?
No swap.
-marco
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T68f44cf88ca61ff3-M3f20653e6d91dd306ae7752f
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
> Not to be a pain, but did you run it for at least 12 hours?
No.
But I did run 4 iterations, which took about 5 hours.
-marco
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T68f44cf88ca61ff3-Mfe0ec20cf84cbc0273833982
Delivery options:
What about swap memory?
I wonder, why the process works, if slowed down by manual scrolling.
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T68f44cf88ca61ff3-M208a397f8c49e88256d1dacf
Delivery options: https://9fans.topicbox.com/groups/9
> I did run MemTest86, which passed; no errors.
Not to be a pain, but did you run it for at least 12 hours?
Sadly, it can take that long or longer to uncover a marginal
module. A really-horribly-bad module will fail in the first
run, but you may not be that "lucky".
Dave Eckhardt
--
Error during compiling:
rc 718: suicide: sys: trap: fault read addr=0x965708 pc=0xb5d9
mk: 8c -FTVw mtrr.c : exit status=rc 718: sys: trap: fault read
addr=0x965708 pc=0xb5d9
acid:
term% acid 718
/proc/718/text:386 plan 9 executable
/sys/lib/acid/p
Have you looked at the crashed binary in acid, and checked if the
PC seems to be pointing at something sensible? Do you get a sane
stack trace?
Can you post it?
Quoth Marco Feichtinger :
> Thanks for the help guys, but unfortunately I couldn't figure it out yet.
>
> I did run MemTest86, which pa
Thanks for the help guys, but unfortunately I couldn't figure it out yet.
I did run MemTest86, which passed; no errors.
I also tried a different RAM module, but got the same error.
The timestamp of the libraries in /386/lib looks fine.
> To avoid such problems while rebuilding kernels + librari
