From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265376AbUGDDXP (ORCPT ); Sat, 3 Jul 2004 23:23:15 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265383AbUGDDXP (ORCPT ); Sat, 3 Jul 2004 23:23:15 -0400 Received: from colin2.muc.de ([193.149.48.15]:8965 "HELO colin2.muc.de") by vger.kernel.org with SMTP id S265376AbUGDDXO (ORCPT ); Sat, 3 Jul 2004 23:23:14 -0400 Date: 4 Jul 2004 05:23:12 +0200 Date: Sun, 4 Jul 2004 05:23:12 +0200 From: Andi Kleen To: Jeff Garzik Cc: linux-kernel@vger.kernel.org Subject: Re: Weird: 30 sec delay during early boot Message-ID: <20040704032312.GA90194@muc.de> References: <2e55c-392-7@gated-at.bofh.it> <40E7710A.4020601@pobox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40E7710A.4020601@pobox.com> User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > would early printk show something that dmesg(8) would not? Yes, it's real time and you can see where the delay occurs. -Andi