Bug 1900639
| Summary: | i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:85ddfffd | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Brian J. Murrell <brian> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 32 | CC: | acaringi, adscvr, airlied, bskeggs, hdegoede, itamar, jarodwilson, jeremy, jforbes, jglisse, jonathan, josef, kernel-maint, lgoncalv, linville, masami256, mchehab, mjg59, ptalbert, steved |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-05-25 17:13:52 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Brian J. Murrell
2020-11-23 13:14:55 UTC
Looks like I duplicated my own bug #1886438. Probably due to forgetting that I had opened one since there was absolutely no response to it whatsoever (in addition to the lack of response to this one). In any case, can we please get some kind of response anyone? FWIW, I tried to add needinfo for kernel-maint but BZ told me that account is disabled[1], hence the wide needinfo request. This needs to get fixed and the total lack of response from two tickets opened about it, both including upstream reports and one including a patch is just distressing. [1] It's also kind of distressing that tickets are assigned to a disabled account to which needinfo cannot be requested. Sorry, as there is only me managing fedora bugs, I don't typically respond to everything submitted, but I do see them and follow them. I have been following this for a while, but upstream seems to be ignoring that patch for some reason. It has not been included in a pull request to linus and doesn't even seem to be in drm-next yet. As soon as it is, I can pull it in. > but upstream seems to be ignoring that patch for some reason
Can you define who upstream is this case and I will see if I can chase them?
I would ping the author, Chris Wilson, he should be able to get it through. Likely he just hasn't noticed it is not moving as he is working on other bugs. Upstream issue has been closed with a patch being submitted: https://gitlab.freedesktop.org/drm/intel/-/issues/2024#note_755162 Can this patch be integrated into Fedora ASAP now? This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. This should have been fixed with 5.10.9 kernels. Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |