Bug 472028
| Summary: | ati x1950pro, xorg crashes (oom) when using modesetting | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Hans de Goede <hdegoede> | ||||||||||
| Component: | xorg-x11-drv-ati | Assignee: | Dave Airlie <airlied> | ||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | medium | Docs Contact: | |||||||||||
| Priority: | medium | ||||||||||||
| Version: | 10 | CC: | airlied, awilliam, htl10, johannbg, mcepl, mjw, xgl-maint | ||||||||||
| Target Milestone: | --- | Keywords: | Reopened, Triaged | ||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | All | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2009-12-18 06:52:44 UTC | Type: | --- | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Bug Depends On: | |||||||||||||
| Bug Blocks: | 432388 | ||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Hans de Goede
2008-11-18 11:32:43 UTC
Wov! Could we get our classical trio (Xorg.0.log, xorg.conf if any, and dmesg), please? Created attachment 324038 [details]
xorg.log
Created attachment 324039 [details]
xorg.conf
Relevant part of dmesg is already reproduced in the original report above. grab -54 of -ati and let me know if this happens again. /me goes looking for memory leaks. (In reply to comment #5) > grab -54 of -ati and let me know if this happens again. > > /me goes looking for memory leaks. Ok, note I've only seen this once ever, but I'll report back here if it happens again. If not we can close this one. This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping There have been bunch of bug fixes Could you retest with the latest kernel ( -132 at the time of this writing ) You can get the latest kernel build here http://koji.fedoraproject.org/koji/buildinfo?buildID=72270 And with the latest xorg-x11-drv-ati. ( -60 at the time of this writing ) You can get the latest xorg-x11-drv-ati build here http://koji.fedoraproject.org/koji/packageinfo?packageID=95 And report back if it either improves or fixes this issue.. Thanks. Johan, (In reply to comment #8) > There have been bunch of bug fixes > > Could you retest with the latest kernel I appreciate the efforts of the bug triaging team, but I would appreciate it even more if you people would first actually read the entire bug report, which part of: (comment #6) > Ok, note I've only seen this once ever, but I'll report back here if it happens > again. If not we can close this one. Did you not understand ? Haha I've been that end as well... Teaches a tester to be doing crappy triaging work.. For future reference there is nothing preventing you from closing it your self if this is one of those bugs that happen just only when the moon is full and all the stars are correctly lined or do it if the problem has been fixed.... Just change the status from assigned to closed with the appropriate sub options of closed. Thank you. As discussed with the assignee just because this has not happened anymore does not mean this is fixed, so I'm re-opening this. The issue is that the kernel code tries to kmalloc 64k, which translates to needing 16 (or 8 on x86_64) consecutive physical pages in a row, on a system which has been running for a while and thus has fragmented memory this will not always succeed. The plan is to add a vmalloc fallback for now to work around this. As I'm going to see if we can use priority and severity usefully, I'm dropping it on this bug, as it's obviously not something that is practically causing major problems at the moment. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Still have those oom messages, although xorg does not crash (it just seems to be unresponsive for about a minute and comes back). kernel-2.6.30.6-53.fc11.x86_64 xorg-x11-drv-ati-6.12.2-18.fc11.x86_64 xorg-x11-server-Xorg-1.6.4-0.1.fc11.x86_64 I seem to be able to get this every couple of weeks, by running seamonkey (not firefox) and do the usual web browsing thing for a few days. logs to follow. Created attachment 361016 [details]
the latest dmesg
the latest dmesg showing one such instance.
Created attachment 361017 [details]
Xorg.0.log
my Xorg.0.log. I run without an xorg.conf .
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. 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 WONTFIX if it remains open with a Fedora 'version' of '10'. 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 prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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. Thank you for reporting this bug and we are sorry it could not be fixed. |