(In reply to Andy Furniss from comment #81)
> Recently needed to re-locate and while doing so updated to 4.1.10 = hard
> lock after 7 days uptime. The kernel was not the only difference as I
> attached a usb printer and so have usb module and cups running now, though
> the printer had been off f
My Asrock Q1900DC was originally bought to be a headless router/pvr/nas
which it now is - so no more testing of this lock from me for a long
time (or so I thought).
When putting it to its new duties I put a vanilla 4.1.1 on it (didn't
patch as being headless I don't get any i915 interrupts). All w
(In reply to Andy Furniss from comment #17)
> (In reply to Andy Furniss from comment #16)
> > (In reply to Andy Furniss from comment #15)
> >
> > > I only recently started seeing locks - turns out that dri3 was OK for me,
> > > but of course it then got disabled by default and I started getting lo
(In reply to Andy Furniss from comment #16)
> (In reply to Andy Furniss from comment #15)
>
> > I only recently started seeing locks - turns out that dri3 was OK for me,
> > but of course it then got disabled by default and I started getting locks.
>
> It seems I was a bit hasty in calling dri3 O
(In reply to Andy Furniss from comment #15)
> I only recently started seeing locks - turns out that dri3 was OK for me,
> but of course it then got disabled by default and I started getting locks.
It seems I was a bit hasty in calling dri3 OK - I can lock if I try long
enough, just that it takes
(In reply to Chris Wilson from comment #13)
> Implemented the bspec recommendation:
>
> commit d247cb7d0cdb73736f31612157e47f166af68ba0
> Author: Chris Wilson
> Date: Mon Dec 8 10:07:25 2014 +
>
> sna/gen6: Poke PSMI control around WAIT_FOR_EVENT to prevent idling
>
> The bspe
6 matches
Mail list logo
