Bug 28177 - Xserver segfaults from bad commit 7c9733d063acee04735a0e75d62e508fe4ea1163 "xfree86: use screen privates for Xv offscreen images."
Summary: Xserver segfaults from bad commit 7c9733d063acee04735a0e75d62e508fe4ea1163 "x...
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium minor
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-19 11:47 UTC by blaise
Modified: 2010-05-19 15:20 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments

Description blaise 2010-05-19 11:47:55 UTC 
Running a bisect the first bad commit that comes up is:

"xfree86: use screen privates for Xv offscreen images."

commit 7c9733d063acee04735a0e75d62e508fe4ea1163.

After reverting the commit,rebuilding and installing it runs normally without any problems.
Since I only use only one machine it's hard to do a debug to see what is really happening but I thought should let others know about it in case they experience the same thing.

nVidia GT 220 kernel module version 195.36.07.04
Xorg git master (xserver HEAD 673eb707ce6737284c4886265ba149c5587a74e2)
Ubuntu 10.04
Comment 1 Julien Cristau 2010-05-19 12:30:20 UTC 
Do you have a log?  I would have thought the nvidia driver wasn't compatible with the various ABI changes in git at this point.
Comment 2 blaise 2010-05-19 15:20:43 UTC 
  You can mark this ticket as Incompleted/Closed since I have to bone up on my git bisecting skills. The relevant commit isn't the problem since it seems good now that I'm retesting. 

  The last good xserver commit without a segfault I can use is 81a081c1f0cb55df94cb10495aa7ad71cd5a9afb 2010-04-28 Cygwin/X: AIGLX using native WGL. The 4 merges after that seems to where things go awry. I'll resubmit a ticket once I've really tracked down the problem area. Sorry for the trouble.

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.