| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <5B8DA87D05A7694D9FA63FD143655C1B1AFB7151@HASMSX106.ger.corp.intel.com> Date: Mon, 7 Apr 2014 13:10:40 +0000 From: "Winkler, Tomas" <tomas.winkler@...el.com> To: Nikola Ciprich <nikola.ciprich@...uxbox.cz> CC: "Greg KH (gregkh@...uxfoundation.org)" <gregkh@...uxfoundation.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: RE: 3.0 -> 3.10 regression? poweroff instead of reboot? > > Hello Tomas, > > I would need the devices ids of the MEI device on your platform (lspci will do > the job), is this same platform as you tested before? > > You should not get to requesting the HW readiness w/ my patch. > > yes, it's the same box. > > here are the IDs: > > 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series > Chipset Family MEI Controller #1 (rev 04) > 00:16.1 Communication controller: Intel Corporation 6 Series/C200 Series > Chipset Family MEI Controller #2 (rev 04) > > 00:16.0 0780: 8086:1c3a (rev 04) > 00:16.1 0780: 8086:1c3b (rev 04) Are use you have the patch applied, because the driver just should not load. If any case you dump the firmware status registers" At offset 0x40 and 0x48 in PCI config space sudo hexdump -s 0x48 -n 4 /proc/bus/pci/00/16.0 sudo hexdump -s 0x40 -n 4 /proc/bus/pci/00/16.0 Thanks Tomas -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists