From owner-freebsd-questions Thu Sep 10 20:13:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA29245 for freebsd-questions-outgoing; Thu, 10 Sep 1998 20:13:19 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from post.mail.demon.net (post-12.mail.demon.net [194.217.242.41]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA29234 for ; Thu, 10 Sep 1998 20:13:15 -0700 (PDT) (envelope-from tonydl@the-coolpad.demon.co.uk) Received: from [194.222.65.225] (helo=the-coolpad.demon.co.uk) by post.mail.demon.net with smtp (Exim 2.02 #1) id 0zHJdw-0005tk-00 for freebsd-questions@FreeBSD.ORG; Fri, 11 Sep 1998 03:13:04 +0000 Message-ID: Date: Fri, 11 Sep 1998 04:12:00 +0100 To: freebsd-questions@FreeBSD.ORG From: Tony Dunn-Lowes Subject: cc: Internal compiler error URGENT MIME-Version: 1.0 X-Mailer: Turnpike (32) Version 4.00 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG HELP 1. I have just nuked my 2.2.5 system and reinstalled with 2.2.7 -RELEASE only to find that nearly every time I attempt to compile an application or upgrade I get ... cc: Internal compiler error: program cc1 got fatal signal 11 ... or similar. 2. Also... if several "ls -la" commands are executed in succession then you would get an error and core dump. 3. And... If a terminal screen is left for a few minutes (without activity) it will result in a disconnection (without warning) I have tried disabling the CPU cache (which has seemed to improve problem 2) but it hasn't solved the problems. I have also replaced the RAM. Machine Profile ... 32MB RAM, P133, Diamond Stealth 2000, SpeedEasy QDI Motherboard. I have heard that this set of problems could be due to the CPU type. Is this true ? Regards Tony --- Tony Dunn-Lowes To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message