From: Corey Minyard <minyard@acm.org>
To: Daniel Drake <drake@endlessm.com>
Cc: Chris Chiu <chiu@endlessm.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Upstreaming Team <linux@endlessm.com>,
openipmi-developer@lists.sourceforge.net,
Corey Minyard <cminyard@mvista.com>
Subject: Re: [PATCH] ipmi:pci: Blacklist a Realtek "IPMI" device
Date: Tue, 13 Mar 2018 06:59:11 -0500 [thread overview]
Message-ID: <7630b31f-0b6a-6725-aac0-3c06c142d557@acm.org> (raw)
In-Reply-To: <CAD8Lp45pebxPSbPHXi_fT0Yg+mC01S12P-6cX2MWyQZwRbheMQ@mail.gmail.com>
On 03/13/2018 02:27 AM, Daniel Drake wrote:
> Hi,
>
> On Mon, Feb 26, 2018 at 10:50 AM, <minyard@acm.org> wrote:
>> From: Corey Minyard <cminyard@mvista.com>
>>
>> Realtek has some sort of "Virtual" IPMI device on the PCI bus as a
>> KCS controller, but whatever it is, it's not one. Ignore it if seen.
>>
>> Reported-by: Chris Chiu <chiu@endlessm.com>
>> Signed-off-by: Corey Minyard <cminyard@mvista.com>
>> ---
>>
>> I haven't heard anything from you on this. Here is a patch that should
>> blacklist that device, though I don't have a way to easily test it.
>> If you would prefer this, could you test it?
> Sorry for the slow response, and thanks for the patch!
>
> We have tested it here and it seems to be working fine now - the IPMI
> stuff no longer initializes system interfaces, and hence doesn't get
> in the way when going into suspend or reboot later.
Ok, thanks, I will add it with a "Tested-by" from you, if that is ok.
-corey
>
> This is a consumer desktop platform, so if some kind of IPMI
> functionality is really present in the hardware then it is not really
> going to be relevant for the ordinary user. So it should be fine to
> just ignore the hardware as you have done.
>
> Thanks
> Daniel
next prev parent reply other threads:[~2018-03-13 11:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 3:01 ipmi_si fails to get BMC ID Chris Chiu
2018-02-08 15:53 ` Corey Minyard
2018-02-09 3:09 ` Chris Chiu
2018-02-09 13:34 ` Corey Minyard
2018-02-14 2:44 ` Chris Chiu
2018-02-14 17:17 ` Corey Minyard
2018-02-20 17:52 ` Chris Chiu
2018-02-26 2:50 ` [PATCH] ipmi:pci: Blacklist a Realtek "IPMI" device minyard
2018-02-26 14:34 ` Andy Shevchenko
2018-02-26 14:48 ` Corey Minyard
2018-03-13 7:27 ` Daniel Drake
2018-03-13 11:59 ` Corey Minyard [this message]
2019-01-22 16:17 ipmi_si: 90 s delay in system start with 4.14.94, but not 4.18.6 Paul Menzel
2019-01-22 20:58 ` Corey Minyard
2019-01-23 16:25 ` Paul Menzel
2019-01-23 16:27 ` [PATCH] ipmi:pci: Blacklist a Realtek "IPMI" device Paul Menzel
2019-01-23 16:32 ` Greg KH
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=7630b31f-0b6a-6725-aac0-3c06c142d557@acm.org \
--to=minyard@acm.org \
--cc=chiu@endlessm.com \
--cc=cminyard@mvista.com \
--cc=drake@endlessm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@endlessm.com \
--cc=openipmi-developer@lists.sourceforge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®