I’d prefer not to see a chase-the-kernel-version and hope-it-goes-away, like to know the root cause.  :-)

Arch’s kernel generally is tracking releases and not rcs. 4.8.4-1 

And yes I do still see the issue.

https://www.archlinux.org/packages/core/x86_64/linux/

Thanks,

Sean


On 25 DFómh 2016, at 16:37, bugzilla-daemon@freedesktop.org wrote:


Comment # 18 on bug 98311 from 
(In reply to Sean V Kelley from comment #17)
> Yes, I was going to say I've been using 4.8 on Arch and the issue is always
> there.
> 
> Sean

My last result was from upstream kernel at tag v4.8-rc8, which is not v4.8-rc8+
as Haihao tested.  @Haihao, can you be more specific about which commit id you
are on with v4.8-rc8+?  @Sean, is your kernel a 4.8 "final" or an "rc" release?

I'm trying 4.9.0-rc2+ (i.e. 9fe68cad6e74) right now, and so far I am not seeing
the issue with this version after ~100 executions.

You are receiving this mail because:
  • You are the QA Contact for the bug.

=