autoport segfault on ibexpeak

[Stefan Tauner]

Hi,

since the rebase of the existing t410s patch to current master was
non-trivial (for me anyway) so I gave autoport a shot without knowing
that it currently does not support ibexpeak (5 series). This became
quite obvious from the output... but that's not the main reason why I am
writing (although I'd be interested regrading support for earlier
chipsets to autoport) but...

1) autoport segfaults on the t410s with vendor bios and that should
definitely be fixed IMHO.
2) about a dozen or so seconds after running autoport my laptop
completely locks up. Any ideas why this might happen?

Stdio/err is log attached. FWIW autoport also wrote the following log
files:

-rw-r--r-- 1 root root 329204 May  3 23:24 acpidump.log
-rw-r--r-- 1 root root   9464 May  3 23:24 codec#0
-rw-r--r-- 1 root root   3598 May  3 23:24 codec#3
-rw-r--r-- 1 root root   3444 May  3 23:24 cpuinfo.log
-rw-r--r-- 1 root root  15925 May  3 23:24 dmidecode.log
-rw-r--r-- 1 root root      0 May  3 23:24 ectool.log
-rw-r--r-- 1 root root     75 May  3 23:24 input_bustypes.log
-rw-r--r-- 1 root root 825285 May  3 23:24 inteltool.log
-rw-r--r-- 1 root root   1136 May  3 23:24 ioports.log
-rw-r--r-- 1 root root 150333 May  3 23:24 lspci.log
-rw-r--r-- 1 root root    160 May  3 23:24 pin_hwC0D0
-rw-r--r-- 1 root root     48 May  3 23:24 pin_hwC0D3

[Stefan Tauner]

On Thu, 5 May 2016 00:14:36 +0200
Stefan Tauner  wrote:
> about a dozen or so seconds after running autoport my laptop
>
> completely locks up. Any ideas why this might happen?

Felix suggested that inteltool -a might be the culprit... and I can
confirm this. However, inteltool has worked without such issues in the
past on this machine... if nobody beats me to it I'll investigate
further/bisect when time allows.

[Trammell Hudson]

On Thu, May 05, 2016 at 01:14:28AM +0200, Stefan Tauner wrote:
> Felix suggested that inteltool -a might be the culprit... and I can
> confirm this. However, inteltool has worked without such issues in the
> past on this machine... if nobody beats me to it I'll investigate
> further/bisect when time allows.

inteltool -a causes a hard lockup on my X1 with Skylake (i7-6600U).
I've been slowly trying to add support for it.

autoport also fails with a null pointer in DetectGPE, due to an
unsupported Southbridge (QM170?).

[Stefan Tauner]

On Wed, 4 May 2016 19:00:40 -0600
Trammell Hudson  wrote:
> On Thu, May 05, 2016 at 01:14:28AM +0200, Stefan Tauner wrote:
> > Felix suggested that inteltool -a might be the culprit... and I can
> > confirm this. However, inteltool has worked without such issues in the
> > past on this machine... if nobody beats me to it I'll investigate
> > further/bisect when time allows.
>
> inteltool -a causes a hard lockup on my X1 with Skylake (i7-6600U).
> I've been slowly trying to add support for it.

I could bisect the issue and it is due to the dumping of the graphics
registers (in my case). See also
https://review.coreboot.org/14624
https://review.coreboot.org/14627
> autoport also fails with a null pointer in DetectGPE, due to an
> unsupported Southbridge (QM170?).

Yes... I won't touch that for now.