| Summary: | [945gm] regular segfaults in XvPutImage path | ||||||
|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Daniel Stone <daniel> | ||||
| Component: | Driver/intel | Assignee: | Jesse Barnes <jbarnes> | ||||
| Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||
| Severity: | normal | ||||||
| Priority: | medium | CC: | ross | ||||
| Version: | git | ||||||
| Hardware: | Other | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| i915 platform: | i915 features: | ||||||
| Attachments: |
|
||||||
|
Description
Daniel Stone
2007-12-12 17:39:34 UTC
Created attachment 13075 [details]
log of crashed session -- 945gm, no dri
I hope this is a DUP of 13108, please try master... Nope, sorry, but it still crashes. Daniel, have you changed driver code or build instruction? why I can't see overlay register allocation in your log? Do you test with overlay xv or default texture video? My this 945gm laptop works ok with Xv on overlay and texture video. looks similar to #13756? Do you use fb? No, I don't use the framebuffer at all. I haven't made any modifications, obviously. Video works _most_ of the time, but sometimes it segfaults. It seems to be more regularly after S3 than anything (I do a lot of S3, which has a chvt in the path there), but I can't confidently say that's the cause. *** Bug 14661 has been marked as a duplicate of this bug. *** I wonder if this is the same as 14622. In that case, the segfaults actually occurs in the data copy routine... Yeah, for sure. All I know is that it happens somewhere _under_ PutImage (including the data copying itself, and most probably is). I can't gdb with a single machine, so I'm just at the mercy of glibc's backtrace(). I'm willing to bet they're the same though. Lukas just added a patch to #14622, care to give it a try? Patch has been pushed upstream. Pls test with master. I'm closing this one, feel free to reopen if issue still exists. Thanks. |
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.