Skip to contentSkip to conversation

ipmi_si fails to get BMC ID

PATCH In review Chris Chiu 4 participants 12 messages Feb 8, 2018 – Mar 13, 2018 IPMI

lore
Share & tools
lore

Chris Chiu

author
#0 lore raw

Hi,
We are working with a new desktop Acer Veriton Z4640G and get
stumbled on failing to enter S3 suspend with kernel version 4.14 even the latest 4.15+. Here's the kernel log
https://gist.github.com/mschiu77/76888f1fd4eb56aa8959d76759a912bb.

    As you see, it is due to "ipmi_probe+0x430/0x430 [ipmi_si]". After

the message "ipmi_si 0000:02:00.3: There appears to be no BMC at this location" shows up, then it can really go to suspend w/o problem. Although it took around 3 mins. The IPMI device is probed from PCI and here's the output of lspci
https://gist.github.com/mschiu77/33f0372be41670d8a69c97e64f833087. The IPMI device is "02:00.3 IPMI SMIC interface [0c07]". We get stuck here because we don't really know why it took so long in try_get_dev_id() / ipmi_si_intf.c. Any suggestion about this to help us moving forward? Thanks

Chris

#1 lore raw
Quoted 5 lines · Chris Chiu

Hi,
We are working with a new desktop Acer Veriton Z4640G and get
stumbled on failing to enter S3 suspend with kernel version 4.14 even the latest 4.15+. Here's the kernel log
https://gist.github.com/mschiu77/76888f1fd4eb56aa8959d76759a912bb.

This is a little strange, nobody had reported this before.  Can you reproduce this at will, or was it a one-time thing?

Does the IPMI driver always take this long to issue that error, even if you are not entering sleep state?

And it started with 4.14, and didn't occur before then, right?

There's a bug in the PCI utils database, I submitted a report a while ago.  This is a KCS, not a SMIC interface.

It looks like the driver is trying to detect that there is a device out there and there is something that kind of works, but doesn't work completely. The interface specific code was all split out into separate files in 4.14.  It is possible the detection code got messed up in the process.  Nothing jumps out looking at the code differences, and I know it works on some PCI machines.

Assuming this is reproducible, can you send the the output of a pre-4.14 kernel?  If that doesn't make it obvious I may have to have access to the machine itself.

-corey

Quoted 13 lines
     As you see, it is due to "ipmi_probe+0x430/0x430 [ipmi_si]". After

the message "ipmi_si 0000:02:00.3: There appears to be no BMC at this location" shows up, then it can really go to suspend w/o problem. Although it took around 3 mins. The IPMI device is probed from PCI and here's the output of lspci
https://gist.github.com/mschiu77/33f0372be41670d8a69c97e64f833087. The IPMI device is "02:00.3 IPMI SMIC interface [0c07]". We get stuck here because we don't really know why it took so long in try_get_dev_id() / ipmi_si_intf.c. Any suggestion about this to help us moving forward? Thanks

Chris

author
#2 lore raw
Quoted 9 lines · Corey Minyard
Quoted 6 lines · Chris Chiu

Hi,
We are working with a new desktop Acer Veriton Z4640G and get
stumbled on failing to enter S3 suspend with kernel version 4.14 even the latest 4.15+. Here's the kernel log
https://gist.github.com/mschiu77/76888f1fd4eb56aa8959d76759a912bb.

Quoted 3 lines

This is a little strange, nobody had reported this before. Can you reproduce this
at will, or was it a one-time thing?

It can be reproduced on each reboot.

Quoted 5 lines

Does the IPMI driver always take this long to issue that error, even if you are not
entering sleep state?

Yep, it will always print "ipmi_si 0000:02:00.3: There appears to be no BMC at this
location" few minutes after boot.

Quoted 2 lines

And it started with 4.14, and didn't occur before then, right?

I haven't try pre-4.14 kernel. Will do that and update here.

Quoted 13 lines

There's a bug in the PCI utils database, I submitted a report a while ago. This is
a KCS, not a SMIC interface.

It looks like the driver is trying to detect that there is a device out there and
there is something that kind of works, but doesn't work completely. The interface
specific code was all split out into separate files in 4.14. It is possible the
detection code got messed up in the process. Nothing jumps out looking at the code differences, and I know it works on some PCI machines.

