Bug 109579 - [CI][DRMTIP] igt@runner@aborted - fail - Previous test: gem_mmap_gtt (hang), Kernel tainted (0x240 -- 200)
Summary: [CI][DRMTIP] igt@runner@aborted - fail - Previous test: gem_mmap_gtt (hang), ...
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-07 13:55 UTC by Martin Peres
Modified: 2019-03-06 16:25 UTC (History)
1 user (show)

See Also:
i915 platform: BXT
i915 features: firmware/guc


Attachments

Description Martin Peres 2019-02-07 13:55:36 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_198/fi-apl-guc/igt%40gem_mmap_gtt%40hang.html

Aborting.
Previous test: gem_mmap_gtt (hang)
Next test: gem_pwrite (huge-cpu-forwards)

Kernel tainted (0x240 -- 200)


I don't see where the tainting is happening... but it happened, so that's why I file the bug!
Comment 1 CI Bug Log 2019-02-07 13:56:13 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* GUC: igt@runner@aborted - fail - Previous test: gem_mmap_gtt (hang), Kernel tainted (0x240 -- 200)
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_198/fi-apl-guc/igt@runner@aborted.html
Comment 2 Chris Wilson 2019-02-07 14:04:57 UTC
Just
<3> [196.216777] i915 0000:00:02.0: GPU recovery failed
but it's a stale bug from deleted code affecting the guc...
Comment 3 Martin Peres 2019-03-06 16:25:46 UTC
(In reply to Chris Wilson from comment #2)
> Just
> <3> [196.216777] i915 0000:00:02.0: GPU recovery failed
> but it's a stale bug from deleted code affecting the guc...

If the code has been deleted, then whatever :) Thanks!
Comment 4 CI Bug Log 2019-03-06 16:25:54 UTC
The CI Bug Log issue associated to this bug has been archived.

New failures matching the above filters will not be associated to this bug anymore.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.