Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 14 Dec 2001 11:12:59 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 14 Dec 2001 11:12:50 -0500 Received: from tartarus.telenet-ops.be ([195.130.132.34]:29334 "EHLO tartarus.telenet-ops.be") by vger.kernel.org with ESMTP id ; Fri, 14 Dec 2001 11:12:35 -0500 Date: Fri, 14 Dec 2001 17:12:29 +0100 From: Sven Vermeulen To: Linux-Kernel Development Mailinglist Subject: Resolved (was Re: 2.4.17-rc1 doesn't boot (on K6-II)) Message-ID: <20011214171229.A513@Zenith.starcenter> Mail-Followup-To: Linux-Kernel Development Mailinglist In-Reply-To: <20011214164301.A512@Zenith.starcenter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011214164301.A512@Zenith.starcenter>; from sven.vermeulen@rug.ac.be on Fri, Dec 14, 2001 at 04:43:01PM +0100 X-Operating-System: Linux 2.4.17-rc1 X-Telephone: +32 486 460306 X-Requested: Beautiful, smart and Linux-lovin' girlfriend Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Dec 14, 2001 at 04:43:01PM +0100, Sven Vermeulen wrote: > When booting 2.4.17-rc1, the following text appears: [...] A kernel compiled with a different gcc went very well. I found it strange that the gcc I previously used (which I always use for compiling) gave that error, so I recompiled it with that compiler and rebooted... which went alright. I can only guess what has mishappened. My /boot was full, but I hardly think this was the problem. Oh well, it goes well now, no need to complain, do I? ;-) Sven Vermeulen -- panic("Foooooooood fight!"); ~(In the kernel source aha1542.c, after detecting a bad segment list.) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/