Quoted 7 lines

Assuming this is reproducible, can you send the the output of a pre-4.14 kernel? If that doesn't make it obvious I may have to have access to the machine itself.

-corey

It's an All-in-One machine so I think it would be difficult for shipment. I'll see what
I can do. Thanks for help.

Chris

Quoted 16 lines
Quoted 13 lines
     As you see, it is due to "ipmi_probe+0x430/0x430 [ipmi_si]". After

the message "ipmi_si 0000:02:00.3: There appears to be no BMC at this location" shows up, then it can really go to suspend w/o problem. Although it took around 3 mins. The IPMI device is probed from PCI and here's the output of lspci
https://gist.github.com/mschiu77/33f0372be41670d8a69c97e64f833087. The IPMI device is "02:00.3 IPMI SMIC interface [0c07]". We get stuck here because we don't really know why it took so long in try_get_dev_id() / ipmi_si_intf.c. Any suggestion about this to help us moving forward? Thanks

Chris

#3 lore raw
Quoted 16 lines · Chris Chiu
Quoted 10 lines · Corey Minyard
Quoted 5 lines · Chris Chiu

Hi,
We are working with a new desktop Acer Veriton Z4640G and get
stumbled on failing to enter S3 suspend with kernel version 4.14 even the latest 4.15+. Here's the kernel log
https://gist.github.com/mschiu77/76888f1fd4eb56aa8959d76759a912bb.

This is a little strange, nobody had reported this before. Can you reproduce this
at will, or was it a one-time thing?

It can be reproduced on each reboot.

Quoted 4 lines

Does the IPMI driver always take this long to issue that error, even if you are not
entering sleep state?

Quoted 7 lines

Yep, it will always print "ipmi_si 0000:02:00.3: There appears to be no BMC at this
location" few minutes after boot.

Quoted 2 lines

And it started with 4.14, and didn't occur before then, right?

I haven't try pre-4.14 kernel. Will do that and update here.

Ah.  It's probably still worth trying, but I doubt it will make any difference.

Are you sure there is actually an IPMI BMC installed in this system?  It might be a plug-in card that is not installed, but the interface still appears on the PCI bus.  So there is enough hardware to go part-way through the motions of being an IPMI interface, but not enough to actually work.

If there is a BMC there, do you know the register layout?  The IPMI spec has an algorithm to go through to discover some of the parameters, and the driver follows it, but IMHO it's not really very good.  I'll need to know the size of the registers, and the spacing between the registers.

-corey

Quoted 41 lines
Quoted 13 lines

There's a bug in the PCI utils database, I submitted a report a while ago. This is
a KCS, not a SMIC interface.

It looks like the driver is trying to detect that there is a device out there and
there is something that kind of works, but doesn't work completely. The interface
specific code was all split out into separate files in 4.14. It is possible the
detection code got messed up in the process. Nothing jumps out looking at the code differences, and I know it works on some PCI machines.

Quoted 7 lines

Assuming this is reproducible, can you send the the output of a pre-4.14 kernel? If that doesn't make it obvious I may have to have access to the machine itself.

-corey

It's an All-in-One machine so I think it would be difficult for shipment. I'll see what
I can do. Thanks for help.

Chris

Quoted 15 lines
Quoted 13 lines
      As you see, it is due to "ipmi_probe+0x430/0x430 [ipmi_si]". After

the message "ipmi_si 0000:02:00.3: There appears to be no BMC at this location" shows up, then it can really go to suspend w/o problem. Although it took around 3 mins. The IPMI device is probed from PCI and here's the output of lspci
https://gist.github.com/mschiu77/33f0372be41670d8a69c97e64f833087. The IPMI device is "02:00.3 IPMI SMIC interface [0c07]". We get stuck here because we don't really know why it took so long in try_get_dev_id() / ipmi_si_intf.c. Any suggestion about this to help us moving forward? Thanks

Chris

author
#4 lore raw
Quoted 43 lines · Corey Minyard
Quoted 23 lines · Chris Chiu
Quoted 10 lines · Corey Minyard
Quoted 6 lines · Chris Chiu

