All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <matthew.garrett@nebula.com>
To: "rja@sgi.com" <rja@sgi.com>
Cc: "lenb@kernel.org" <lenb@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"minyard@acm.org" <minyard@acm.org>,
	"rjw@rjwysocki.net" <rjw@rjwysocki.net>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH V2] Change ACPI IPMI support to "default y"
Date: Thu, 20 Feb 2014 20:16:22 +0000	[thread overview]
Message-ID: <1392927381.20109.0.camel@x230> (raw)
In-Reply-To: <20140220201458.GA7099@sgi.com>

On Thu, 2014-02-20 at 14:14 -0600, Russ Anderson wrote:

> The distro that added this change created all sorts of support
> problems.  Problems include kipmi0 spinning at 100% of cpu
> (creating a performance hit) and long boot delays (as the
> kernel tries to talk to a BMC that will never respond).
> It has been a big mess.

Why is the BMC not responding? Why is kipmi0 at 100%? Why are we not
fixing those bugs?

-- 
Matthew Garrett <matthew.garrett@nebula.com>

WARNING: multiple messages have this Message-ID (diff)
From: Matthew Garrett <matthew.garrett@nebula.com>
To: "rja@sgi.com" <rja@sgi.com>
Cc: "lenb@kernel.org" <lenb@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"minyard@acm.org" <minyard@acm.org>,
	"rjw@rjwysocki.net" <rjw@rjwysocki.net>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH V2] Change ACPI IPMI support to "default y"
Date: Thu, 20 Feb 2014 20:16:22 +0000	[thread overview]
Message-ID: <1392927381.20109.0.camel@x230> (raw)
In-Reply-To: <20140220201458.GA7099@sgi.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 626 bytes --]

On Thu, 2014-02-20 at 14:14 -0600, Russ Anderson wrote:

> The distro that added this change created all sorts of support
> problems.  Problems include kipmi0 spinning at 100% of cpu
> (creating a performance hit) and long boot delays (as the
> kernel tries to talk to a BMC that will never respond).
> It has been a big mess.

Why is the BMC not responding? Why is kipmi0 at 100%? Why are we not
fixing those bugs?

-- 
Matthew Garrett <matthew.garrett@nebula.com>
ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥

  reply	other threads:[~2014-02-20 20:16 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18 16:28 [PATCH V2] Change ACPI IPMI support to "default y" Matthew Garrett
2014-02-18 23:26 ` Rafael J. Wysocki
2014-02-18 23:15   ` Matthew Garrett
2014-02-18 23:15     ` Matthew Garrett
2014-02-18 23:35     ` Rafael J. Wysocki
2014-02-18 23:25       ` Matthew Garrett
2014-02-18 23:25         ` Matthew Garrett
2014-02-19  0:45         ` Rafael J. Wysocki
2014-02-19  0:53           ` Corey Minyard
2014-03-12 23:00     ` Pavel Machek
2014-03-12 23:22       ` Matthew Garrett
2014-03-12 23:22         ` Matthew Garrett
2014-03-13  7:22         ` Pavel Machek
2014-03-13  7:24           ` Matthew Garrett
2014-03-13  7:24             ` Matthew Garrett
2014-03-13  8:38             ` Pavel Machek
2014-03-13 13:29               ` Corey Minyard
2014-03-16  8:53                 ` Pavel Machek
2014-02-20 20:14 ` Russ Anderson
2014-02-20 20:16   ` Matthew Garrett [this message]
2014-02-20 20:16     ` Matthew Garrett
2014-02-20 20:40     ` Russ Anderson
2014-02-20 20:46       ` Matthew Garrett
2014-02-20 20:46         ` Matthew Garrett
2014-02-20 20:59         ` Russ Anderson
2014-02-20 21:00           ` Matthew Garrett
2014-02-20 21:00             ` Matthew Garrett
2014-02-20 21:28             ` Russ Anderson
2014-02-20 21:39               ` Matthew Garrett
2014-02-20 21:39                 ` Matthew Garrett
2014-02-20 22:06                 ` Russ Anderson
2014-02-20 22:26                   ` Matthew Garrett
2014-02-20 22:26                     ` Matthew Garrett
2014-02-20 22:45                     ` Russ Anderson
2014-02-20 23:09                       ` Matthew Garrett
2014-02-20 23:09                         ` Matthew Garrett
2014-02-20 23:59                         ` Russ Anderson
2014-02-21  0:13                           ` Matthew Garrett
2014-02-21  0:13                             ` Matthew Garrett
2014-02-21 16:53                             ` Russ Anderson
2014-02-21  2:17                           ` Zheng, Lv
2014-02-21 16:12                             ` Matthew Garrett
2014-02-21 16:12                               ` Matthew Garrett
2014-02-24  0:48                               ` Zheng, Lv
2014-02-24  0:48                                 ` Zheng, Lv
2014-02-21 16:33                             ` Russ Anderson
2014-02-21 13:37             ` Corey Minyard
2014-02-21 15:51               ` Matthew Garrett
2014-02-21 15:51                 ` Matthew Garrett
2014-02-21 17:12                 ` Corey Minyard
2014-02-20 21:49         ` Russ Anderson
2014-02-20 21:51           ` Matthew Garrett
2014-02-20 21:51             ` Matthew Garrett
2014-02-21  0:10   ` Rafael J. Wysocki
2014-02-20 23:01 ` Russ Anderson

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=1392927381.20109.0.camel@x230 \
    --to=matthew.garrett@nebula.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minyard@acm.org \
    --cc=rja@sgi.com \
    --cc=rjw@rjwysocki.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.