| Summary: | Xorg crashes with signal 11 after a while | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Dennis Jacobfeuerborn <d.jacobfeuerborn> | ||||||
| Component: | * Other | Assignee: | Adam Jackson <ajax> | ||||||
| Status: | RESOLVED DUPLICATE | QA Contact: | |||||||
| Severity: | blocker | ||||||||
| Priority: | high | CC: | erik.andren | ||||||
| Version: | 6.99.99.902 (7.0 RC2) | Keywords: | have-backtrace | ||||||
| Hardware: | x86 (IA32) | ||||||||
| OS: | Linux (All) | ||||||||
| Whiteboard: | |||||||||
| i915 platform: | i915 features: | ||||||||
| Bug Depends on: | |||||||||
| Bug Blocks: | 5041 | ||||||||
| Attachments: |
|
||||||||
|
Description
Dennis Jacobfeuerborn
2006-04-23 12:39:25 UTC
Please post your xorg conf and your xorg.log Also please try to get a remote backtrace. Created attachment 5430 [details]
xorg.conf and Xorg.0.log
This happened a couple of time now for me in the last couple of days and always
with the same trace. What exactly is a remote backtrace and how do I obtain it?
I just tried running Xorg using gdb which worked but when X crashed it caught the SIGSEGV, printed the backtrace and in gdb I only got the backtrace of a followup SIGPIPE. Is there away to tell Xorg to let gdb catch the signal 11 instead? There is some documentation on running the X server under gdb on the wiki: http://xorg.freedesktop.org/wiki/DebuggingTheXserver Created attachment 5516 [details]
gdb backtrace
After a few days the crash happened again and this time I had a remote gdb
attached. See attachment.
Two observations: 1. XAAComposite() gets called with xSrc=51, ySrc=270 which then calls fbComposite() with xSrc=109, ySrc=4578 which looks odd to me because I see no instructions modifying these variables between those calls. 2. The call to fbComposite() happens right after the patch for bug #4320. (called xorg-x11-server-1.0.1-composite-fastpath-fdo4320.patch in the Fedora Core Rawhide SRPM). Could this patch be responsible for the breakage? (In reply to comment #6) > Two observations: > 1. XAAComposite() gets called with xSrc=51, ySrc=270 which then calls > fbComposite() with xSrc=109, ySrc=4578 which looks odd to me because I see no > instructions modifying these variables between those calls. > > 2. The call to fbComposite() happens right after the patch for bug #4320. > (called xorg-x11-server-1.0.1-composite-fastpath-fdo4320.patch in the Fedora > Core Rawhide SRPM). > > Could this patch be responsible for the breakage? Could be. Should also be unnecessary now in rawhide. The RC2 server build is going through now, give it a try tomorrow. I'd also be interested to know if this is a problem with Composite disabled. This is still a problem with the package xorg-x11-server-Xorg-1.0.99.902-1. I've disabled Composite now to see if that makes any difference. Unfortunately I'm still getting hit by this even with Composite disabled. (In reply to comment #9) > Unfortunately I'm still getting hit by this even with Composite disabled. There's a good shot this is bug #6827. I've built some rawhide RPMs with that patch included at: http://people.freedesktop.org/~ajax/rawhide/ Could you test these? Thanks, I've installed the RPMs an will check if Xorg runs more stable. I can already report that this fixes the following Firefox bug I reported here: https://bugzilla.mozilla.org/show_bug.cgi?id=334951 (Resized image displayed as black rectangle) (In reply to comment #11) > I can already report that this fixes the following Firefox bug I reported here: > https://bugzilla.mozilla.org/show_bug.cgi?id=334951 (Resized image displayed as > black rectangle) That's probably justification enough to include this in the release. If I don't hear of any crashes from you before this Friday I'll land this for RC3. pretty clear that this is a dupe by now. *** This bug has been marked as a duplicate of 6827 *** |
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.