search

zamaudio / intelmetool

My tool for working with Intel Management Engine - RETIRED REPO (see coreboot for new upstream)
https://review.coreboot.org/plugins/gitiles/coreboot/+/refs/heads/master/util/intelmetool
Other
156 stars 25 forks source link

Unclear output #2 - Dell E6410 #12

Closed stellaro15 closed 6 years ago

stellaro15 commented 7 years ago

Hello, I have a Dell Latitude E6410 laptop with Intel i5-520M CPU. uname -a: Linux devuan 3.16.0-4-amd64 #1 SMP Debian 3.16.43-2+deb8u2 (2017-06-26) x86_64 GNU/Linux ME chipset: 00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)

When modules mei and mei_me are loaded, the output of intelmetool -s is a following:

Bad news, you have a Mobile 5 Series Chipset LPC Interface Controller so you have ME hardware on board and you can't control or disable it, continuing...

MEI not hidden on PCI, checking if visible MEI found: [8086:3b64] 5 Series/3400 Series Chipset HECI Controller

ME Status : 0x245 ME Status 2 : 0x69000000

ME: FW Partition Table : OK ME: Bringup Loader Failure : NO ME: Firmware Init Complete : YES ME: Manufacturing Mode : NO ME: Boot Options Present : NO ME: Update In Progress : NO ME: Current Working State : Normal ME: Current Operation State : M0 with UMA ME: Current Operation Mode : Normal ME: Error Code : No Error ME: Progress Phase : Host Communication ME: Power Management Event : Non-power cycle reset ME: Progress Phase State : Host communication established

ME: Extend SHA-256: a73091cb6a59b170f398b6cbcad8668e1acd38614ad956caf55762c4530b2b00

ME: timeout waiting for data: expected 8, available 0 ME: GET FW VERSION message failed ME: response is missing data ME: invalid response, group 3 ?= 196, command 2 ?= 3, is_response 0 ME: not enough room in response buffer: 8 != 3 ME Capability: Full Network manageability : ON ME Capability: Regular Network manageability : ON ME Capability: Manageability : ON ME Capability: Small business technology : ON ME Capability: Level III manageability : ON ME Capability: IntelR Anti-Theft (AT) : ON ME Capability: IntelR Capability Licensing Service (CLS) : ON ME Capability: IntelR Power Sharing Technology (MPC) : ON ME Capability: ICC Over Clocking : ON ME Capability: Protected Audio Video Path (PAVP) : ON ME Capability: IPV6 : ON ME Capability: KVM Remote Control (KVM) : ON ME Capability: Outbreak Containment Heuristic (OCH) : ON ME Capability: Virtual LAN (VLAN) : ON ME Capability: TLS : ON ME Capability: Wireless LAN (WLAN) : ON Segmentation fault

That I suppose must be some bug, because this processor doesn't support even a half of these capabilities.

After running that, I tried unloading mei and mei_me using modprobe -r, which gave me a log in dmesg:

