Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750729AbWCLWPA (ORCPT ); Sun, 12 Mar 2006 17:15:00 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750730AbWCLWO7 (ORCPT ); Sun, 12 Mar 2006 17:14:59 -0500 Received: from cfa.harvard.edu ([131.142.10.1]:62660 "EHLO cfa.harvard.edu") by vger.kernel.org with ESMTP id S1750729AbWCLWO7 (ORCPT ); Sun, 12 Mar 2006 17:14:59 -0500 Date: Sun, 12 Mar 2006 17:14:57 -0500 (EST) From: Gaspar Bakos Reply-To: gbakos@cfa.harvard.edu To: linux-kernel@vger.kernel.org Subject: 2.6.15 -- unable to open an initial console Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1298 Lines: 35 Hi, I am experimenting with the pristine 2.6.15.6 kernel on an AMD dual core CPU machine under FC3. The boot seems fine till i get to the point: Freeing unused memory ... "Warning: unable to open initial console". This is the last message, and then nothing ever happens. Maybe this message has nothing to do with the real error, but that is the last information I can grab. Everything works fine with previous kernel 2.6.13.4, except for occasional crashes under high load, which is the reason for the attempt to upgrade. I borrowed the old .config file from 2.6.13.4, and did "make oldconfig", so most of the settings must have remained the same. Then I also did a "make xconfig" just to have a better overview of what new options have appeared. The kernel compiled seemingly without any problems. By the way, when the old 2.6.13.4 kernel is booted up, there is no such warning about the console, and after the "Freeing unused memory" the next lines are: "Red HAT nash version 4.2.15 starting" ... So maybe the problem is somewhere here. Gaspar - 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/