Bug 450247
| Summary: | Xorg fails to start with 4GB or greater | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Andy Burns <fedora> | ||||||||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | low | Docs Contact: | |||||||||||||
| Priority: | low | ||||||||||||||
| Version: | 9 | CC: | adam, airlied, bestis+rh, patrick, redhat-bugzilla, xgl-maint | ||||||||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | x86_64 | ||||||||||||||
| OS: | Linux | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Fixed In Version: | kernel-2.6.26.3-29.fc9.x86_64 | Doc Type: | Bug Fix | ||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2009-07-14 18:05:13 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: | |||||||||||||||
| Attachments: |
|
||||||||||||||
|
Description
Andy Burns
2008-06-06 07:43:37 UTC
Created attachment 308513 [details]
Xorg.log showing failure
Created attachment 308514 [details]
Xorg.log showing succesful start
Created attachment 308515 [details]
dmesg from machine
Comment on attachment 308515 [details]
dmesg from machine
changed mime type to text/plain
i can confirm this problem with a radeon hd 2400 pro (rv610) card i also opened a bug https://bugzilla.redhat.com/show_bug.cgi?id=450432 should we close one? but i have got the 32bit version of fedora installed Although they both seem related to 4GB memory, on my machine with the intel driver it crashes xorg, yours with the radeon driver reboots the machine (kernel panic?) I'd rather see some comment from an ajax and/or arlied before closing either of them. I found out something more about this problem. could this be an mtrr problem? i have attached a dmesg file and my gdm log in both there are mtrr problems like: error setting MTRR (base = 0xf0000000, size = 0x08000000, type = 1) Invalid argument (22) Created attachment 309037 [details]
gdm log file
Created attachment 309038 [details]
dmesg log file
i found a solution for my problem. i dont know if this is a nice idea... i disabled the memory remap feature in my motherboard bios. ofter that my ati radeon 2400 pro works I have this problem on a Dell Optiplex 745. Didn't realize it was a 4GB problem. I'm reasonably sure I'm seeing this bug, rather than bug #450247. Commonalities: - machine locks hard on spawning of second X server (first is fine), e.g. GDM after RHGB; if I turn RHGB off it crashes if log out - which restarts X - 4GB RAM Similarities: - Radeon HD 2400 XT - Dell Optiplex 755 I also see: error setting MTRR (base = 0xd0000000, size = 0x10000000, type = 1) Invalid argument (22) in my GDM log, and: Aug 29 13:58:17 keyop kernel: mtrr: type mismatch for d0000000,10000000 old: write-back new: write-combining in /var/log/messages. I've updated to the latest available BIOS. I can't find a memory remap feature in the BIOS. It'll be tricky to test removing a stick of RAM (but possible if needed) - I'll have to get alarms disabled etc. I'm running a vaguely usable machine by disabling RHGB - as long as I don't log out! Ha. I meant, of course, that I see more in common with this bug than bug #450432. My Bug report in #455127 seems to have the same problem. I also have the same motherboard and 4G of ram as the original reported. This has been resolved for me since I applied the latest F9 updates. I can't see an xorg package amongst them, so I think it must be the kernel update that fixed it (to kernel-2.6.26.3-29.fc9.x86_64). Booting back into kernel-2.6.25.14-108.fc9.x86_64 causes the crash again. I am having this problem again with kernel-2.6.26.5-45.fc9.x86_64. I can run X exactly once between reboots. Optiplex 745. As a workaround, try limiting memory to 4GB with the kernel option 'mem=4096M' in grub.conf. Looks like a lockup in drm. In case it helps narrow the problem down: just to note that I'm *not* experiencing the problem again having rebooted into kernel-2.6.26.5-45.fc9.x86_64. An Optiplex 755 with Radeon HD 2400 XT and 4GB RAM. I'm not using any kernel mem= options. This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. 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 '9'. 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 9'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 9 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 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 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. |