public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jim owens <jowens@hp.com>
To: Martin Knoblauch <knobi@knobisoft.de>
Cc: Matthew Wilcox <matthew@wil.cx>,
	Kay Sievers <kay.sievers@vrfy.org>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	efault@gmx.de, viro@zeniv.linux.org.uk, rjw@sisk.pl,
	linux-kernel@vger.kernel.org, shemminger@vyatta.com,
	mike.miller@hp.com, linux-pci@vger.kernel.org
Subject: Re: Analyzed/Solved/Bisected: Booting 2.6.30-rc2-git7 very slow
Date: Sun, 21 Jun 2009 09:50:06 -0400	[thread overview]
Message-ID: <4A3E3A8E.4030703@hp.com> (raw)
In-Reply-To: <619506.56238.qm@web32605.mail.mud.yahoo.com>

Martin Knoblauch wrote:
> 
>  How do you get to see the debug-output from initrd? I never managed that.

I did all my boot testing from ILO with VSP for a serial console.

jim

  reply	other threads:[~2009-06-21 13:50 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-27 11:25 Analyzed/Solved/Bisected: Booting 2.6.30-rc2-git7 very slow Martin Knoblauch
2009-05-27 20:31 ` Andrew Morton
2009-05-27 20:56   ` Kay Sievers
2009-05-28  9:14     ` Martin Knoblauch
2009-06-16 19:25       ` Jesse Barnes
2009-06-17  8:35         ` Martin Knoblauch
2009-06-20 16:37           ` jim owens
2009-06-20 16:58             ` Matthew Wilcox
2009-06-20 18:19               ` Kay Sievers
2009-06-20 18:26                 ` Matthew Wilcox
2009-06-20 18:36                   ` Kay Sievers
2009-06-20 19:06                     ` Matthew Wilcox
2009-06-20 21:17                       ` jim owens
2009-06-21 10:57                         ` Martin Knoblauch
2009-06-21 13:50                           ` jim owens [this message]
2009-06-21 10:54             ` Martin Knoblauch
  -- strict thread matches above, loose matches on Subject: below --
2009-05-20 11:01 Martin Knoblauch
2009-04-24 12:45 Analyzed/Solved: " Martin Knoblauch
2009-04-29  1:28 ` Andrew Morton
2009-04-29  3:51   ` Mike Galbraith
2009-04-29  8:17     ` Andrew Morton
2009-04-29 12:08       ` Al Viro
2009-04-29 14:18         ` Mike Galbraith
2009-05-05 22:49           ` Andrew Morton
2009-05-06  4:45             ` Mike Galbraith
2009-05-06  7:55               ` Martin Knoblauch
2009-05-06  8:37                 ` Mike Galbraith
2009-05-20 10:22                   ` Analyzed/Solved/Bisected: " Martin Knoblauch
2009-05-27  6:31                     ` Andrew Morton
2009-05-27  9:14                       ` Martin Knoblauch
2009-05-27 11:21                       ` Matthew Wilcox
2009-05-27 11:53                         ` Martin Knoblauch
2009-05-27 18:07                           ` jim owens
2009-05-27 18:18                             ` Miller, Mike (OS Dev)
2009-05-27 20:12                               ` jim owens
2009-05-27 21:18                                 ` Miller, Mike (OS Dev)
2009-05-28  8:59                               ` Martin Knoblauch
2009-05-28 19:01                                 ` Miller, Mike (OS Dev)
2009-05-28 20:48                                   ` Martin Knoblauch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A3E3A8E.4030703@hp.com \
    --to=jowens@hp.com \
    --cc=akpm@linux-foundation.org \
    --cc=efault@gmx.de \
    --cc=jbarnes@virtuousgeek.org \
    --cc=kay.sievers@vrfy.org \
    --cc=knobi@knobisoft.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=mike.miller@hp.com \
    --cc=rjw@sisk.pl \
    --cc=shemminger@vyatta.com \
    --cc=viro@zeniv.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox