Bug 108787 - [BSW] Mesa "total_needs <= urb_chunks" abort in GfxBench CarChase startup
Summary: [BSW] Mesa "total_needs <= urb_chunks" abort in GfxBench CarChase startup
Status: NEW
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords: regression
Depends on:
Blocks: 101406
  Show dependency treegraph
 
Reported: 2018-11-19 14:32 UTC by Eero Tamminen
Modified: 2019-01-09 10:51 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eero Tamminen 2018-11-19 14:32:33 UTC
Setup:
* BSW N3050
* Ubuntu 18.04
* Gfx stack built from Git
* GfxBench v4 / v5 (reproduced with latter, but v4 should work the same)

Use-case:
* bin/testfw_app --gfx glfw --gl_api desktop_core --width 1920 --height 1080 --fullscreen 1 --test_id gl_4

Actual outcome:
* Abort with following message:
testfw_app: src/intel/common/gen_urb_config.c:152: gen_get_urb_config: Assertion `total_needs <= urb_chunks' failed.

This regressed between following Mesa commits:
41c8f99137: 2018-11-12 18:28:04: util: Fix warning in u_cpu_detect on non-x86
e13dd70581: 2018-11-14 14:41:58: i965: avoid 'unused variable' warnings

In case it matters:
* i965 has always misrendered Carchase benchmark on BSW, see bug 101406
* GfxBench Vulkan Aztec Ruins and SynMark DeferredAA & TexMem128 started
  to GPU hang around 6th of November, but for now this seems more of
  a drm-tip kernel than Mesa issue
Comment 1 Eero Tamminen 2018-11-28 14:25:44 UTC
CarChase still aborts on BSW N3050 to this error with latest Mesa Git version, both with v4.19 and latest v4.20-rc4 drm-tip kernels.
Comment 2 Eero Tamminen 2018-12-28 09:59:31 UTC
This regression is still happening with latest v4.20.0-rc7 drm-tip kernel & Mesa.


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.