| Summary: | Savage Xv doesn't work after suspend-to-ram | ||
|---|---|---|---|
| Product: | xorg | Reporter: | Scott Bronson <bronson> |
| Component: | Driver/savage | Assignee: | Xorg Project Team <xorg-team> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | high | CC: | erik.andren, freedesktop.org |
| Version: | unspecified | ||
| Hardware: | x86 (IA32) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Scott Bronson
2004-12-06 10:20:14 UTC
Sorry, I should mention that I'm using 6.8.1-1ubuntu4 from Hoary. try xorg from cvs. For what it's worth, I'm seeing the same thing on a T22 running Fedora Core 4 with all the latest updates (xorg-x11-6.8.2-37.FC4.49.2). I see the same symptoms after suspend-to-ram, and after suspend-to-disk using the swsusp2 patches. In both cases, it's necessary to to restart the X server to get Xv working. Forgot to mention that I'm also seeing the same thing on a Toshiba Tecra 8100 which uses the Savage chip set. It's also running the lates updates to Fedora Core 4 and xorg-x11-6.8.2-37.FC4.49.2 It turns out (on my system anyway) that it's not even necessary to suspend. Simply switching to the text console (Ctl-Alt-F1) and back to X is enough to stop Xv from working. (Perhaps that information will make debugging easier) Is there any way to "reset" Xv without having to kill and restart the X server?? I'm running Fedora Core 4 on an IBM ThinkPad T23 (SuperSavage IX/C SDR (rev
05)), and see the same issue.
> try xorg from cvs.
Building RPMs without all the Fedora patches would be fairly time consuming (it
looks like some of the patches are required for GCC 4.0).
So this weekend I tried building the latest Fedora Core 4 x.org source
(xorg-x11-6.8.2-37.FC4.49.2) with drivers/savage reverted to 6.7.0 (which did
not have this issue). This hybrid does not have the bug, so it does look like
it crept into the mainline Savage driver after 6.7.0.
I would be happy to try out any changes that might fix this issue, or help to
narrow down the cause.
Otherwise, I'll try a binary search of the changes after 6.7.0 to find exactly
when this was introduced. But I'm not sure how long that process will take.
Thanks for the suggestion. I was hoping I could get away without having to rebuild from the ground up, so I tried simply replacing /usr/X11R6/lib/Server/modules/drivers/savage_drv.o on FC4 with the corresponding file from the FC2 distribution (which is built from 6.7.0). It works! (Well, I'm probably missing some 6.8 functionality or bug fixes, but this specific issue appears to be fixed, so this seems like a good workaround for now) Any improvements using a more current version of xorg? Ping to the bug submitter! I had to give that T-23 back to my ex-employer so I don't have the hardware anymore. Maybe David Wragg or Peter Fales could say? Thanks for the ping! Marking broken (status null/blank) bugs in xorg with no activity in a long time as fixed. Please reopen if you think it's necessary, but first do a search if a similar bug report is already filed and in a NEW/ASSIGNED state. These bugs do not currently show in most search results as they do not have any status. Sorry for this janitorial spam, you know where to send hate mails to when your inbox gets full of bugs you're subscribed to. |
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.