[Kernel-packages] [Bug 1154749] Re: reboot does a shutdown instead of rebooting (OCP v2)
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 shutdown instead of rebooting (OCP v2) Status in OEM Priority Project: Invalid Status in Open Compute Project: New Status in “linux” package in Ubuntu: Confirmed Bug description: On the OCP v2 compliant system (Windmill OCP motherboard v2), the system hang at the reboot startup. This issue happens on 12.04.1, 12.04.2 and 12.10. The work around in http://ubuntuforums.org/showthread.php?t=2024096, blacklisting mei, works. Note the first reboot doesn't work, but the subsequent reboots work. mei in 12.04.1 $ modinfo mei filename: /lib/modules/3.2.0-38-generic/kernel/drivers/staging/mei/mei.ko version:7.1.20.1 license:GPL v2 description:Intel(R) Management Engine Interface author: Intel Corporation srcversion: 9252880194B02634B5F0427 Kernel mei message before blacklisted: kernel: [6.961623] mei: module is from the staging directory, the quality is unknown, you have been warned. kernel: [6.962226] mei :00:16.0: PCI INT A - GSI 16 (level, low) - IRQ 16 kernel: [6.962235] mei :00:16.0: setting latency timer to 64 kernel: [6.962310] mei :00:16.0: irq 104 for MSI/MSI-X mei in 12.04.2 $ modinfo mei filename: /lib/modules/3.5.0-25-generic/kernel/drivers/misc/mei/mei.ko license:GPL v2 description:Intel(R) Management Engine Interface author: Intel Corporation srcversion: 0580619CB5DEF6AB7228EBE Kernel mei message before blacklisted: kernel: [6.543470] mei :00:16.0: setting latency timer to 64 kernel: [6.543547] mei :00:16.0: irq 104 for MSI/MSI-X kernel: [6.547516] mei :00:16.0: wd: failed to find the client mei in 12.10 $ modinfo mei filename: /lib/modules/3.5.0-21-generic/kernel/drivers/misc/mei/mei.ko license:GPL v2 description:Intel(R) Management Engine Interface author: Intel Corporation srcversion: 0580619CB5DEF6AB7228EBE Kernel mei message before blacklisted: kernel: [4.731997] mei :00:16.0: setting latency timer to 64 kernel: [4.736801] mei :00:16.0: irq 104 for MSI/MSI-X kernel: [4.741695] mei :00:16.0: wd: failed to find the client To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1154749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1300416] Re: Install of 14.04 fails with 3.13.0-20-generic kernel
I've verified that the 3.13-23-gneric kernel does indeed fix the problem on the systems I'd been using. -- 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/1300416 Title: Install of 14.04 fails with 3.13.0-20-generic kernel Status in “linux” package in Ubuntu: Fix Released Bug description: I've tried installing the latest daily build of Trusty server, with a 3.13.0-20-generic kernel, on several Lenovo ThinkPad models (X121e, X131e, and L330). It's failed on every one of them. The installer hangs on an empty purple screen (see screen shot). Switching to VT4 reveals kernel error messages, which also appear in /var/log/syslog. (A bash shell can be obtained on VT2 or VT3 to retrieve this log file.) I'm attaching a copy of the log file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1300416] Re: Install of 14.04 fails with 3.13.0-20-generic kernel
Tim, disabling the Wi-Fi radio in the firmware did not resolve the problem. (I didn't see any other options related to Wi-Fi.) Of course, that's moot if Seth's fix works, so I look forward to testing it. -- 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/1300416 Title: Install of 14.04 fails with 3.13.0-20-generic kernel Status in “linux” package in Ubuntu: In Progress Bug description: I've tried installing the latest daily build of Trusty server, with a 3.13.0-20-generic kernel, on several Lenovo ThinkPad models (X121e, X131e, and L330). It's failed on every one of them. The installer hangs on an empty purple screen (see screen shot). Switching to VT4 reveals kernel error messages, which also appear in /var/log/syslog. (A bash shell can be obtained on VT2 or VT3 to retrieve this log file.) I'm attaching a copy of the log file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1300416] [NEW] Install of 14.04 fails with 3.13.0-20-generic kernel
Public bug reported: I've tried installing the latest daily build of Trusty server, with a 3.13.0-20-generic kernel, on several Lenovo ThinkPad models (X121e, X131e, and L330). It's failed on every one of them. The installer hangs on an empty purple screen (see screen shot). Switching to VT4 reveals kernel error messages, which also appear in /var/log/syslog. (A bash shell can be obtained on VT2 or VT3 to retrieve this log file.) I'm attaching a copy of the log file. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: Screen shot of hung VT1 https://bugs.launchpad.net/bugs/1300416/+attachment/4056300/+files/hung.jpg -- 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/1300416 Title: Install of 14.04 fails with 3.13.0-20-generic kernel Status in “linux” package in Ubuntu: New Bug description: I've tried installing the latest daily build of Trusty server, with a 3.13.0-20-generic kernel, on several Lenovo ThinkPad models (X121e, X131e, and L330). It's failed on every one of them. The installer hangs on an empty purple screen (see screen shot). Switching to VT4 reveals kernel error messages, which also appear in /var/log/syslog. (A bash shell can be obtained on VT2 or VT3 to retrieve this log file.) I'm attaching a copy of the log file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1300416] Re: Install of 14.04 fails with 3.13.0-20-generic kernel
** Attachment added: /var/log/syslog from hung system. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300416/+attachment/4056313/+files/syslog -- 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/1300416 Title: Install of 14.04 fails with 3.13.0-20-generic kernel Status in “linux” package in Ubuntu: New Bug description: I've tried installing the latest daily build of Trusty server, with a 3.13.0-20-generic kernel, on several Lenovo ThinkPad models (X121e, X131e, and L330). It's failed on every one of them. The installer hangs on an empty purple screen (see screen shot). Switching to VT4 reveals kernel error messages, which also appear in /var/log/syslog. (A bash shell can be obtained on VT2 or VT3 to retrieve this log file.) I'm attaching a copy of the log file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1300416] Re: Install of 14.04 fails with 3.13.0-20-generic kernel
** Attachment added: output of cat /proc/version_signature on an affected machine https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300416/+attachment/4056366/+files/version_signature.txt -- 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/1300416 Title: Install of 14.04 fails with 3.13.0-20-generic kernel Status in “linux” package in Ubuntu: Incomplete Bug description: I've tried installing the latest daily build of Trusty server, with a 3.13.0-20-generic kernel, on several Lenovo ThinkPad models (X121e, X131e, and L330). It's failed on every one of them. The installer hangs on an empty purple screen (see screen shot). Switching to VT4 reveals kernel error messages, which also appear in /var/log/syslog. (A bash shell can be obtained on VT2 or VT3 to retrieve this log file.) I'm attaching a copy of the log file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1300416] Re: Install of 14.04 fails with 3.13.0-20-generic kernel
** Attachment added: Output of lspci -vnvn on an affected machine https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300416/+attachment/4056365/+files/lspci-vnvn.txt -- 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/1300416 Title: Install of 14.04 fails with 3.13.0-20-generic kernel Status in “linux” package in Ubuntu: Incomplete Bug description: I've tried installing the latest daily build of Trusty server, with a 3.13.0-20-generic kernel, on several Lenovo ThinkPad models (X121e, X131e, and L330). It's failed on every one of them. The installer hangs on an empty purple screen (see screen shot). Switching to VT4 reveals kernel error messages, which also appear in /var/log/syslog. (A bash shell can be obtained on VT2 or VT3 to retrieve this log file.) I'm attaching a copy of the log file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1300416] Re: Install of 14.04 fails with 3.13.0-20-generic kernel
The installation fails and apport-collect is unavailable in the installation environment. Therefore, I'm unable to run this command. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- 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/1300416 Title: Install of 14.04 fails with 3.13.0-20-generic kernel Status in “linux” package in Ubuntu: Confirmed Bug description: I've tried installing the latest daily build of Trusty server, with a 3.13.0-20-generic kernel, on several Lenovo ThinkPad models (X121e, X131e, and L330). It's failed on every one of them. The installer hangs on an empty purple screen (see screen shot). Switching to VT4 reveals kernel error messages, which also appear in /var/log/syslog. (A bash shell can be obtained on VT2 or VT3 to retrieve this log file.) I'm attaching a copy of the log file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1300416] Re: Install of 14.04 fails with 3.13.0-20-generic kernel
No, an Ethernet cable doesn't seem to have any effect. My initial report was with Ethernet connected. I've since tried with it disconnected, and the symptoms look the same. I'm attaching /var/log/syslog from the cable-disconnected case, though, in case that gives you any more clues. ** Attachment added: /var/log/syslog from system with Ethernet cable unplugged https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300416/+attachment/4056595/+files/syslog -- 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/1300416 Title: Install of 14.04 fails with 3.13.0-20-generic kernel Status in “linux” package in Ubuntu: Confirmed Bug description: I've tried installing the latest daily build of Trusty server, with a 3.13.0-20-generic kernel, on several Lenovo ThinkPad models (X121e, X131e, and L330). It's failed on every one of them. The installer hangs on an empty purple screen (see screen shot). Switching to VT4 reveals kernel error messages, which also appear in /var/log/syslog. (A bash shell can be obtained on VT2 or VT3 to retrieve this log file.) I'm attaching a copy of the log file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1154749] Re: reboot does a shutdown instead of rebooting (OCP v2)
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 has frequently been coming up without access to the i350 Ethernet hardware. This isn't happening 100% of the time, but it is happening quite often -- maybe 90% of the time. Finally, I'm seeing the following kernel errors when using dcmitool in- band: [ 256.029897] BUG: scheduling while atomic: dcmitool/2056/0x0002 [ 256.029956] Modules linked in: dcmi(OF) snd_hda_codec_hdmi snd_hda_intel snd_hda_codec intel_rapl radeon snd_hwdep snd_pcm snd_page_alloc snd_timer x86_pkg_temp_thermal intel_powerclamp snd coretemp soundcore kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel sb_edac ppdev lp aes_x86_64 ttm drm_kms_helper psmouse drm edac_core serio_raw joydev parport_pc mei_me parport lrw gf128mul glue_helper ablk_helper cryptd mei lpc_ich mac_hid igb i2c_algo_bit hid_generic isci dca e1000e usbhid libsas ptp hid ahci libahci pps_core scsi_transport_sas [ 256.030019] CPU: 9 PID: 2056 Comm: dcmitool Tainted: GF W O 3.13.0-17-lowlatency #37 [ 256.030022] Hardware name: Quanta Freedom/Windmill-EP, BIOS F03_3A07 03/02/2012 [ 256.030025] 882c7fc34600 881212f0bc50 81715e6d 7fff [ 256.030034] 881212f0bc60 8170feec 881212f0bcc0 817198de [ 256.030041] 881209a76040 881212f0bfd8 00014600 00014600 [ 256.030049] Call Trace: [ 256.030058] [81715e6d] dump_stack+0x4d/0x6f [ 256.030064] [8170feec] __schedule_bug+0x4c/0x5a [ 256.030070] [817198de] __schedule+0x6de/0x7f0 [ 256.030077] [81719a19] schedule+0x29/0x70 [ 256.030083] [81718c39] schedule_timeout+0x279/0x320 [ 256.030089] [81094cbb] ? ttwu_stat+0x9b/0x110 [ 256.030096] [8171ae1c] wait_for_completion+0x9c/0x100 [ 256.030103] [8109ae90] ? wake_up_state+0x20/0x20 [ 256.030110] [8108bfda] kthread_stop+0x4a/0x130 [ 256.030118] [a0277f7d] dcmi_transport_close+0x6d/0x120 [dcmi] [ 256.030124] [a02776d9] dcmi_disconnect+0x29/0x40 [dcmi] [ 256.030130] [a0278d0e] dcmi_release+0x2e/0xa0 [dcmi] [ 256.030137] [811beb13] __fput+0xd3/0x250 [ 256.030143] [811becde] fput+0xe/0x10 [ 256.030154] [810888f4] task_work_run+0xc4/0xe0 [ 256.030162] [8106a816] do_exit+0x2a6/0xa90 [ 256.030169] [8109e8a4] ? vtime_account_user+0x54/0x60 [ 256.030175] [8106b07f] do_group_exit+0x3f/0xa0 [ 256.030180] [8106b0f4] SyS_exit_group+0x14/0x20 [ 256.030187] [817252ff] tracesys+0xe1/0xe6 Once, the computer spontaneously rebooted a few seconds after I used dcmitool. I don't know if that's connected to the kernel error messages, though. -- 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 of rebooting (OCP v2) Status in OEM Priority Project: Invalid Status in Open Compute Project: New Status in “linux” package in Ubuntu: Confirmed Bug description: On the OCP v2 compliant system (Windmill OCP motherboard v2), the system hang at the reboot startup. This issue happens on 12.04.1, 12.04.2 and 12.10. The work around in http://ubuntuforums.org/showthread.php?t=2024096, blacklisting mei, works. Note the first reboot doesn't work, but the subsequent reboots work. mei in 12.04.1 $ modinfo mei filename: /lib/modules/3.2.0-38-generic/kernel/drivers/staging/mei/mei.ko version:7.1.20.1 license:GPL v2 description:Intel(R) Management Engine Interface author: Intel Corporation srcversion: 9252880194B02634B5F0427 Kernel mei message before blacklisted: kernel: [6.961623] mei: module is from the staging directory, the quality is unknown, you have been warned. kernel: [6.962226] mei :00:16.0: PCI INT A - GSI 16 (level, low) - IRQ 16 kernel: [6.962235] mei :00:16.0: setting latency timer to 64 kernel: [6.962310] mei :00:16.0: irq 104 for MSI/MSI-X mei in 12.04.2 $ modinfo mei filename: /lib/modules/3.5.0-25-generic/kernel/drivers/misc/mei/mei.ko license:GPL v2 description:Intel(R) Management Engine Interface author: Intel Corporation srcversion: 0580619CB5DEF6AB7228EBE Kernel mei message before blacklisted: kernel: [6.543470] mei :00:16.0: setting latency timer to 64 kernel: [6.543547] mei :00:16.0: irq 104 for MSI/MSI-X kernel: [6.547516] mei :00:16.0: wd: failed to find the client mei in 12.10 $ modinfo mei filename:
[Kernel-packages] [Bug 1154749] Re: reboot does a shutdown instead of rebooting (OCP v2)
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 caused the EFI-mode reboot failures noted in my previous report. -- 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 of rebooting (OCP v2) Status in OEM Priority Project: Invalid Status in Open Compute Project: New Status in “linux” package in Ubuntu: Confirmed Bug description: On the OCP v2 compliant system (Windmill OCP motherboard v2), the system hang at the reboot startup. This issue happens on 12.04.1, 12.04.2 and 12.10. The work around in http://ubuntuforums.org/showthread.php?t=2024096, blacklisting mei, works. Note the first reboot doesn't work, but the subsequent reboots work. mei in 12.04.1 $ modinfo mei filename: /lib/modules/3.2.0-38-generic/kernel/drivers/staging/mei/mei.ko version:7.1.20.1 license:GPL v2 description:Intel(R) Management Engine Interface author: Intel Corporation srcversion: 9252880194B02634B5F0427 Kernel mei message before blacklisted: kernel: [6.961623] mei: module is from the staging directory, the quality is unknown, you have been warned. kernel: [6.962226] mei :00:16.0: PCI INT A - GSI 16 (level, low) - IRQ 16 kernel: [6.962235] mei :00:16.0: setting latency timer to 64 kernel: [6.962310] mei :00:16.0: irq 104 for MSI/MSI-X mei in 12.04.2 $ modinfo mei filename: /lib/modules/3.5.0-25-generic/kernel/drivers/misc/mei/mei.ko license:GPL v2 description:Intel(R) Management Engine Interface author: Intel Corporation srcversion: 0580619CB5DEF6AB7228EBE Kernel mei message before blacklisted: kernel: [6.543470] mei :00:16.0: setting latency timer to 64 kernel: [6.543547] mei :00:16.0: irq 104 for MSI/MSI-X kernel: [6.547516] mei :00:16.0: wd: failed to find the client mei in 12.10 $ modinfo mei filename: /lib/modules/3.5.0-21-generic/kernel/drivers/misc/mei/mei.ko license:GPL v2 description:Intel(R) Management Engine Interface author: Intel Corporation srcversion: 0580619CB5DEF6AB7228EBE Kernel mei message before blacklisted: kernel: [4.731997] mei :00:16.0: setting latency timer to 64 kernel: [4.736801] mei :00:16.0: irq 104 for MSI/MSI-X kernel: [4.741695] mei :00:16.0: wd: failed to find the client To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1154749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1154749] Re: reboot does a shutdown instead of rebooting (OCP v2)
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 member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1154749 Title: reboot does a shutdown instead of rebooting (OCP v2) Status in OEM Priority Project: Invalid Status in Open Compute Project: New Status in “linux” package in Ubuntu: Confirmed Bug description: On the OCP v2 compliant system (Windmill OCP motherboard v2), the system hang at the reboot startup. This issue happens on 12.04.1, 12.04.2 and 12.10. The work around in http://ubuntuforums.org/showthread.php?t=2024096, blacklisting mei, works. Note the first reboot doesn't work, but the subsequent reboots work. mei in 12.04.1 $ modinfo mei filename: /lib/modules/3.2.0-38-generic/kernel/drivers/staging/mei/mei.ko version:7.1.20.1 license:GPL v2 description:Intel(R) Management Engine Interface author: Intel Corporation srcversion: 9252880194B02634B5F0427 Kernel mei message before blacklisted: kernel: [6.961623] mei: module is from the staging directory, the quality is unknown, you have been warned. kernel: [6.962226] mei :00:16.0: PCI INT A - GSI 16 (level, low) - IRQ 16 kernel: [6.962235] mei :00:16.0: setting latency timer to 64 kernel: [6.962310] mei :00:16.0: irq 104 for MSI/MSI-X mei in 12.04.2 $ modinfo mei filename: /lib/modules/3.5.0-25-generic/kernel/drivers/misc/mei/mei.ko license:GPL v2 description:Intel(R) Management Engine Interface author: Intel Corporation srcversion: 0580619CB5DEF6AB7228EBE Kernel mei message before blacklisted: kernel: [6.543470] mei :00:16.0: setting latency timer to 64 kernel: [6.543547] mei :00:16.0: irq 104 for MSI/MSI-X kernel: [6.547516] mei :00:16.0: wd: failed to find the client mei in 12.10 $ modinfo mei filename: /lib/modules/3.5.0-21-generic/kernel/drivers/misc/mei/mei.ko license:GPL v2 description:Intel(R) Management Engine Interface author: Intel Corporation srcversion: 0580619CB5DEF6AB7228EBE Kernel mei message before blacklisted: kernel: [4.731997] mei :00:16.0: setting latency timer to 64 kernel: [4.736801] mei :00:16.0: irq 104 for MSI/MSI-X kernel: [4.741695] mei :00:16.0: wd: failed to find the client To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1154749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
