Re: -CURRENT crashes on compilling

From: Dag-Erling Smørgrav (des_at_des.no)
Date: 06/17/05

  • Next message: Peter Edwards: "Re: Towards a working "wine". [long]"
    To: Tarc <tarc@tarc.po.cs.msu.su>
    Date: Fri, 17 Jun 2005 20:17:10 +0200
    
    

    Tarc <tarc@tarc.po.cs.msu.su> writes:
    > I change my old computer to a new one (see dmesgs links below) and
    > my computer begins to crash anywhere(cc1, sh, awk, ...) with (mainly
    > page fault) very often.

    Bad hardware - most likely bad RAM, possibly a bad CPU.

    DES

    -- 
    Dag-Erling Smørgrav - des@des.no
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
    

  • Next message: Peter Edwards: "Re: Towards a working "wine". [long]"

    Relevant Pages

    • Re: random XP crashes
      ... call to the handler for a prior exception. ... double fault. ... A kernel stack overflow. ... One of three types of problems occurred in kernel-mode: Hardware ...
      (microsoft.public.windowsxp.perform_maintain)
    • Re: weird error message
      ... call to the handler for a prior exception. ... double fault. ... A kernel stack overflow. ... One of three types of problems occurred in kernel-mode: Hardware ...
      (microsoft.public.windowsxp.general)
    • Proliant 1600R Install Failure (ida + SMPng to blame?)
      ... Booting off the 5.1 boot floppies gives a page fault about 15 seconds ... to believe that this is not a hardware issue. ... I gather that the ida driver is not ready for SMPng, ...
      (freebsd-current)
    • Re: Disk troubleshooter?
      ... that may need recovery. ... hardware, ... DiskWarrior has fixed a hard disc fault for me that NDD and Disk ...
      (uk.comp.sys.mac)
    • SUMMARY: Memory channel II failures
      ... As the mc0 driver does not fail over rails automatically, I have a suspicion that the hardware is just fine and this is an IP or higher software problem. ... But with no way to prove the fault, HP service are having a hard time locating the fault. ... Does anyone know of any low-level memory channel test, similar to mc_cable, which could be run from Tru64 in order to verify whether the hardware really has failed on both rails simultaneously? ... i.e. something which doesn't rely on the mc0 device driver 'Ethernet MAC' interface, but works at a more basic level directly between servers? ...
      (Tru64-UNIX-Managers)