mei_me timeout failure at boot up
I have an mei_me error at system boot up with additional behavior， that the computer'screen is refreshed about every 2 second. After seeing the purple boot screen of Ubuntu I got these error (so I was not able to get the login screen so far):
...
[ OK ] Started GNOME Display Manager.
[ OK ] Started Disk Manager
[ OK ] Started Snappy daemon
[ OK ] Started Hold until boot process finishes up.
[ 34.079970] mei_me 0000:00:16.0: timer: init client timeouthbm_state = 2.
[ 94.560062] mei_me 0000:00:16.0: timer: init client timeouthbm_state = 2.
[ 94.561248] mei_me 0000:00:16.0: reset: reached maximal consecutive resets: disabling the device.
I got Ubuntu 18.04.1 LTS with kernel version 4.15.0-43-generic.
I already did some searching. With
mei_me unexpected reset and mei_me initialization failed at boot up.
When I try to add
blacklist mei_meat the end of/etc/modprobe.d/blacklist.conf file, I was also not able to boot:
...
[ OK ] Started GNOME Display Manager.
[ OK ] Started Disk Manager
[ OK ] Started Snappy daemon
[ OK ] Started Hold until boot process finishes up.
I will be struck at the last line and make no progress. (Hmm the mei_me dosen't appear but it not so helpful for booting.)
- When I try
control-pto get toManagement Engine BIOS Extension Options, it doesn't give me a reply and still lead me to theUbuntu OS. But I was able to get to the BIOS with pressingF2and I got an Intel Core i5-4210. Maybe that is a way to fix my problem, when I could get to theManagement Engine BIOS Extension Options?
boot 18.04 bios
asked 2 days ago
Jigao
63
add a comment |
I have an mei_me error at system boot up with additional behavior， that the computer'screen is refreshed about every 2 second. After seeing the purple boot screen of Ubuntu I got these error (so I was not able to get the login screen so far):
...
[ OK ] Started GNOME Display Manager.
[ OK ] Started Disk Manager
[ OK ] Started Snappy daemon
[ OK ] Started Hold until boot process finishes up.
[ 34.079970] mei_me 0000:00:16.0: timer: init client timeouthbm_state = 2.
[ 94.560062] mei_me 0000:00:16.0: timer: init client timeouthbm_state = 2.
[ 94.561248] mei_me 0000:00:16.0: reset: reached maximal consecutive resets: disabling the device.
I got Ubuntu 18.04.1 LTS with kernel version 4.15.0-43-generic.
I already did some searching. With
mei_me unexpected reset and mei_me initialization failed at boot up.
When I try to add
blacklist mei_meat the end of/etc/modprobe.d/blacklist.conf file, I was also not able to boot:
...
[ OK ] Started GNOME Display Manager.
[ OK ] Started Disk Manager
[ OK ] Started Snappy daemon
[ OK ] Started Hold until boot process finishes up.
I will be struck at the last line and make no progress. (Hmm the mei_me dosen't appear but it not so helpful for booting.)
- When I try
control-pto get toManagement Engine BIOS Extension Options, it doesn't give me a reply and still lead me to theUbuntu OS. But I was able to get to the BIOS with pressingF2and I got an Intel Core i5-4210. Maybe that is a way to fix my problem, when I could get to theManagement Engine BIOS Extension Options?
boot 18.04 bios
asked 2 days ago
Jigao
63
add a comment |
I have an mei_me error at system boot up with additional behavior， that the computer'screen is refreshed about every 2 second. After seeing the purple boot screen of Ubuntu I got these error (so I was not able to get the login screen so far):
...
[ OK ] Started GNOME Display Manager.
[ OK ] Started Disk Manager
[ OK ] Started Snappy daemon
[ OK ] Started Hold until boot process finishes up.
[ 34.079970] mei_me 0000:00:16.0: timer: init client timeouthbm_state = 2.
[ 94.560062] mei_me 0000:00:16.0: timer: init client timeouthbm_state = 2.
[ 94.561248] mei_me 0000:00:16.0: reset: reached maximal consecutive resets: disabling the device.
I got Ubuntu 18.04.1 LTS with kernel version 4.15.0-43-generic.
I already did some searching. With
mei_me unexpected reset and mei_me initialization failed at boot up.
When I try to add
blacklist mei_meat the end of/etc/modprobe.d/blacklist.conf file, I was also not able to boot:
...
[ OK ] Started GNOME Display Manager.
[ OK ] Started Disk Manager
[ OK ] Started Snappy daemon
[ OK ] Started Hold until boot process finishes up.
I will be struck at the last line and make no progress. (Hmm the mei_me dosen't appear but it not so helpful for booting.)
- When I try
control-pto get toManagement Engine BIOS Extension Options, it doesn't give me a reply and still lead me to theUbuntu OS. But I was able to get to the BIOS with pressingF2and I got an Intel Core i5-4210. Maybe that is a way to fix my problem, when I could get to theManagement Engine BIOS Extension Options?
boot 18.04 bios
asked 2 days ago
Jigao
63
I have an mei_me error at system boot up with additional behavior， that the computer'screen is refreshed about every 2 second. After seeing the purple boot screen of Ubuntu I got these error (so I was not able to get the login screen so far):
...
[ OK ] Started GNOME Display Manager.
[ OK ] Started Disk Manager
[ OK ] Started Snappy daemon
[ OK ] Started Hold until boot process finishes up.
[ 34.079970] mei_me 0000:00:16.0: timer: init client timeouthbm_state = 2.
[ 94.560062] mei_me 0000:00:16.0: timer: init client timeouthbm_state = 2.
[ 94.561248] mei_me 0000:00:16.0: reset: reached maximal consecutive resets: disabling the device.
I got Ubuntu 18.04.1 LTS with kernel version 4.15.0-43-generic.
I already did some searching. With
mei_me unexpected reset and mei_me initialization failed at boot up.
When I try to add
blacklist mei_meat the end of/etc/modprobe.d/blacklist.conf file, I was also not able to boot:
...
[ OK ] Started GNOME Display Manager.
[ OK ] Started Disk Manager
[ OK ] Started Snappy daemon
[ OK ] Started Hold until boot process finishes up.
I will be struck at the last line and make no progress. (Hmm the mei_me dosen't appear but it not so helpful for booting.)
- When I try
control-pto get toManagement Engine BIOS Extension Options, it doesn't give me a reply and still lead me to theUbuntu OS. But I was able to get to the BIOS with pressingF2and I got an Intel Core i5-4210. Maybe that is a way to fix my problem, when I could get to theManagement Engine BIOS Extension Options?
boot 18.04 bios
boot 18.04 bios
asked 2 days ago
Jigao
63
asked 2 days ago
Jigao
63
asked 2 days ago
Jigao
63
asked 2 days ago
Jigao
63
asked 2 days ago
Jigao
63
63
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I found that is a current issue for the 18.04 and the solution that I found is this one: 18.04 Boot freezes at "Started Hold until boot process finishes up".
I did have no space in the /boot/ partition and I could boot to the OS, after I remote some old kernel image.
Seems this problem is not relevant to the mei_me but still hope this post could helpful for other having the same problem as me.
answered yesterday
Jigao
63
New contributor
Jigao is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1104877%2fmei-me-timeout-failure-at-boot-up%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I found that is a current issue for the 18.04 and the solution that I found is this one: 18.04 Boot freezes at "Started Hold until boot process finishes up".
I did have no space in the /boot/ partition and I could boot to the OS, after I remote some old kernel image.
Seems this problem is not relevant to the mei_me but still hope this post could helpful for other having the same problem as me.
answered yesterday
Jigao
63
New contributor
Jigao is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I found that is a current issue for the 18.04 and the solution that I found is this one: 18.04 Boot freezes at "Started Hold until boot process finishes up".
I did have no space in the /boot/ partition and I could boot to the OS, after I remote some old kernel image.
Seems this problem is not relevant to the mei_me but still hope this post could helpful for other having the same problem as me.
answered yesterday
Jigao
63
New contributor
Jigao is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I found that is a current issue for the 18.04 and the solution that I found is this one: 18.04 Boot freezes at "Started Hold until boot process finishes up".
I did have no space in the /boot/ partition and I could boot to the OS, after I remote some old kernel image.
Seems this problem is not relevant to the mei_me but still hope this post could helpful for other having the same problem as me.
answered yesterday
Jigao
63
New contributor
Jigao is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I found that is a current issue for the 18.04 and the solution that I found is this one: 18.04 Boot freezes at "Started Hold until boot process finishes up".
I did have no space in the /boot/ partition and I could boot to the OS, after I remote some old kernel image.
Seems this problem is not relevant to the mei_me but still hope this post could helpful for other having the same problem as me.
answered yesterday
Jigao
63
New contributor
Jigao is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered yesterday
Jigao
63
New contributor
Jigao is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered yesterday
Jigao
63
answered yesterday
Jigao
63
63
New contributor
Jigao is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Jigao is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Jigao is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1104877%2fmei-me-timeout-failure-at-boot-up%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
