Bug 100951 - vkcube fails with vkMapMemory failed
Summary: vkcube fails with vkMapMemory failed
Status: RESOLVED NOTOURBUG
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Vulkan/radeon (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: mesa-dev
QA Contact: mesa-dev
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-05 21:34 UTC by Fabian Maurer
Modified: 2018-01-22 16:58 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Fabian Maurer 2017-05-05 21:34:45 UTC 
When running the Vulkan demo program vkcube, it fails on vkMapMemory. When skipping the check, it segfaults.
Note that this is a regression, it used to work with the same program.


System it was tested with:
- Arch Linux 64bit
- Linux 4.10.13, AMDGPU driver
- Mesa 17.2.0-devel (git-a5f82db380) / Mesa 17.0.5
- Radeon R9 285

Demo program: https://github.com/krh/vkcube
Comment 1 Fabian Maurer 2017-06-28 19:54:40 UTC 
Still present with 7bbcf3ac70.
Comment 2 Bas Nieuwenhuizen 2017-09-09 12:10:25 UTC 
vkcube is known broken, it allocates memory from a non-mappable memory type and then tries to map it.
Comment 3 Fabian Maurer 2017-09-09 12:38:57 UTC 
(In reply to Bas Nieuwenhuizen from comment #2)
> vkcube is known broken, it allocates memory from a non-mappable memory type
> and then tries to map it.

Well, that was unexpected. Thanks for explaining, can confirm it work fine with the samples from https://github.com/SaschaWillems/Vulkan !
Comment 4 Kristian Høgsberg 2018-01-22 16:58:44 UTC 
Can you really claim it's "known broken" when nobody told the maintainer?

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.