On Wed, 17 Aug 2016, Peter Zijlstra wrote:
> On Tue, Aug 09, 2016 at 11:51:48AM -0400, Vince Weaver wrote:
> >
> > So still haswell/4.8-rc1, after 6 hours of fuzzing this is where the
> > system finally locked up permanently.
> >
> > It looks like some sort of spinlock error.
> > The logs
On Wed, 17 Aug 2016, Peter Zijlstra wrote:
> On Tue, Aug 09, 2016 at 11:51:48AM -0400, Vince Weaver wrote:
> >
> > So still haswell/4.8-rc1, after 6 hours of fuzzing this is where the
> > system finally locked up permanently.
> >
> > It looks like some sort of spinlock error.
> > The logs
On Tue, Aug 09, 2016 at 11:51:48AM -0400, Vince Weaver wrote:
>
> So still haswell/4.8-rc1, after 6 hours of fuzzing this is where the
> system finally locked up permanently.
>
> It looks like some sort of spinlock error.
> The logs continued being spammed with this stuff overnight until I
>
On Tue, Aug 09, 2016 at 11:51:48AM -0400, Vince Weaver wrote:
>
> So still haswell/4.8-rc1, after 6 hours of fuzzing this is where the
> system finally locked up permanently.
>
> It looks like some sort of spinlock error.
> The logs continued being spammed with this stuff overnight until I
>
So still haswell/4.8-rc1, after 6 hours of fuzzing this is where the
system finally locked up permanently.
It looks like some sort of spinlock error.
The logs continued being spammed with this stuff overnight until I
finally put it out of its misery, but I think just the beginning here
is the
So still haswell/4.8-rc1, after 6 hours of fuzzing this is where the
system finally locked up permanently.
It looks like some sort of spinlock error.
The logs continued being spammed with this stuff overnight until I
finally put it out of its misery, but I think just the beginning here
is the
6 matches
Mail list logo
