Bug 11353 - Kernel does not reboot on Super Micro X9 boards
Summary: Kernel does not reboot on Super Micro X9 boards
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: x86_64 Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-02 00:13 CEST by James Reno
Modified: 2014-07-08 21:28 CEST (History)
0 users

See Also:
Source RPM: kernel-3.8.13.4-1.mga3.src.rpm
CVE:
Status comment:


Attachments

Description James Reno 2013-10-02 00:13:46 CEST
Description of problem:
Machine does not reboot, always powers off.


Version-Release number of selected component (if applicable):
Kernel 3.x


How reproducible:
Always


Steps to Reproduce:
1. Install mageia 3, update to latest kernel
2. exectue "reboot" command
3. -- machine powers off


This is evidently a known issue with specific kernel releases in the 3.x series that has effected other distributions such as ubuntu. There may be an updated kernel patch to apply to resolve this issue.

I have confirmed the BIOS is up-to-date with the latest version from SuperMicro.

Reproducible: 

Steps to Reproduce:
Comment 1 James Reno 2013-10-02 00:19:33 CEST
http://askubuntu.com/questions/210249/reboot-only-shuts-down-and-doesnt-actually-boot-again
http://ubuntuforums.org/showthread.php?t=2024096


Following the recommendations for ubuntu and modifying the /etc/modprobe.d/blacklist-mga.conf adding "blacklist mei" and unloading the mei driver prior to reboot solves the problem.

However, I believe this should be resolved with a kernel update or something...  Work arounds such as this one should *NOT* be necessary.
Comment 2 Manuel Hiebel 2013-10-07 12:38:48 CEST
maybe it's better with kernel 3.10 from testing ?
Comment 3 James Reno 2014-07-08 21:28:53 CEST
Its fixed in MGA4 so this bug may be closed.

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.