Re: [coreboot] How does intelmetool's support for Skylake?

[Shawn]

Hi Zoran,

I created hwdb.bin via:

# udevadm hwdb --update

The result is still "segfault". dmesg:

[  972.044664] intelmetool[5055]: segfault at 16 ip 000000000040169e
sp 000072ed96a44680 error 4 in intelmetool[400000+6000]
[  972.044674] grsec: Segmentation fault occurred at 0000000000000016
in /usr/local/bin/intelmetool[intelmetool:5055] uid/euid:0/0
gid/egid:0/0, parent /bin/bash[bash:4332] uid/euid:0/0 gid/egid:0/0
[  972.044685] grsec: denied resource overstep by requesting 4096 for
RLIMIT_CORE against limit 0 for
/usr/local/bin/intelmetool[intelmetool:5055] uid/euid:0/0
gid/egid:0/0, parent /bin/bash[bash:4332] uid/euid:0/0 gid/egid:0/0

On Mon, Dec 26, 2016 at 9:49 PM, Zoran Stojsavljevic
 wrote:
> Not sure if your strace log has anything to do with intelmetool.
>
> I did on your strace log the following (and in RED is possible cause of your
> problems):
>
> [zoran@localhost projects]$ cat crash.log | grep ENOENT
> access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or
> directory)
> access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or
> directory)
> access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or
> directory)
> access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or
> directory)
> access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or
> directory)
> access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or
> directory)
> access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or
> directory)
> access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or
> directory)
> access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or
> directory)
> open("/usr/share/misc/pci.ids.gz", O_RDONLY) = -1 ENOENT (No such file or
> directory)
> connect(4, {sa_family=AF_LOCAL, sun_path="/var/run/nscd/socket"}, 110) = -1
> ENOENT (No such file or directory)
> connect(4, {sa_family=AF_LOCAL, sun_path="/var/run/nscd/socket"}, 110) = -1
> ENOENT (No such file or directory)
> access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or
> directory)
> access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or
> directory)
> access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or
> directory)
> access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or
> directory)
> open("/root/.pciids-cache", O_RDONLY)   = -1 ENOENT (No such file or
> directory)
> open("/etc/systemd/hwdb/hwdb.bin", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such
> file or directory)
> open("/etc/udev/hwdb.bin", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or
> directory)
> open("/usr/lib/systemd/hwdb/hwdb.bin", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No
> such file or directory)
> open("/lib/systemd/hwdb/hwdb.bin", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such
> file or directory)
> [zoran@localhost projects]$
>
> I guess, you have one very important missing file in your Linux
> configuration, this one: /etc/systemd/hwdb/hwdb.bin... /etc/udev/hwdb.bin ?!
>
> Here is good read:
> https://www.freedesktop.org/software/systemd/man/hwdb.html
> http://www.dsm.fordham.edu/cgi-bin/man-cgi.pl?topic=systemd-hwdb&sect=8
>
> Have no idea who is creating this file, but you can check your Linux distro
> / tree with the following paths to find hwdb.bin:
>
> /etc/systemd/hwdb/hwdb.bin
> /etc/udev/hwdb.bin                    <<======= In my Fedora rawhide VM
> (future Fedora 26) I have here hwdb.bin =======
> /usr/lib/systemd/hwdb/hwdb.bin
> /lib/systemd/hwdb/hwdb.bin
>
> If you don't have in any, please, create one with the following link:
> http://www.dsm.fordham.edu/cgi-bin/man-cgi.pl?topic=systemd-hwdb&sect=8
>
> Please, let us know!
>
> Zoran
>
> On Mon, Dec 26, 2016 at 3:42 PM, Shawn  wrote:
> > Hi,
> >
> > intelmetool occurs "segfault" on my laptop running Mint 18 with
> > PaX/Grsecurity 4.7.10. The PCI info:
> >
> > -[0000:00]-+-00.0  Intel Corporation Sky Lake Host Bridge/DRAM
> > Registers [8086:1904]
> >            +-02.0  Intel Corporation Sky Lake Integrated Graphics
> > [8086:1916]
> >            +-04.0  Intel Corporation Skylake Processor Thermal
> > Subsystem [8086:1903]
> >            +-14.0  Intel Corporation Sunrise Point-LP USB 3.0 xHCI
> > Controller [8086:9d2f]
> >            +-14.2  Intel Corporation Sunrise Point-LP Thermal
> > subsystem [8086:9d31]
> >            +-15.0  Intel Corporation Sunrise Point-LP Serial IO I2C
> > Controller [8086:9d60]
> >            +-15.1  Intel Corporation Sunrise Point-LP Serial IO I2C
> > Controller [8086:9d61]
> >            +-16.0  Intel Corporation Sunrise Point-LP CSME HECI
> > [8086:9d3a]
> >            +-1c.0-[01]----00.0  NVIDIA Corporation GM107M [GeForce GTX
> > 960M] [10de:139b]
> >            +-1c.4-[02]----00.0  Samsung Electronics Co Ltd NVMe SSD
> > Controller [144d:a802]
> >            +-1c.6-[03]----00.0  Qualcomm Atheros Killer E2400 Gigabit
> > Ethernet Controller [1969:e0a1]
> >            +-1c.7-[04]----00.0  Qualcomm Atheros QCA6174 802.11ac
> > Wireless Network Adapter [168c:003e]
> >            +-1d.0-[05]----00.0  Samsung Electronics Co Ltd NVMe SSD
> > Controller [144d:a802]
> >            +-1d.2-[06-3e]--
> >            +-1f.0  Intel Corporation Sunrise Point-LP LPC Controller
> > [8086:9d48]
> >            +-1f.2  Intel Corporation Sunrise Point-LP PMC [8086:9d21]
> >            +-1f.3  Intel Corporation Sunrise Point-LP HD Audio [8086:9d70]
> >            -1f.4  Intel Corporation Sunrise Point-LP SMBus [8086:9d23]
> >
> > The crash log was attached! I'm not sure if intelmetool support
> > Skylake as well. One tiny feature of PaX/Grsecurity prevent the ioperm
> > for killing the potential threats in case which
> > the adversary re-flash the SPI ROM once they get the root priv. It
> > does affect flashrom but intelmetool. I also ran intelmetool on the
> > distro( Mint 18) kernel and got the same result.
> >
> > regards
> > Shawn