Summary: | commit 61e47d92c5196 breaks RS780 | ||
---|---|---|---|
Product: | Mesa | Reporter: | octoploid <octoploid> |
Component: | Drivers/Gallium/r600 | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED FIXED | QA Contact: | Default DRI bug account <dri-devel> |
Severity: | normal | ||
Priority: | medium | CC: | Hi-Angel, octoploid |
Version: | git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
octoploid
2017-04-12 12:33:25 UTC
octoploid don't think we have many people working on r600, so if you can track down the commit that caused the regression that will be appreciated. git bisect should be done in ~7 steps. (In reply to Emil Velikov from comment #1) > octoploid don't think we have many people working on r600, so if you can > track down the commit that caused the regression that will be appreciated. > > git bisect should be done in ~7 steps. No sorry, but this would be too annoying (these GPU lockup sometimes hang the whole machine). So I would have to reboot all the time. So take it as an FYI. Well, I figured out a way to bisect without rebooting. The issue started with: 61e47d92c5196bf0240e322bb1b9d305836559e3 is the first bad commit commit 61e47d92c5196bf0240e322bb1b9d305836559e3 Author: Constantine Kharlamov <Hi-Angel@yandex.ru> Date: Mon Apr 10 23:04:37 2017 +0300 r600g: get rid of dummy pixel shader I reverted the bad commit. Thanks for bisecting. |
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.