Bug 1254148
Summary: | [TTM] Failed to find memory space for buffer [hex-address] eviction | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | matti aarnio <matti.aarnio> |
Component: | xorg-x11-drv-nouveau | Assignee: | Adam Jackson <ajax> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 22 | CC: | airlied, ajax, bskeggs, masao-takahashi |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-07-19 18:55:14 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
matti aarnio
2015-08-17 09:47:23 UTC
This appeared after update from Fedora 21 to Fedora 22. This happens repeatedly after 2 to 1 hours of browser + eclipse usage. There seem to be a tendency to happen after shorter time when not rebooting the machine. I have not recorded restart times to know for sure. The kernel TTM diagnostics apparently happened about 210 seconds before X server crashed, and thus may or may not be related. Also the pixman may not be the culprit, and Xorg base instead is. Using kernel 4.1.3-100.fc21.x86_64 the stability problem disappears while rest of the system is FC22. Therefore the issue is probably in later nouveau kernel driver (or kernel TTM,) and not in the pixman. Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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. |