linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nathan Zimmer <nzimmer@sgi.com>
To: Joe Perches <joe@perches.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	<linux-kernel@vger.kernel.org>, <linux-pci@vger.kernel.org>,
	Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: [PATCH] revert "PCI: log vendor/device ID always"
Date: Fri, 5 Oct 2012 08:55:33 -0500	[thread overview]
Message-ID: <506EE6D5.4010603@sgi.com> (raw)
In-Reply-To: <1349368662.2008.20.camel@joe-AO722>

On 10/04/2012 11:37 AM, Joe Perches wrote:
> On Thu, 2012-10-04 at 11:02 -0500, Nathan Zimmer wrote:
>> At many of our customer sites the log level is set to KERN_DEBUG. It
>> helps avoid reboots due to operator impatience.  Machines this large
>> take significantly longer then typical to boot and seeing the extra
>> messages reassures them that the kernel isn't hung.
> That argues for adding some KERN_INFO "still booting" messages
> not logging unnecessary KERN_DEBUG messages.
>
>
Actually I would think that argues for reducing boot times on these 
large systems.

  reply	other threads:[~2012-10-05 13:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1349187780-25692-1-git-send-email-nzimmer@sgi.com>
2012-10-03 22:54 ` [PATCH] revert "PCI: log vendor/device ID always" Bjorn Helgaas
2012-10-04 16:02   ` Nathan Zimmer
2012-10-04 16:37     ` Joe Perches
2012-10-05 13:55       ` Nathan Zimmer [this message]
2012-10-05 14:14         ` Joe Perches
2012-10-05 14:54           ` Nathan Zimmer
2012-10-05 15:16             ` Bjorn Helgaas
2012-10-05 15:27               ` Joe Perches
2012-10-05 15:47               ` Nathan Zimmer

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=506EE6D5.4010603@sgi.com \
    --to=nzimmer@sgi.com \
    --cc=bhelgaas@google.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).