Hi,
We are working with a new desktop Acer Veriton Z4640G and get
stumbled on failing to enter S3 suspend with kernel version 4.14 even the latest 4.15+. Here's the kernel log
https://gist.github.com/mschiu77/76888f1fd4eb56aa8959d76759a912bb.

Quoted 3 lines

This is a little strange, nobody had reported this before. Can you reproduce this
at will, or was it a one-time thing?

It can be reproduced on each reboot.

Quoted 6 lines

Does the IPMI driver always take this long to issue that error, even if you
are not
entering sleep state?

Quoted 7 lines

Yep, it will always print "ipmi_si 0000:02:00.3: There appears to be no BMC at this
location" few minutes after boot.

Quoted 2 lines

And it started with 4.14, and didn't occur before then, right?

I haven't try pre-4.14 kernel. Will do that and update here.

Ah. It's probably still worth trying, but I doubt it will make any difference.

Are you sure there is actually an IPMI BMC installed in this system? It might
be a plug-in card that is not installed, but the interface still appears on the
PCI bus. So there is enough hardware to go part-way through the motions of being an IPMI interface, but not enough to actually work.

Quoted 9 lines

If there is a BMC there, do you know the register layout? The IPMI spec has an algorithm to go through to discover some of the parameters, and the driver follows it, but IMHO it's not really very good. I'll need to know the
size of the registers, and the spacing between the registers.

-corey

Sorry for late response because it's close to Chinese New Year. I can get the IPMI working with the driver here on Windows.
https://www.drivermax.com/Realtek-Virtual-IPMI-Realtek-PCI-VEN-10EC-DEV-816C-1_0_0718_2013-2013-07-18-509795-driver.htm
Then you will see the device (hightlighted) on the control panel as follows
https://pasteboard.co/H7xm3fJ.png

I don't know how to get the register layout you need. I can only take a picture of the content of the PCI resources.
https://pasteboard.co/H7xnhz0.png

The contents of BAR1, BAR3, BAR5 are all 0xff. Can you point me out where the useful information might be and I can try to dump FYI.

Chris

Quoted 46 lines
Quoted 45 lines
Quoted 16 lines

There's a bug in the PCI utils database, I submitted a report a while ago.
This is
a KCS, not a SMIC interface.

It looks like the driver is trying to detect that there is a device out there and
there is something that kind of works, but doesn't work completely. The interface
specific code was all split out into separate files in 4.14. It is possible
the
detection code got messed up in the process. Nothing jumps out looking at
the code differences, and I know it works on some PCI machines.

Quoted 7 lines

Assuming this is reproducible, can you send the the output of a pre-4.14 kernel? If that doesn't make it obvious I may have to have access to the machine itself.

-corey

It's an All-in-One machine so I think it would be difficult for shipment. I'll see what
I can do. Thanks for help.

Chris

Quoted 16 lines
Quoted 13 lines
      As you see, it is due to "ipmi_probe+0x430/0x430 [ipmi_si]". After

the message "ipmi_si 0000:02:00.3: There appears to be no BMC at this location" shows up, then it can really go to suspend w/o problem. Although it took around 3 mins. The IPMI device is probed from PCI and here's the output of lspci
https://gist.github.com/mschiu77/33f0372be41670d8a69c97e64f833087. The IPMI device is "02:00.3 IPMI SMIC interface [0c07]". We get stuck here because we don't really know why it took so long in try_get_dev_id() / ipmi_si_intf.c. Any suggestion about this to help us moving forward? Thanks

Chris

#5 lore raw

I'm removing Greg and Arnd from the email, I don't think this requires their participation.

Quoted 43 lines · Chris Chiu
Quoted 42 lines · Corey Minyard
Quoted 17 lines · Chris Chiu
Quoted 10 lines · Corey Minyard
Quoted 5 lines · Chris Chiu

Hi,
We are working with a new desktop Acer Veriton Z4640G and get
stumbled on failing to enter S3 suspend with kernel version 4.14 even the latest 4.15+. Here's the kernel log
https://gist.github.com/mschiu77/76888f1fd4eb56aa8959d76759a912bb.

This is a little strange, nobody had reported this before. Can you reproduce this
at will, or was it a one-time thing?

It can be reproduced on each reboot.

Quoted 5 lines

Does the IPMI driver always take this long to issue that error, even if you
are not
entering sleep state?

