I patched the source from 3.8.0-27.40 (there aren't any changes for the
mei driver in any Ubuntu 3.8 kernels) and just build the module. The
dmesg log still continues to fill with "mei reset" messages.

Since the mei driver has changed a lot since 3.8, I tried to backport
the mei driver from git AKA 3.11-rc5+ (commit
dab9bf41b23fe700c4a74133e41eb6a21706031e) for a test.

The backport patch is very minimal and stops the messages, but since I
don't use the Intel AMT interface, I don't know if it's working as
expected.


** Patch added: "Backport patch for the mei driver from kernel v3.11-rc5+ to 
v3.8."
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1176577/+attachment/3775052/+files/mei-bp-from-commit-dab9bf41b23.diff

** Bug watch added: Red Hat Bugzilla #917081
   https://bugzilla.redhat.com/show_bug.cgi?id=917081

** Also affects: linux (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=917081
   Importance: Unknown
       Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1176577

Title:
  mei unexpected reset in kernel 3.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1176577/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to