From owner-freebsd-current@FreeBSD.ORG Fri Jul 11 12:35:15 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD08837B401 for ; Fri, 11 Jul 2003 12:35:15 -0700 (PDT) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 20FD143F85 for ; Fri, 11 Jul 2003 12:35:15 -0700 (PDT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id MUA74016; Fri, 11 Jul 2003 12:35:13 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 59F305D07; Fri, 11 Jul 2003 12:35:12 -0700 (PDT) To: Alexander Kabaev In-Reply-To: Message from Alexander Kabaev of "Fri, 11 Jul 2003 14:32:44 EDT." <20030711143244.2427e51c.ak03@gte.com> Date: Fri, 11 Jul 2003 12:35:12 -0700 From: "Kevin Oberman" Message-Id: <20030711193512.59F305D07@ptavv.es.net> cc: current@freebsd.org cc: Lukas Ertl Subject: Re: Kernel built with new GCC panics immediately X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jul 2003 19:35:16 -0000 > Date: Fri, 11 Jul 2003 14:32:44 -0400 > From: Alexander Kabaev > Sender: owner-freebsd-current@freebsd.org > > May be I am paranoid, but could you people please make sure you have > removed /usr/src/sys/i386/compile/ before rebuilding a > new kernel with GCC 3.3? > > Also, if simply removing stale file is not a culpit, I will appreciate > if you can test the patch below: I have cleaned out everything with no improvement. I have applied the patches and no improvement. My system still is seen as a 286 followed by a panic. Are we sure that this problem is the result of the new compiler? There were some other changes made last night that might really be the cause of this, although I have not done any real checking, yet. If Alexander is building with the new compiler with a few of these patches missing, that might explain why he never sees the problem. Or, worst of all, maybe an interaction of the new compiler and another patch. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634