5.2 RC2: Semi-deterministic gcc segfault during buildworld

From: Peter Schuller (peter.schuller_at_infidyne.com)
Date: 01/01/04

  • Next message: Haidong Xia: "Problem with loading another pci driver for the same card" 
    To: freebsd-questions@freebsd.org
Date: Thu, 1 Jan 2004 02:55:23 +0100

    Hello,

    I had just installed a fresh 5.2 RC2 system and cvsup:ed the latest source
    (only 5-10 files changed; nothing related to this problem as far as I could
    see). I wanted to add Coda client support. so I created a GENERIC derivative
    configuration with Coda support added. I proceeded to compile as usual:

       make cleandir && make cleandir && make buildkernel KERNCONF=WHITESTAR

    However every time I do this I encounter the exact same problem:

    /usr/src/sys/dev/aic7xxx/aic79xx.c: In function `ahd_handle_scsiint':
    /usr/src/sys/dev/aic7xxx/aic79xx.c:1719: internal compiler error: Segmentation
    fault
    Please submit a full bug report,
    with preprocessed source if appropriate.
    See <URL:http://gcc.gnu.org/bugs.html> for instructions.
    *** Error code 1

    Except for once when I got this instead:

    /usr/src/sys/pci/if_dc.c: In function `dc_init':
    /usr/src/sys/pci/if_dc.c:3593: internal compiler error: Segmentation fault
    Please submit a full bug report,
    with preprocessed source if appropriate.
    See <URL:http://gcc.gnu.org/bugs.html> for instructions.
    *** Error code 1

    I've been running some memtests on the machine and so far no problems have
    been reported. Besides I would expect memory related problems to be much more
    random than the above.

    The same hardware (minus a new disk) has been running FreeBSD 4.x without
    problems for quite a while before this. I tried booting back into 4.9-RELEASE
    to recompile the kernel - it completed successfully.

    I have also tried some rudimentary write/read/md5sum tests on the disk used
    for 5.2 to try to determine if there are random read errors on the drive
    (which has happened to me before on one disk).

    Has anyone seen this? Could it be a hardware problem in spite of the above? 

    -- 
/ Peter Schuller, InfiDyne Technologies HB
PGP userID: 0xE9758B7D or 'Peter Schuller <peter.schuller@infidyne.com>'
Key retrieval: Send an E-Mail to getpgpkey@scode.org
E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
  • Next message: Haidong Xia: "Problem with loading another pci driver for the same card"

    Relevant Pages

    • RAID1 not save my system in case disk failure
      ... After dropping I/O operations on disk chained to ... Waiting Queue entries: ... Disconnected Queue entries: ... Please file a bug report against this driver. ...
      (Linux-Kernel)
    • Re: XP will not start
      ... then the disk checking will run. ... not boot to Windows, boot from the cd again, then from the start menu got to ... > I choose I get a blue screen saying windows has shut down to protect the ... > Can't get past blue screen, any idea what the error code means. ...
      (microsoft.public.windowsxp.help_and_support)
    • Re: RELENG_6 does not compile
      ... martinko wrote: ... Please submit a full bug report, ... *** Error code 1 ... But in a laptop it could be related to heat such as a clogged heatsink ...
      (freebsd-stable)
    • Re: A6005090 on IPL
      ... Well, I brought it back up to get the error code, and if I cycle the ... display to say "13-3" and hit Enter I get 0002. ... So you do need a console. ... It could be the removal of the disk, it will depend on whether the disk ...
      (comp.sys.ibm.as400.misc)
    • Re: service pk 2 failed
      ... Error code 0x800703e7 ... You'll then have a message saying that it needs exclusive access and will run next ... How to Perform Disk Error Checking in Windows XP ... | Try to install the update again, or request help from one of the following ...
      (microsoft.public.windowsupdate)