Hi I get the same behaviour on my T30. Although the indications for a hardware problem are very strong, I am not yet convinced that this really is one. My suspicion is that there are problems with current (as well with 5.1 and probably 5.0) with power management that will result in overheating, which will then look like a hardware problem. I am currently running continuous buildworlds on stable, and so far they all succeeded. This is what is left to do: run buildworld on current or 5.1 until it fails a couple of times with the below errors, then reboot to 4.8 and run a few buildworlds. if they also fail -> hardware problem very likely if they do not fail -> run again a few buldworlds on current. if these fail again -> software problem very likely could you please also set up this test scenario and report the outcome? my results will be available some time tomorrow thanks, t. On Thu, Jun 26, 2003 at 08:54:07PM +1000, peter wrote: > Hi > > I receive signals 4, 10, and 11 during my buildworlds. Just put in > another PSU: same problem. Checking memory next... > > Christoph Kukulies wrote: > > >I tried to sync my source tree and build the world. Yesterday > >world build failed. Today it seemd to get further but still failed > >with signal 4 (SIGILL !?) > > > >cd /usr/include/fs/fdescfs; for h in *.h; do if [ -L $h ]; then rm -f > >$h; fi; done > >cd /usr/include/fs/fifofs; for h in *.h; do if [ -L $h ]; then rm -f $h; > >fi; done > >cd /usr/include/fs/msdosfs; for h in *.h; do if [ -L $h ]; then rm -f > >$h; fi; done > >cd /usr/include/fs/ntfs; for h in *.h; do if [ -L $h ]; then rm -f $h; > >fi; done > >cd /usr/include/fs/nullfs; for h in *.h; do if [ -L $h ]; then rm -f $h; > >fi; done > >*** Signal 4Received on Thu Jun 26 2003 - 01:19:53 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:13 UTC