Quoted 7 lines

Yep, it will always print "ipmi_si 0000:02:00.3: There appears to be no BMC at this
location" few minutes after boot.

Quoted 2 lines

And it started with 4.14, and didn't occur before then, right?

I haven't try pre-4.14 kernel. Will do that and update here.

Ah. It's probably still worth trying, but I doubt it will make any difference.

Are you sure there is actually an IPMI BMC installed in this system? It might
be a plug-in card that is not installed, but the interface still appears on the
PCI bus. So there is enough hardware to go part-way through the motions of being an IPMI interface, but not enough to actually work.

If there is a BMC there, do you know the register layout? The IPMI spec has an algorithm to go through to discover some of the parameters, and the driver follows it, but IMHO it's not really very good. I'll need to know the
size of the registers, and the spacing between the registers.

Quoted 8 lines
Quoted 3 lines

-corey

Sorry for late response because it's close to Chinese New Year. I can get the IPMI working with the driver here on Windows.
https://www.drivermax.com/Realtek-Virtual-IPMI-Realtek-PCI-VEN-10EC-DEV-816C-1_0_0718_2013-2013-07-18-509795-driver.htm
Then you will see the device (hightlighted) on the control panel as follows
https://pasteboard.co/H7xm3fJ.png

Hmm, Windows has a built-in IPMI driver.  I wonder why the aren't using that. And I don't know what "Virtual IPMI" means.

Quoted 6 lines

I don't know how to get the register layout you need. I can only take a picture of the content of the PCI resources.
https://pasteboard.co/H7xnhz0.png

The contents of BAR1, BAR3, BAR5 are all 0xff. Can you point me out where the useful information might be and I can try to dump FYI.

This whole thing sounds like they have created a non-standard IPMI interface and put it on the PCI bus like a standard one.  Unless we can get documentation for this, there's not much I can do but blacklist it.

Do you have any ties with Realtek?  I can't find anything on their web site related to IPMI.

-corey

Quoted 47 lines

Chris

Quoted 44 lines
Quoted 44 lines
Quoted 16 lines

There's a bug in the PCI utils database, I submitted a report a while ago.
This is
a KCS, not a SMIC interface.

It looks like the driver is trying to detect that there is a device out there and
there is something that kind of works, but doesn't work completely. The interface
specific code was all split out into separate files in 4.14. It is possible
the
detection code got messed up in the process. Nothing jumps out looking at
the code differences, and I know it works on some PCI machines.

Quoted 7 lines

Assuming this is reproducible, can you send the the output of a pre-4.14 kernel? If that doesn't make it obvious I may have to have access to the machine itself.

-corey

It's an All-in-One machine so I think it would be difficult for shipment. I'll see what
I can do. Thanks for help.

Chris

Quoted 15 lines
Quoted 13 lines
       As you see, it is due to "ipmi_probe+0x430/0x430 [ipmi_si]". After

the message "ipmi_si 0000:02:00.3: There appears to be no BMC at this location" shows up, then it can really go to suspend w/o problem. Although it took around 3 mins. The IPMI device is probed from PCI and here's the output of lspci
https://gist.github.com/mschiu77/33f0372be41670d8a69c97e64f833087. The IPMI device is "02:00.3 IPMI SMIC interface [0c07]". We get stuck here because we don't really know why it took so long in try_get_dev_id() / ipmi_si_intf.c. Any suggestion about this to help us moving forward? Thanks

Chris

author
#6 lore raw
Quoted 90 lines · Corey Minyard

I'm removing Greg and Arnd from the email, I don't think this requires their participation.

Quoted 57 lines · Chris Chiu
Quoted 45 lines · Corey Minyard
Quoted 23 lines · Chris Chiu
Quoted 10 lines · Corey Minyard
Quoted 6 lines · Chris Chiu

Hi,
We are working with a new desktop Acer Veriton Z4640G and get
stumbled on failing to enter S3 suspend with kernel version 4.14 even the latest 4.15+. Here's the kernel log
https://gist.github.com/mschiu77/76888f1fd4eb56aa8959d76759a912bb.

Quoted 3 lines

This is a little strange, nobody had reported this before. Can you reproduce this
at will, or was it a one-time thing?

