Arch Linux

amiko

Member

Registered: 2016-08-22

Posts: 3

Multiple issues including mei_wdt: Could not reg notif event ret=-22

I recently wiped my old Arch install and have reinstalled from scratch, as I'm making several major configuration changes. I've had several problems with this install, but I have most of them worked out. I have 2 main issues at this point.

I'm using openbox with tint2 and lightdm. My hard drive is Luks encrypted.

1. When I boot up, lightdm loads fine, and lets me log in and launch openbox. Sometimes tint2 loads, sometimes it doesn't. Sometimes I can open a terminal, sometimes I can't. If I can't open a terminal, I also can't Ctrl+Alt+F7 to fall back into init 3. I have to manually power the machine off and then reboot to try again. Sometimes rebooting fixes this, sometimes it doesn't. I thought the problem might be lightdm, but I disabled it in systemctl, and when I startx, I get the same issue.

2. I've noticed I get an error every time I boot up:

mei_wdt mei::05b79a6f-4628-4d7f-899d-a91514cb32ab:02: Could not reg notif event ret=-22

Here's a partial output of journalctl -xe:

Jun 02 21:26:34 localhost NetworkManager[374]: <info>  [1496456794.1498] policy: set-hostname: set hostname to 'localhost.localdomain' (Error reverse-resolving “192.168.1.23”: Name or service
Jun 02 21:26:34 localhost.localdomain systemd-hostnamed[411]: Changed host name to 'localhost.localdomain'
Jun 02 21:26:34 localhost.localdomain nm-dispatcher[407]: req:3 'hostname': new request (0 scripts)
Jun 02 21:26:34 localhost.localdomain nm-dispatcher[407]: req:3 'hostname': completed: no scripts
Jun 02 21:26:36 localhost.localdomain NetworkManager[374]: <info>  [1496456796.2368] manager: NetworkManager state is now CONNECTED_GLOBAL
Jun 02 21:26:36 localhost.localdomain nm-dispatcher[407]: req:4 'connectivity-change': new request (0 scripts)
Jun 02 21:26:36 localhost.localdomain nm-dispatcher[407]: req:4 'connectivity-change': completed: no scripts
Jun 02 21:26:42 localhost.localdomain kernel: mei_wdt mei::05b79a6f-4628-4d7f-899d-a91514cb32ab:02: Could not reg notif event ret=-22
Jun 02 21:26:42 localhost.localdomain kernel: mei_wdt: probe of mei::05b79a6f-4628-4d7f-899d-a91514cb32ab:02 failed with error -22
Jun 02 21:27:09 localhost.localdomain kernel: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size i
Jun 02 21:27:09 localhost.localdomain systemd[456]: Started D-Bus User Message Bus.

I looked thorugh a couple of other logs (lightdm, Xorg.0.log, faillog, lastlog), and none of them seemed to have anything relevant.

Do these two issues seem to be related, or am I on the wrong track? Is hte mei_wdt something I need to address right now, or can it wait until after I've solved the lightdm/X11/openbox/tint2 issue?

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,426

Website

Re: Multiple issues including mei_wdt: Could not reg notif event ret=-22

Set your hostname.

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

amiko

Member

Registered: 2016-08-22

Posts: 3

Re: Multiple issues including mei_wdt: Could not reg notif event ret=-22

I set a hostname, and updated the /etc/hosts file and rebooted. Manually started X11, checkted journalctl and mei_wdt error is still there. Re-enabled lightdm and rebooted. After launching openbox, machine is unresponsive. So setting a hostname seemed to have no effect.

I've now restarted from scratch. I have a command-line only installation. I've completed basic pacstrap and have installed these additional utilities only:
sudo
vim
wget
networkmanager

After booting into command line and running journalctl -xe, I still see mei_wdt error.