[ 3440.611114] mei_me 0000:00:16.0: FW not ready: resetting.
[ 3440.611138] mei_me 0000:00:16.0: unexpected reset: dev_state = ENABLED 00000245 69000000
[ 3440.611144] mei_me 0000:00:16.0: H_RST is set = 0x80000011
[ 3442.610432] mei_me 0000:00:16.0: wait hw ready failed. status = -62
[ 3442.610440] mei_me 0000:00:16.0: hw_start failed ret = -62
[ 3442.610457] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING 00000245 69000000
[ 3442.614641] ------------[ cut here ]------------
[ 3442.614706] kernel BUG at /build/linux-ch53fA/linux-3.16.43/drivers/misc/mei/hbm.c:873!
[ 3442.614809] invalid opcode: 0000 [#1] SMP 
[ 3442.614874] Modules linked in: ctr ccm pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) tun fuse lp dell_wmi sparse_keymap iTCO_wdt iTCO_vendor_support ppdev arc4 snd_hda_codec_hdmi dell_laptop dcdbas iwldvm mac80211 intel_powerclamp snd_hda_codec_idt coretemp snd_hda_codec_generic kvm_intel kvm evdev iwlwifi joydev serio_raw i915 pcspkr cfg80211 intel_ips lpc_ich mfd_core snd_hda_intel rfkill parport_pc snd_hda_controller wmi tpm_tis drm_kms_helper parport snd_hda_codec tpm battery snd_hwdep drm snd_pcm dell_smo8800 snd_timer shpchp i2c_algo_bit snd acpi_cpufreq video soundcore mei_me mei ac processor button thermal_sys ext4 crc16 mbcache jbd2 algif_skcipher af_alg usb_storage hid_generic usbhid hid dm_crypt dm_mod sg sd_mod crc_t10dif crct10dif_generic crct10dif_pclmul crct10dif_common
[ 3442.615712]  crc32_pclmul crc32c_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd ahci libahci firewire_ohci sdhci_pci sdhci psmouse libata ehci_pci ehci_hcd i2c_i801 scsi_mod i2c_core mmc_core firewire_core crc_itu_t e1000e usbcore ptp pps_core usb_common
[ 3442.616002] CPU: 0 PID: 458 Comm: irq/42-mei_me Tainted: G           O  3.16.0-4-amd64 #1 Debian 3.16.43-2+deb8u2
[ 3442.616078] Hardware name: Dell Inc. Latitude E6410/0667CC, BIOS A16 12/05/2013
[ 3442.616135] task: ffff880191d4e110 ti: ffff8800d6b2c000 task.ti: ffff8800d6b2c000
[ 3442.616192] RIP: 0010:[<ffffffffa0348730>]  [<ffffffffa0348730>] mei_hbm_dispatch+0x530/0xee0 [mei]
[ 3442.616273] RSP: 0018:ffff8800d6b2fd30  EFLAGS: 00010a83
[ 3442.616316] RAX: 000000000000002f RBX: ffff880035947000 RCX: 0000000000000004
[ 3442.616371] RDX: ffffc90000c96004 RSI: ffffc90000c96004 RDI: 00000000800c0c0d
[ 3442.616426] RBP: ffff8800359475e0 R08: ffff8800d6b2c000 R09: 0000000000000018
[ 3442.616481] R10: 0000000000000000 R11: 0000000000000006 R12: ffff8800d6b2fdcc
[ 3442.616535] R13: ffff8800d6b2fdd0 R14: ffff880035947200 R15: ffff880191d4e110
[ 3442.616590] FS:  0000000000000000(0000) GS:ffff88019bc00000(0000) knlGS:0000000000000000
[ 3442.616652] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 3442.616697] CR2: 00007f4fd24a7bf0 CR3: 0000000001813000 CR4: 00000000000007f0
[ 3442.616751] Stack:
[ 3442.616771]  ffff8800d6b2fdf4 ffff880194b9b400 ffff880035947000 ffff8800359475e0
[ 3442.616841]  ffff8800d6b2fdcc ffff8800d6b2fdd0 ffff880035947200 ffff880191d4e110
[ 3442.616910]  ffffffffa03494a0 0000000000000000 0000000000000020 0000000000000002
[ 3442.616980] Call Trace:
[ 3442.617011]  [<ffffffffa03494a0>] ? mei_irq_read_handler+0x2f0/0x740 [mei]
[ 3442.617070]  [<ffffffffa035c79d>] ? mei_me_irq_thread_handler+0x11d/0x310 [mei_me]
[ 3442.617136]  [<ffffffff81516811>] ? __schedule+0x2b1/0x6f0
[ 3442.617185]  [<ffffffff810bdb00>] ? irq_finalize_oneshot.part.30+0xd0/0xd0
[ 3442.617241]  [<ffffffff810bdb1b>] ? irq_thread_fn+0x1b/0x40
[ 3442.617286]  [<ffffffff810bde2b>] ? irq_thread+0x11b/0x140
[ 3442.617332]  [<ffffffff810bdba0>] ? irq_forced_thread_fn+0x60/0x60
[ 3442.617382]  [<ffffffff810bdd10>] ? irq_thread_check_affinity+0xc0/0xc0
[ 3442.617438]  [<ffffffff8108954d>] ? kthread+0xbd/0xe0
[ 3442.617481]  [<ffffffff81089490>] ? kthread_create_on_node+0x180/0x180
[ 3442.617535]  [<ffffffff8151a3d8>] ? ret_from_fork+0x58/0x90
[ 3442.617581]  [<ffffffff81089490>] ? kthread_create_on_node+0x180/0x180
[ 3442.617632] Code: 03 00 00 48 c7 c6 e0 3e 35 a0 31 c0 48 81 c7 98 00 00 00 e8 93 c1 05 e1 b8 b9 ff ff ff e9 2e fb ff ff 66 0f 1f 84 00 00 00 00 00 <0f> 0b 48 8b 33 48 c7 c2 18 39 35 a0 48 c7 c7 08 67 35 a0 31 c0 
[ 3442.618052] RIP  [<ffffffffa0348730>] mei_hbm_dispatch+0x530/0xee0 [mei]
[ 3442.618111]  RSP <ffff8800d6b2fd30>
[ 3442.627681] ---[ end trace e1a2844578f690be ]---
[ 3442.627729] BUG: unable to handle kernel paging request at ffffffffffffffd8
[ 3442.627816] IP: [<ffffffff81089b1c>] kthread_data+0xc/0x20
[ 3442.627890] PGD 1816067 PUD 1818067 PMD 0 
[ 3442.627946] Oops: 0000 [#2] SMP 
[ 3442.627992] Modules linked in: ctr ccm pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) tun fuse lp dell_wmi sparse_keymap iTCO_wdt iTCO_vendor_support ppdev arc4 snd_hda_codec_hdmi dell_laptop dcdbas iwldvm mac80211 intel_powerclamp snd_hda_codec_idt coretemp snd_hda_codec_generic kvm_intel kvm evdev iwlwifi joydev serio_raw i915 pcspkr cfg80211 intel_ips lpc_ich mfd_core snd_hda_intel rfkill parport_pc snd_hda_controller wmi tpm_tis drm_kms_helper parport snd_hda_codec tpm battery snd_hwdep drm snd_pcm dell_smo8800 snd_timer shpchp i2c_algo_bit snd acpi_cpufreq video soundcore mei_me mei ac processor button thermal_sys ext4 crc16 mbcache jbd2 algif_skcipher af_alg usb_storage hid_generic usbhid hid dm_crypt dm_mod sg sd_mod crc_t10dif crct10dif_generic crct10dif_pclmul crct10dif_common
[ 3442.640596]  crc32_pclmul crc32c_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd ahci libahci firewire_ohci sdhci_pci sdhci psmouse libata ehci_pci ehci_hcd i2c_i801 scsi_mod i2c_core mmc_core firewire_core crc_itu_t e1000e usbcore ptp pps_core usb_common
[ 3442.646833] CPU: 2 PID: 458 Comm: irq/42-mei_me Tainted: G      D    O  3.16.0-4-amd64 #1 Debian 3.16.43-2+deb8u2
[ 3442.649851] Hardware name: Dell Inc. Latitude E6410/0667CC, BIOS A16 12/05/2013
[ 3442.652825] task: ffff880191d4e110 ti: ffff8800d6b2c000 task.ti: ffff8800d6b2c000
[ 3442.655752] RIP: 0010:[<ffffffff81089b1c>]  [<ffffffff81089b1c>] kthread_data+0xc/0x20
[ 3442.658654] RSP: 0018:ffff8800d6b2fb00  EFLAGS: 00010202
[ 3442.661512] RAX: 0000000000000000 RBX: ffff880191d4e110 RCX: 0000000000000062
[ 3442.664357] RDX: ffff8800d6b2fe98 RSI: 0000000000000000 RDI: ffff880191d4e110
[ 3442.667190] RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000001
[ 3442.670000] R10: 0000000000000001 R11: 0000000000000005 R12: ffffffff81a6a760
[ 3442.672769] R13: ffff880191d4e110 R14: 0000000000000000 R15: ffff880191d4e110
[ 3442.675536] FS:  0000000000000000(0000) GS:ffff88019bc80000(0000) knlGS:0000000000000000
[ 3442.678328] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 3442.681123] CR2: ffffffffffffffd8 CR3: 0000000001813000 CR4: 00000000000007e0
[ 3442.683935] Stack:
[ 3442.686722]  ffffffff810bdbbe ffff880191d4e760 0000000000000000 ffffffff8108679c
[ 3442.689564]  000000000000000b 0000000000000000 0000000000000246 ffffffff81705ff1
[ 3442.692381]  ffffffff8106acd1 ffff880191d4e110 000000018151177e 0000000000000010
[ 3442.695200] Call Trace:
[ 3442.697968]  [<ffffffff810bdbbe>] ? irq_thread_dtor+0x1e/0xb0
[ 3442.700749]  [<ffffffff8108679c>] ? task_work_run+0x8c/0xb0
[ 3442.703559]  [<ffffffff8106acd1>] ? do_exit+0x2b1/0xa70
[ 3442.706322]  [<ffffffff810172a7>] ? oops_end+0x97/0xe0
[ 3442.709065]  [<ffffffff81014850>] ? do_error_trap+0x70/0xe0
[ 3442.711797]  [<ffffffffa0348730>] ? mei_hbm_dispatch+0x530/0xee0 [mei]
[ 3442.714520]  [<ffffffff8151bebe>] ? invalid_op+0x1e/0x30
[ 3442.717261]  [<ffffffffa0348730>] ? mei_hbm_dispatch+0x530/0xee0 [mei]
[ 3442.719985]  [<ffffffffa03494a0>] ? mei_irq_read_handler+0x2f0/0x740 [mei]
[ 3442.722723]  [<ffffffffa035c79d>] ? mei_me_irq_thread_handler+0x11d/0x310 [mei_me]
[ 3442.725484]  [<ffffffff81516811>] ? __schedule+0x2b1/0x6f0
[ 3442.728239]  [<ffffffff810bdb00>] ? irq_finalize_oneshot.part.30+0xd0/0xd0
[ 3442.730990]  [<ffffffff810bdb1b>] ? irq_thread_fn+0x1b/0x40
[ 3442.733725]  [<ffffffff810bde2b>] ? irq_thread+0x11b/0x140
[ 3442.736409]  [<ffffffff810bdba0>] ? irq_forced_thread_fn+0x60/0x60
[ 3442.739166]  [<ffffffff810bdd10>] ? irq_thread_check_affinity+0xc0/0xc0
[ 3442.741915]  [<ffffffff8108954d>] ? kthread+0xbd/0xe0
[ 3442.744539]  [<ffffffff81089490>] ? kthread_create_on_node+0x180/0x180
[ 3442.747041]  [<ffffffff8151a3d8>] ? ret_from_fork+0x58/0x90
[ 3442.749527]  [<ffffffff81089490>] ? kthread_create_on_node+0x180/0x180
[ 3442.752004] Code: 08 04 00 00 48 8b 40 c8 48 c1 e8 02 83 e0 01 c3 66 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 48 8b 87 08 04 00 00 <48> 8b 40 d8 c3 66 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 66 
[ 3442.757574] RIP  [<ffffffff81089b1c>] kthread_data+0xc/0x20
[ 3442.760269]  RSP <ffff8800d6b2fb00>
[ 3442.762947] CR2: ffffffffffffffd8
[ 3442.765550] ---[ end trace e1a2844578f690bf ]---
[ 3442.765553] Fixing recursive fault but reboot is needed!

