[coreboot] Re: [linux-mei] intelmetool crashed mei_me driver

2019-01-22 Thread Shawn
intelmetool is for ME( desktop/laptop/etc) and we barely use it on SPS. We tested it on a pre-broadwell machine and it works fine. Could it be an issue related to the specific ME OS, e.g: the different impls of handling stuff from mei_me between MINIX-based and ThreadX? On Tue, Jan 22, 2019 at

[coreboot] Re: Fallback mechanisms on x86 with C_ENVIRONMENT_BOOTBLOCK

2019-01-22 Thread Julius Werner
> There's a trycount that I think defaults to 10. After 10 failing tries it > should switch slots. There's also a 'set good firmware' notion which signals > to the firmware one was able to boot. This is picked up on the next reboot > and the information is passed through vboot non volatile

[coreboot] Re: Fallback mechanisms on x86 with C_ENVIRONMENT_BOOTBLOCK

2019-01-22 Thread Aaron Durbin via coreboot
On Tue, Jan 22, 2019 at 6:45 AM Arthur Heymans wrote: > Hi > > As more and more x86 platforms are moving to C_ENVIRONMENT_BOOTBLOCK > and therefore don't use a romcc compiled bootblock anymore a certain > question arises. With the romcc bootblock there was a normal/fallback > mechanism. > > It

[coreboot] Re: Testing modernizing patches on ASUS KGPE-D16. (was Re: Asus KGPE-D16 with latest coreboot errors with Unsupported Hardware on Qubes 4 install missing IOMMU?)

2019-01-22 Thread Ivan Ivanov
Sorry for a late reply, but have you tried repairing/replacing the chips (capacitors?) on the bottom of your G34 cpu? чт, 20 дек. 2018 г. в 00:29, taii...@gmx.com : > > On 12/18/2018 01:56 PM, Daniel Kulesz via coreboot wrote: > > Hi folks, > > > > is there a branch that has all the outstanding

[coreboot] Re: Coreboot doesn't POST on ASUS KCMA-D8

2019-01-22 Thread Ivan Ivanov
Hi Sean, libreboot is always behind coreboot regarding the commits, so RAM compatibility could vary because of some breaking commit that happened after the latest libreboot release but before the latest coreboot. So of course it would break at the next libreboot release as well. You could prevent

[coreboot] Re: [linux-mei] intelmetool crashed mei_me driver

2019-01-22 Thread Winkler, Tomas
First time I see it. My guess is this tool is for SPS and it will conflict with the mei driver on clients platform (mobile, desktop, workstations) It messes up the drive state machine, hence the error I've removed recently the BUG() from the drivers so I guess on 4.20 it won't crash, but still

[coreboot] Re: [linux-mei] intelmetool crashed mei_me driver

2019-01-22 Thread Winkler, Tomas
What is intelmeitool? Thanks Tomas > -Original Message- > From: linux-mei-requ...@eclists.intel.com [mailto:linux-mei- > requ...@eclists.intel.com] On Behalf Of Shawn > Sent: Tuesday, January 22, 2019 10:30 > To: linux-...@linux.intel.com; coreboot > Subject: [linux-mei] intelmetool

[coreboot] Fallback mechanisms on x86 with C_ENVIRONMENT_BOOTBLOCK

2019-01-22 Thread Arthur Heymans
Hi As more and more x86 platforms are moving to C_ENVIRONMENT_BOOTBLOCK and therefore don't use a romcc compiled bootblock anymore a certain question arises. With the romcc bootblock there was a normal/fallback mechanism. It works the following way: It uses RTC cmos to select between the normal

[coreboot] Re: [linux-mei] intelmetool crashed mei_me driver

2019-01-22 Thread Shawn
use this one: https://github.com/coreboot/coreboot/tree/master/util/intelmetool On Tue, Jan 22, 2019 at 4:32 PM Winkler, Tomas wrote: > > What is intelmeitool? > Thanks > Tomas > > > > -Original Message- > > From: linux-mei-requ...@eclists.intel.com [mailto:linux-mei- > >

[coreboot] intelmetool crashed mei_me driver

2019-01-22 Thread Shawn
Hi, intelmetool crashed mei_me driver and you can reproduce it via: -- #!/bin/bash counter=0 while [ $counter -le 1000 ] do ./intelmetool -m >> /tmp/me.log echo $counter sleep 5 counter=$(($counter + 1)) done -- The kernel crash