The gcc update just failed to compile on one of my systems with a
segfault, but then succeeded after trying again even though I didn't
change anything. Does that indicate a hardware problem for sure?
Should I run memtester? Any other tests to run? Nothing in dmesg.
- Grant
On Thu, Feb 23, 2012 at 2:17 PM, Grant emailgr...@gmail.com wrote:
The gcc update just failed to compile on one of my systems with a
segfault, but then succeeded after trying again even though I didn't
change anything. Does that indicate a hardware problem for sure?
Should I run memtester?
On Thu, Feb 23, 2012 at 11:17 AM, Grant emailgr...@gmail.com wrote:
The gcc update just failed to compile on one of my systems with a
segfault, but then succeeded after trying again even though I didn't
change anything. Does that indicate a hardware problem for sure?
Should I run memtester?
On Thu, Feb 23, 2012 at 2:28 PM, Mark Knecht markkne...@gmail.com wrote:
On Thu, Feb 23, 2012 at 11:17 AM, Grant emailgr...@gmail.com wrote:
The gcc update just failed to compile on one of my systems with a
segfault, but then succeeded after trying again even though I didn't
change anything.
On Thu, 23 Feb 2012 11:17:54 -0800
Grant emailgr...@gmail.com wrote:
The gcc update just failed to compile on one of my systems with a
segfault, but then succeeded after trying again even though I didn't
change anything. Does that indicate a hardware problem for sure?
Should I run memtester?
The gcc update just failed to compile on one of my systems with a
segfault, but then succeeded after trying again even though I didn't
change anything. Does that indicate a hardware problem for sure?
Should I run memtester? Any other tests to run? Nothing in dmesg.
Not definitively
On Thu, Feb 23, 2012 at 11:36 AM, Michael Mol mike...@gmail.com wrote:
On Thu, Feb 23, 2012 at 2:28 PM, Mark Knecht markkne...@gmail.com wrote:
On Thu, Feb 23, 2012 at 11:17 AM, Grant emailgr...@gmail.com wrote:
The gcc update just failed to compile on one of my systems with a
segfault, but
The gcc update just failed to compile on one of my systems with a
segfault, but then succeeded after trying again even though I didn't
change anything. Does that indicate a hardware problem for sure?
Should I run memtester? Any other tests to run? Nothing in dmesg.
- Grant
Nah, most
On Thu, 23 Feb 2012 11:47:03 -0800, Grant wrote:
Parallel builds are not deterministic so if the Makefile allows a race
condition to develop it's pot luck whether you'll be hit with it or
not
I got sick of stuff like that so I run MAKEOPTS=-j1 on all of my
systems.
If it were a
Parallel builds are not deterministic so if the Makefile allows a race
condition to develop it's pot luck whether you'll be hit with it or
not
I got sick of stuff like that so I run MAKEOPTS=-j1 on all of my
systems.
If it were a frequent occurrence, there may be some benefit in that.
The gcc update just failed to compile on one of my systems with a
segfault, but then succeeded after trying again even though I didn't
change anything. Does that indicate a hardware problem for sure?
Should I run memtester? Any other tests to run? Nothing in dmesg.
Not definitively
On Thu, Feb 23, 2012 at 1:11 PM, Grant emailgr...@gmail.com wrote:
SNIP
mprime ran for about 1.5 hours until it found this:
[Work thread Feb 23 13:04] FATAL ERROR: Rounding was 0.5, expected less than
0.4
[Work thread Feb 23 13:04] Hardware failure detected, consult stress.txt file.
[Work
Grant writes:
I have a 1200 watt Corsair power supply and my temps are very low even
during the stress test so I'm thinking bad (Corsair) RAM. I should
remove modules one at a time and re-test to narrow it down?
This sounds just like the right thing to do. Well, if you have four RAM
chips,
On Thu, 23 Feb 2012 11:46:03 -0800
Mark Knecht markkne...@gmail.com wrote:
Whenever I get build failures with the load-adaptive MAKEOPTS and
EMERGE_DEFAULT_OPTS, I check the build log to see if it's relatively
obvious that something was depended upon before it was built. If
so, I file a
On Thu, Feb 23, 2012 at 4:00 PM, Grant emailgr...@gmail.com wrote:
Parallel builds are not deterministic so if the Makefile allows a race
condition to develop it's pot luck whether you'll be hit with it or
not
I got sick of stuff like that so I run MAKEOPTS=-j1 on all of my
systems.
If
15 matches
Mail list logo