So I did reset the hardware and made a run of intelmetool -s with unloaded modules mei and mei_me which give the following output:

Bad news, you have a Mobile 5 Series Chipset LPC Interface Controller so you have ME hardware on board and you can't control or disable it, continuing...

MEI not hidden on PCI, checking if visible MEI found: [8086:3b64] 5 Series/3400 Series Chipset HECI Controller

ME Status : 0x245 ME Status 2 : 0x69000000

ME: FW Partition Table : OK ME: Bringup Loader Failure : NO ME: Firmware Init Complete : YES ME: Manufacturing Mode : NO ME: Boot Options Present : NO ME: Update In Progress : NO ME: Current Working State : Normal ME: Current Operation State : M0 with UMA ME: Current Operation Mode : Normal ME: Error Code : No Error ME: Progress Phase : Host Communication ME: Power Management Event : Non-power cycle reset ME: Progress Phase State : Host communication established

ME: Extend SHA-256: a73091cb6a59b170f398b6cbcad8668e1acd38614ad956caf55762c4530b2b00

ME: timeout waiting for data: expected 8, available 0 ME: GET FW VERSION message failed ME: timeout waiting for data: expected 5, available 0 ME: GET FWCAPS message failed

Can you help me to understand which output should I follow, a first one or a second one?

zamaudio commented 6 years ago

The output after you did this is correct:

So I did reset the hardware and made a run of intelmetool -s with unloaded modules mei and mei_me which give the following output: