< said:
> If you're using a Skylake, I suspect that you can set the
> hw.skz63_enable tunable to 0 as a workaround, assuming you're not using
> any code that relies on Intel TSX. (I don't think there's anything in
> the base system that does.) There are some details in
>
On Sun, Nov 25, 2018 at 11:35:30PM -0500, Garrett Wollman wrote:
> < said:
>
> > On Sun, Nov 18, 2018 at 08:24:38PM -0500, Garrett Wollman wrote:
> >> Has anyone seen this before? It's on a busy NFS server, but hasn't
> >> been observed on any of our other NFS servers.
> >>
> >>
<
said:
> On Sun, Nov 18, 2018 at 08:24:38PM -0500, Garrett Wollman wrote:
>> Has anyone seen this before? It's on a busy NFS server, but hasn't
>> been observed on any of our other NFS servers.
>>
>>
>> Fatal trap 12:
On Sun, Nov 18, 2018 at 08:24:38PM -0500, Garrett Wollman wrote:
> Has anyone seen this before? It's on a busy NFS server, but hasn't
> been observed on any of our other NFS servers.
>
>
> Fatal trap 12: page fault while in
Has anyone seen this before? It's on a busy NFS server, but hasn't
been observed on any of our other NFS servers.
Fatal trap 12: page fault while in kernel mode
cpuid = 35; apic id = 35
fault virtual address = 0x5a
fault