It can be reproduced on each reboot.

Quoted 6 lines

Does the IPMI driver always take this long to issue that error, even if you
are not
entering sleep state?

Quoted 7 lines

Yep, it will always print "ipmi_si 0000:02:00.3: There appears to be no BMC at this
location" few minutes after boot.

Quoted 2 lines

And it started with 4.14, and didn't occur before then, right?

I haven't try pre-4.14 kernel. Will do that and update here.

Ah. It's probably still worth trying, but I doubt it will make any difference.

Are you sure there is actually an IPMI BMC installed in this system? It might
be a plug-in card that is not installed, but the interface still appears on
the
PCI bus. So there is enough hardware to go part-way through the motions of being an IPMI interface, but not enough to actually work.

Quoted 10 lines

If there is a BMC there, do you know the register layout? The IPMI spec has
an algorithm to go through to discover some of the parameters, and the driver follows it, but IMHO it's not really very good. I'll need to know the
size of the registers, and the spacing between the registers.

-corey

Quoted 7 lines

Sorry for late response because it's close to Chinese New Year. I can get the IPMI working with the driver here on Windows.

https://www.drivermax.com/Realtek-Virtual-IPMI-Realtek-PCI-VEN-10EC-DEV-816C-1_0_0718_2013-2013-07-18-509795-driver.htm
Then you will see the device (hightlighted) on the control panel as follows
https://pasteboard.co/H7xm3fJ.png

Hmm, Windows has a built-in IPMI driver. I wonder why the aren't using that.
And I don't know what "Virtual IPMI" means.

Quoted 6 lines

I don't know how to get the register layout you need. I can only take a picture of the content of the PCI resources.
https://pasteboard.co/H7xnhz0.png

The contents of BAR1, BAR3, BAR5 are all 0xff. Can you point me out where the useful information might be and I can try to dump FYI.

This whole thing sounds like they have created a non-standard IPMI interface and put it on the PCI bus like a standard one. Unless we can get documentation
for this, there's not much I can do but blacklist it.

Quoted 7 lines

Do you have any ties with Realtek? I can't find anything on their web site related
to IPMI.

-corey

I see. I'll try to reach the contact window for this in Realtek to see if there's any
datasheet or document and get back here.

Chris

Quoted 52 lines
Quoted 51 lines

Chris

Quoted 48 lines
Quoted 48 lines
Quoted 16 lines

There's a bug in the PCI utils database, I submitted a report a while ago.
This is
a KCS, not a SMIC interface.

It looks like the driver is trying to detect that there is a device out there and
there is something that kind of works, but doesn't work completely. The interface
specific code was all split out into separate files in 4.14. It is possible
the
detection code got messed up in the process. Nothing jumps out looking at
the code differences, and I know it works on some PCI machines.

Quoted 9 lines

Assuming this is reproducible, can you send the the output of a pre-4.14
kernel? If that doesn't make it obvious I may have to have access to the
machine itself.

-corey

It's an All-in-One machine so I think it would be difficult for shipment. I'll see what
I can do. Thanks for help.

Chris

Quoted 17 lines
Quoted 14 lines
       As you see, it is due to "ipmi_probe+0x430/0x430 [ipmi_si]".

After
the message "ipmi_si 0000:02:00.3: There appears to be no BMC at this location" shows up, then it can really go to suspend w/o problem. Although it took around 3 mins. The IPMI device is probed from PCI and here's the output of lspci
https://gist.github.com/mschiu77/33f0372be41670d8a69c97e64f833087. The IPMI device is "02:00.3 IPMI SMIC interface [0c07]". We get stuck here because we don't really know why it took so long in try_get_dev_id() / ipmi_si_intf.c. Any suggestion about this to help us moving forward? Thanks

Chris

#7 lore raw

PATCH 1/1 ipmi:pci: Blacklist a Realtek "IPMI" device

From: Corey Minyard <[email protected]>

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.

---

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?

 drivers/char/ipmi/ipmi_si_pci.c | 12 ++++++++++++
 1 file changed, 12 insertions(+)
drivers/char/ipmi/ipmi_si_pci.c +12 -0
index 27dd11c..d24990b 100644
@@ -65,6 +65,15 @@ static int ipmi_pci_probe_regspacing(struct si_sm_io *io)
 	return DEFAULT_REGSPACING;
 }
 
