You are not logged in.

#1 2013-09-10 16:58:39

cecar
Member
Registered: 2013-03-10
Posts: 39

[SOLVED] Random lockups 3.10.10-1 kernel 64bit

I have for a while random lockups on my system. The whole system halts all i can do is hardreset the system. No keyboard respons at all.

This is Journalctl -r output just before i reset the system. There are over 1000 lines of "kernel: mei_me 0000:00:16.0: reset: wrong host start response"

-- Reboot --
sep 10 12:39:52 asusarch systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
sep 10 12:39:52 asusarch systemd[1]: systemd-journald.service: main process exited, code=exited, status=1/FAILURE
sep 10 12:39:52 asusarch systemd-journal[1858]: Journal started
sep 10 12:39:52 asusarch systemd-journal[1858]: Allowing system journal files to grow to 8.0M.
sep 10 12:39:52 asusarch systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
sep 10 12:39:52 asusarch systemd[1]: systemd-journald.service: main process exited, code=exited, status=1/FAILURE
sep 10 12:39:52 asusarch systemd-journal[1854]: Journal started
sep 10 12:39:52 asusarch systemd-journal[1854]: Allowing system journal files to grow to 8.0M.
sep 10 12:39:52 asusarch systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
sep 10 12:39:52 asusarch systemd[1]: systemd-journald.service: main process exited, code=exited, status=1/FAILURE
sep 10 12:39:52 asusarch systemd-journal[1850]: Journal started
sep 10 12:39:52 asusarch systemd-journal[1850]: Allowing system journal files to grow to 8.0M.
sep 10 12:39:52 asusarch systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
sep 10 12:39:52 asusarch systemd[1]: systemd-journald.service: main process exited, code=killed, status=10/USR1
sep 10 12:39:52 asusarch systemd[1]: systemd-journald.service: main process exited, code=exited, status=1/FAILURE
sep 10 12:39:52 asusarch systemd-journal[1847]: Journal started
sep 10 12:39:52 asusarch systemd-journal[1847]: Allowing system journal files to grow to 8.0M.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING

Anyone that has an idea what i can do to track down the problem.

Last edited by cecar (2013-09-11 09:22:11)

Offline

#2 2013-09-10 17:29:18

jrussell
Member
From: Cape Town, South Africa
Registered: 2012-08-16
Posts: 510

Re: [SOLVED] Random lockups 3.10.10-1 kernel 64bit

maybe related? https://bugs.archlinux.org/task/36288

Are you using intel graphics?

Last edited by jrussell (2013-09-10 17:30:19)


bitcoin: 1G62YGRFkMDwhGr5T5YGovfsxLx44eZo7U

Offline

#3 2013-09-10 17:37:58

WonderWoofy
Member
From: Los Gatos, CA
Registered: 2012-05-19
Posts: 8,412

Re: [SOLVED] Random lockups 3.10.10-1 kernel 64bit

Blacklist/unload the mei_me module.  This may have negative consequences on suspending (though I have noticed no difference on my Core2Duo machine).

When you system locks up, does it really lock up?  That is, can you try enabling the Magic SysRq key and then try to use that the next time this happens?  I suspect that your userspace might have frozen, but the kernel should still be alive and functioning (otherwise you would typically end up with a kernel panic).

In any case, I don't think that the mei_me thing would cause a total lockup of your machine.  Besides the journal being spammed like crazy with those messages, I didn't notice any difference in the functionality of the machine.


Edit: I think that in cases such as this, the simplest thing you can do is change kernels and see if the problem persists.  As it is, you have provided no real indication that the issue is even related to the kernel upgrade/version.  So downgrade just the kernel and see if the problem persists (or install the [testing] kernel).

Last edited by WonderWoofy (2013-09-10 17:40:13)

Offline

#4 2013-09-10 18:57:28

cecar
Member
Registered: 2013-03-10
Posts: 39

Re: [SOLVED] Random lockups 3.10.10-1 kernel 64bit

Yes, im using Intel graphics.
I have enabled SysRq and tried REISUB. It's totally frozen. Capslock, numlock lights do not turn on or off when pressing the keys. I'll try blacklising and see if it helps.

Thanks for helping out

Edit: I blacklisted mei_me module and i have not had any lockups for 24 hours so i am marking this as solved for the time being.

Last edited by cecar (2013-09-11 09:21:36)

Offline

#5 2013-09-13 00:21:08

donniezazen
Member
From: Salt Lake City
Registered: 2011-06-24
Posts: 671
Website

Re: [SOLVED] Random lockups 3.10.10-1 kernel 64bit

@WonderWoofy What kind of suspend problem are we talking about? This apparently resolves lock-up issues but my KDE setup doesn't look like suspending automatically. It suspends fine manually.

UPDATE:- I can confirm that KDE is unable to lock my system automatically after timeout but can suspend the system manually.

Last edited by donniezazen (2013-09-13 00:27:00)

Offline

#6 2013-09-13 00:25:13

WonderWoofy
Member
From: Los Gatos, CA
Registered: 2012-05-19
Posts: 8,412

Re: [SOLVED] Random lockups 3.10.10-1 kernel 64bit

Considering that I am wholly unaffected by these suspend problems, I really couldn't tell you with any confidence.  I just remember reading that people were having issues with suspend after blacklisting/unloading the mei_me module.  But what you are describing sounds vaguely familiar.

Offline

#7 2013-09-13 05:31:57

donniezazen
Member
From: Salt Lake City
Registered: 2011-06-24
Posts: 671
Website

Re: [SOLVED] Random lockups 3.10.10-1 kernel 64bit

I had a lock up this evening after blacklisting mei_me. At least on my system, mei_me doesn't particularly has to do with system freeze.

Offline

#8 2013-09-13 14:06:48

mcloaked
Member
From: Yorkshire, UK
Registered: 2012-02-02
Posts: 686

Re: [SOLVED] Random lockups 3.10.10-1 kernel 64bit

It would be nice to see the kernel 3.11 released to core - I had random lockup problems with 3.10 on more than one machine - someone I know compiled 3.11 and gave me access to it - on the machine on which that I have been using 3.11 there have been no further lockup problems. I notice that in testing kernel 3.11 was signed off on both i686 and x86_64 some days ago, but it is not yet released so I presume that there are some residual issues that present release?   Also 3.11.1 is about ready too - but hopefully we will see 3.11 in [core] before long. There is a chance that these issues may then well just go away!

If anyone wants to try 3.11 before it gets to core there is the linux-mainline package at https://aur.archlinux.org/packages/linux-mainline/

Last edited by mcloaked (2013-09-13 14:42:56)


Mike C

Offline

#9 2013-09-17 09:07:53

mcloaked
Member
From: Yorkshire, UK
Registered: 2012-02-02
Posts: 686

Re: [SOLVED] Random lockups 3.10.10-1 kernel 64bit

Now that kernel 3.11.1-1 is released to [core] it would be nice if the original reporter could say if the problems with lockups are still occurring with the 3.11 kernel?


Mike C

Offline

#10 2013-09-17 11:40:28

cecar
Member
Registered: 2013-03-10
Posts: 39

Re: [SOLVED] Random lockups 3.10.10-1 kernel 64bit

I have enabled mei_me again with the new kernel. I will report back and edit this post with the result.

Edit: I have been running the 3.11 kernel with mei_me module for 24 hours now without any problems at all so the new kernel fixed the issue with freezing for me.

Last edited by cecar (2013-09-18 11:57:42)

Offline

Board footer

Powered by FluxBB