On 10/05/2012 10:16 AM, Bjorn Helgaas wrote:
On Fri, Oct 5, 2012 at 8:54 AM, Nathan Zimmer wrote:
On 10/05/2012 09:14 AM, Joe Perches wrote:
On Fri, 2012-10-05 at 08:55 -0500, Nathan Zimmer wrote:
On 10/04/2012 11:37 AM, Joe Perches wrote:
On Thu, 2012-10-04 at 11:02 -0500, Nathan Zimmer wro
On Fri, 2012-10-05 at 09:16 -0600, Bjorn Helgaas wrote:
> On Fri, Oct 5, 2012 at 8:54 AM, Nathan Zimmer wrote:
> > On 10/05/2012 09:14 AM, Joe Perches wrote:
> >> On Fri, 2012-10-05 at 08:55 -0500, Nathan Zimmer wrote:
> >>> On 10/04/2012 11:37 AM, Joe Perches wrote:
> On Thu, 2012-10-04 at 1
On Fri, Oct 5, 2012 at 8:54 AM, Nathan Zimmer wrote:
> On 10/05/2012 09:14 AM, Joe Perches wrote:
>>
>> On Fri, 2012-10-05 at 08:55 -0500, Nathan Zimmer wrote:
>>>
>>> On 10/04/2012 11:37 AM, Joe Perches wrote:
On Thu, 2012-10-04 at 11:02 -0500, Nathan Zimmer wrote:
>
> At many o
On 10/05/2012 09:14 AM, Joe Perches wrote:
On Fri, 2012-10-05 at 08:55 -0500, Nathan Zimmer wrote:
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
On Fri, 2012-10-05 at 08:55 -0500, Nathan Zimmer wrote:
> 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 t
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 t
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 th
On 10/03/2012 05:54 PM, Bjorn Helgaas wrote:
On Tue, Oct 2, 2012 at 8:23 AM, Nathan Zimmer wrote:
Revert commit id 2c6413aee215a43b1f95e218067abcde50ccbc5e
On larger systems (256 cores+) with signifigant IO attached this single message
represents over 20% of the messages at boot.
Is this causi
On Tue, Oct 2, 2012 at 8:23 AM, Nathan Zimmer wrote:
> Revert commit id 2c6413aee215a43b1f95e218067abcde50ccbc5e
> On larger systems (256 cores+) with signifigant IO attached this single
> message
> represents over 20% of the messages at boot.
Is this causing a problem? The messages are at KERN
9 matches
Mail list logo