Re: blacklist mei_me?

[hw <hw@adminart.net>]

On Tue, 2022-11-15 at 12:27 +0000, Tixy wrote:
> On Tue, 2022-11-15 at 11:10 +0100, hw wrote:
> > Hi,
> > 
> > this module causes delays when booting and I'm finding this in dmesg:
> > 
> > 
> > [   14.889003] mei_me 0000:00:16.0: hw_reset failed ret = -62
> > [   20.009003] mei_me 0000:00:16.0: hw_reset failed ret = -62
> > [   25.129003] mei_me 0000:00:16.0: hw_reset failed ret = -62
> > [   25.129315] mei_me 0000:00:16.0: reset: reached maximal consecutive
> > resets:
> > disabling the device
> > [   25.129797] mei_me 0000:00:16.0: reset failed ret = -19
> > [   25.130086] mei_me 0000:00:16.0: link layer initialization failed.
> > [   25.130431] mei_me 0000:00:16.0: init hw failure.
> > [   25.130745] mei_me 0000:00:16.0: initialization failed.
> > 
> > 
> > Should I just blacklist it or is that a bad idea?  Apparently whatever it is
> > for
> > gets disabled anyway and it doesn't seem to be a disadvantage other than
> > causing
> > delays.
> > 
> 
> If you use Google to search for mei_me you'll lots o similar reports
> going back a decade, e.g. https://bbs.archlinux.org/viewtopic.php?id=168403
> 
> These seem to suggest blacklisting the module or disabling Management
> Engine Interface in the BIOS.
> 

Thanks.  Of course I did search and it was unclear if I should just disable the
module, so I thought I'd better ask.