Summary: | XServer segfaults when EXANoUploadToScreen is set. | ||||||
---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Rafael Monica <monraaf> | ||||
Component: | Driver/Radeon | Assignee: | xf86-video-ati maintainers <xorg-driver-ati> | ||||
Status: | RESOLVED WONTFIX | QA Contact: | Xorg Project Team <xorg-team> | ||||
Severity: | normal | ||||||
Priority: | medium | CC: | shlomif | ||||
Version: | git | ||||||
Hardware: | Other | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Attachments: |
|
Description
Rafael Monica
2010-10-06 03:19:42 UTC
I'm inclined to resolve this as WONTFIX. This is a useful optimization, and the driver has required the UploadToScreen hook on big endian machines for as long as KMS has worked there. Why are you trying to use Option "EXANoUploadToScreen"? I agree it's a useful optimization and WONTFIX is fine with me, although I think it would be cleaner to disable EXANoUploadToScreen option, or at least mention it in exa(4) that this option causes segfault with radeon driver. I was trying this option because of bug 30188, which gives me EVERGREENUploadToScreen in the backtrace, and was hoping EXANoUploadToScreen option would fix it, unfortunately it doesn't. (In reply to comment #2) > I agree it's a useful optimization and WONTFIX is fine with me, although I > think it would be cleaner to disable EXANoUploadToScreen option, Not possible, it's an option of the "exa" module, which doesn't know that the driver really needs the UploadToScreen hook. > or at least mention it in exa(4) that this option causes segfault with radeon > driver. If anything it should rather be documented with the driver. > I was trying this option because of bug 30188, which gives me > EVERGREENUploadToScreen in the backtrace, and was hoping EXANoUploadToScreen > option would fix it, unfortunately it doesn't. Trying to work around that problem really requires the UploadTo/DownloadFromScreen hooks. The issue is that there is still sometimes direct CPU access to VRAM. |
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.