I can confirm that this has worked much better with recent kernels, so
my comment in #16 can be ignored.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1154749
Title:
reboot does a
The kernel command line parameter described in #15 has been uploaded to
linux 3.13.0-17.37
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1154749
Title:
reboot does a shutdown instead
So I messed around with this machine for a good part of the day. I built
and booted 3.14-rc4, then instrumented the mei and mei-me modules to
show the various setup and teardown stages. I think they are correct.
What I did find were some issues with MSI. In fact, if you boot with MSI
disabled
rodsmith - please try the test kernel at
http://kernel.ubuntu.com/~rtg/3.13.0-16.36-mei/ - After installing you
can add the module parameter options thusly:
echo options mei-me disable_msi=1 | sudo tee /etc/modprobe.d/mei-
me.conf
This option should behave the same as my testing, e.g., disallows
This does seem to help, but with some very big caveats:
First, I was unable to test the -generic kernel because it lacked the
mei and mei_me modules. I therefore did my testing with the -lowlatency
version of the kernel.
Second, whether the disable_msi=1 kernel option was used or not, the
system
rodsmith - I don't think you installed linux-image-
extra-3.13.0-17-generic_3.13.0-17.37_amd64.deb which is why you are
missing mei.ko and mei_me.ko. The lowlatency flavour has still got some
issues that we're working through.
--
You received this bug notification because you are a member of
Update: I've verified this bug in a BIOS-mode boot in trusty, with a
twist: BOTH the mei AND the mei_me modules must be blacklisted in order
to cause a reboot to work. When both are blacklisted, rebooting also
works when the system is booted in EFI mode -- I suspect a failure to
blacklist mei_me
This bug still exists in Trusty, at least when the OCPv2 Windmill is
booted in EFI mode. Blacklisting the mei module does *NOT* work around
the problem with Trusty in EFI mode. Testing in BIOS mode will have to
wait a few more days
--
You received this bug notification because you are a
8 matches
Mail list logo
