https://bugs.freedesktop.org/show_bug.cgi?id=87658
--- Comment #16 from Patrick Baggett ---
That is strange...I would have expected an "illegal instruction" (SIGILL) if
the CPU simply did not support this, but this is SIGSEGV. Is the 'fxsave'
struct really aligned properly? It looks like should b
https://bugs.freedesktop.org/show_bug.cgi?id=87658
--- Comment #15 from Chris Paulson-Ellis ---
Oops - printed the wrong array...
(gdb) p /x regs2
$11 = {, 0x1080e, 0x4400, 0xbfebf9ff}
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freedesktop.org/show_bug.cgi?id=87658
--- Comment #14 from Chris Paulson-Ellis ---
(In reply to David Heidelberg (okias) from comment #13)
> Created attachment 111431 [details] [review]
> 0001-util-add-check-for-bit_FXSAVE.patch
>
> In case your CPU doesn't have FXSAVE support, this
https://bugs.freedesktop.org/show_bug.cgi?id=87658
David Heidelberg (okias) changed:
What|Removed |Added
Attachment #111297|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=87658
--- Comment #12 from David Heidelberg (okias) ---
(In reply to ubizjak from comment #11)
> (In reply to David Heidelberg (okias) from comment #9)
> > I'd say it's kernel (more probably) or gcc bug.
>
> Nope. You have to check FXSAVE bit in cpuid
https://bugs.freedesktop.org/show_bug.cgi?id=87658
--- Comment #11 from ubiz...@gmail.com ---
(In reply to David Heidelberg (okias) from comment #9)
> I'd say it's kernel (more probably) or gcc bug.
Nope. You have to check FXSAVE bit in cpuid.
> For gcc, try 4.7.x and/or 4.9.x if you can.
>
> F
https://bugs.freedesktop.org/show_bug.cgi?id=87658
--- Comment #10 from Chris Paulson-Ellis ---
(In reply to David Heidelberg (okias) from comment #9)
> I'd say it's kernel (more probably) or gcc bug.
For the record...
$ uname -r
3.17.7-200.fc20.i686
$ dmesg | grep gcc
[0.00] Linux ver
https://bugs.freedesktop.org/show_bug.cgi?id=87658
--- Comment #9 from David Heidelberg (okias) ---
I'd say it's kernel (more probably) or gcc bug.
For gcc, try 4.7.x and/or 4.9.x if you can.
For kernel, I think it may be(?) related to [1]- > Paranoid restore. send a
SIGSEGV if we fail to resto
https://bugs.freedesktop.org/show_bug.cgi?id=87658
--- Comment #8 from Chris Paulson-Ellis ---
(In reply to David Heidelberg (okias) from comment #6)
> > > 0001-util-improve-fxsave-detection.patch
> try compile with CFLAGS="-mfxsr"
Somewhat inevitably, given the result of the second patch...
Pr