Re: [CI-ping 1/9] drm/i915: Include engine->last_submitted_seqno in GPU error state

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



 

Yesterday CI got lagged for a bit while I was tuning timeouts in host connectivity. We're now using nmap (instead of ping) to get better results over firewalls and long distances. Change sparked from connecting French DUT to our Jenkins.

 

The results for this series were run, but not posted for some reason, so I redid that. Lots of noise from BSW-NUC, first failed tests were in order:

 

dmesg-fail: igt/gem_cpu_reloc/basic

dmesg-fail: igt/kms_flip/basic-flip-vs-dpms

dmesg-fail: igt/gem_render_tiled_blits/basic

 

https://patchwork.freedesktop.org/series/5400/

 

Tomi

 

 

On Thursday 07 April 2016 19:11:30 Marius Vlad wrote:

> There are some results on PW: https://patchwork.freedesktop.org/series/5400/

>

> Fi CI seems to be a little bit late on the results....

>

> On Thu, Apr 07, 2016 at 04:06:49PM +0100, Chris Wilson wrote:

> > On Thu, Apr 07, 2016 at 07:29:10AM +0100, Chris Wilson wrote:

> > > It's useful to look at the last seqno submitted on a particular engine

> > > and compare it against the HWS value to check for irregularities.

> >

> > CI, what have I done to offend you?

> > -Chris

 

_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

[Index of Archives]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux