Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263255AbTIAT5J (ORCPT ); Mon, 1 Sep 2003 15:57:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263258AbTIAT5J (ORCPT ); Mon, 1 Sep 2003 15:57:09 -0400 Received: from smtp02.fuse.net ([216.68.1.133]:435 "EHLO smtp02.fuse.net") by vger.kernel.org with ESMTP id S263255AbTIAT5H (ORCPT ); Mon, 1 Sep 2003 15:57:07 -0400 From: "Dale E Martin" Date: Mon, 1 Sep 2003 15:57:06 -0400 To: linux-kernel@vger.kernel.org Subject: Re: repeatable, hard lockup on boot in linux-2.6.0-test4 (more details) Message-ID: <20030901195706.GA853@cliftonlabs.com> References: <20030901182359.GA871@cliftonlabs.com> <20030901120412.2047eeff.akpm@osdl.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030901120412.2047eeff.akpm@osdl.org> User-Agent: Mutt/1.5.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1029 Lines: 30 > Are you able to plug any PS/2 devices into the machine, see if that makes > a difference? Yes, plugging in a PS/2 mouse in addition to the USB mouse does allow the machine to boot up. (Just tried it, thanks for the suggestion.) > Also it would be useful to add the option "initcall_debug" to the kernel > boot command line. Then you will see a bunch of messages of the form > > calling initcall 0xNNNNNNNN > > Please look up the final address in the System.map file from the 2.6 build. > This will give us an idea of what the machine was trying to do when it > died. It was in "i8042_init". Thanks again for the help. Take care, Dale -- Dale E. Martin, Clifton Labs, Inc. Senior Computer Engineer dmartin@cliftonlabs.com http://www.cliftonlabs.com pgp key available - 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/