Hi, I think there might be another clue on this one.
One of the comments is also mentioning an unfixed erratum of certain
Baytrail processors, named as "EOI Transaction May Not be Sent if
Software Enters Core C6 During an Interrupt Service Routine". This
erratum can be found on several different processors, even on several
non-baytrails, like Inte Xeon 3400 and similar.
I also came across a patch that was created for SUSE and that seems to
be adressing this issue in pre 4.X kernels:
Dne 18.7.2016 15:30, One Thousand Gnomes napsal:
On Tue, 12 Jul 2016 16:41:58 -0300
Ezequiel Garcia <ezequ...@vanguardiasur.com.ar> wrote:
(Adding interested people to this thread)
On 09 Apr 08:14 PM, One Thousand Gnomes wrote:
> > > I do feel that the importance of the mentioned bug is currently
> > > underestimated. Can anyone here give a note, how much current linux
> > > kernel is supposed to be stable on general baytrail machines?
> > If you did not get any replies... you might want to check MAINTAINERS file,
> > put Intel x86 maintainers on Cc list.
> > I'm sure someone cares :-).
> Yes we care, and there are people looking at the various reports.
Are there any updates on the status of this issue?
The current bugzilla report  marks this as a power management
issue. However, many reports indicate that it would only freeze
when running X, so it's not completely clear if it's related to
the gfx driver too.
There are two things we are currently tracking. One of them was merged
which seems to have made my machine stable at least and fixes a problem
related to the MMC. The second one we may need is a power related
to SPI to hold the CPU in C0/C1 whenever the ACPI _SEM is held.
Graphics shows these problems up because of the way the GPU causes
Intel-gfx mailing list