+static struct pci_device_id ipmi_pci_blacklist[] = {
+	/*
+	 * This is a "Virtual IPMI device", whatever that is.  It appears
+	 * as a KCS device by the class, but it is not one.
+	 */
+	{ PCI_DEVICE(PCI_VENDOR_ID_REALTEK, 0x816c) },
+	{ 0, }
+};
+
 static int ipmi_pci_probe(struct pci_dev *pdev,
 				    const struct pci_device_id *ent)
 {
@@ -72,6 +81,9 @@ static int ipmi_pci_probe(struct pci_dev *pdev,
 	int class_type = pdev->class & PCI_ERMC_CLASSCODE_TYPE_MASK;
 	struct si_sm_io io;
 
+	if (pci_match_id(ipmi_pci_blacklist, pdev))
+		return -ENODEV;
+
 	memset(&io, 0, sizeof(io));
 	io.addr_source = SI_PCI;
 	dev_info(&pdev->dev, "probing via PCI");
Signature · 1 line
2.7.4
#8 lore raw

Re: [PATCH] ipmi:pci: Blacklist a Realtek "IPMI" device

drivers/char/ipmi/ipmi_si_pci.c static int ipmi_pci_probe_regspacing(struct si_sm_io *io) · line 74

Quoted 11 lines · On Mon, Feb 26, 2018 at 4:50 AM, <[email protected]> wrote:

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.

drivers/char/ipmi/ipmi_si_pci.c +7 -0
+static struct pci_device_id ipmi_pci_blacklist[] = {
+       /*
+        * This is a "Virtual IPMI device", whatever that is.  It appears
+        * as a KCS device by the class, but it is not one.
+        */
 
+       { PCI_DEVICE(PCI_VENDOR_ID_REALTEK, 0x816c) },
+       { 0, }

{ PCI_VDEVICE(REALTEK, 0x816c) },
{ }

?

Quoted 4 lines
drivers/char/ipmi/ipmi_si_pci.c +3 -0
+};
 
+       if (pci_match_id(ipmi_pci_blacklist, pdev))
+               return -ENODEV;
Signature · 2 lines
With Best Regards,
Andy Shevchenko
#9 lore raw

Re: [PATCH] ipmi:pci: Blacklist a Realtek "IPMI" device

Quoted 11 lines · Andy Shevchenko

drivers/char/ipmi/ipmi_si_pci.c static int ipmi_pci_probe_regspacing(struct si_sm_io *io) · line 74

Quoted 9 lines · On Mon, Feb 26, 2018 at 4:50 AM, <[email protected]> wrote:

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.

drivers/char/ipmi/ipmi_si_pci.c +7 -0
+static struct pci_device_id ipmi_pci_blacklist[] = {
+       /*
+        * This is a "Virtual IPMI device", whatever that is.  It appears
+        * as a KCS device by the class, but it is not one.
+        */
+       { PCI_DEVICE(PCI_VENDOR_ID_REALTEK, 0x816c) },
+       { 0, }
Quoted 4 lines

{ PCI_VDEVICE(REALTEK, 0x816c) },
{ }

?

That's better, thanks.

-corey

Quoted 5 lines
Quoted 4 lines
drivers/char/ipmi/ipmi_si_pci.c +3 -0
+};
+       if (pci_match_id(ipmi_pci_blacklist, pdev))
+               return -ENODEV;
#10 lore raw

Re: [PATCH] ipmi:pci: Blacklist a Realtek "IPMI" device

In reply to [email protected]

Hi,

Quoted 5 lines · On Mon, Feb 26, 2018 at 10:50 AM, <[email protected]> wrote:

From: Corey Minyard <[email protected]>

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.

Quoted 7 lines

---

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.

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

#11 lore raw

Re: [PATCH] ipmi:pci: Blacklist a Realtek "IPMI" device

Quoted 12 lines · Daniel Drake

Hi,

Quoted 9 lines · On Mon, Feb 26, 2018 at 10:50 AM, <[email protected]> wrote:

From: Corey Minyard <[email protected]>

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.

---

Quoted 8 lines
Quoted 3 lines

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

Quoted 8 lines

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