[lkml]   [2018]   [Feb]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: ipmi_si fails to get BMC ID
On Thu, Feb 8, 2018 at 11:53 PM, Corey Minyard <> wrote:
> On 02/07/2018 09:01 PM, Chris Chiu wrote:
>> 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
> 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.
> 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.

> 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.

> 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
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.


>> 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
>> 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

 \ /
  Last update: 2018-02-09 04:10    [W:0.079 / U:6.016 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site