[Bug 1271628] Re: Xorg crashed with SIGSEGV in memset()

2014-02-05 Thread Chris Wilson
This bug was fixed in the package xserver-xorg-video-intel -
2:2.99.909-0ubuntu2

---
xserver-xorg-video-intel (2:2.99.909-0ubuntu2) trusty; urgency=medium

  * Refresh xmir patch.
 -- Maarten Lankhorst maarten.lankho...@ubuntu.com   Wed, 05 Feb 2014 
14:33:04 +

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1271628

Title:
  Xorg crashed with SIGSEGV in memset()

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1271628/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1271628] Re: Xorg crashed with SIGSEGV in memset()

2014-02-01 Thread Chris Wilson
** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: Confirmed = Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1271628

Title:
  Xorg crashed with SIGSEGV in memset()

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1271628/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1271628] Re: Xorg crashed with SIGSEGV in memset()

2014-01-29 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1271628

Title:
  Xorg crashed with SIGSEGV in memset()

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1271628/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1271628] Re: Xorg crashed with SIGSEGV in memset()

2014-01-22 Thread Anders Kaseorg
** Information type changed from Private to Public

** Package changed: xorg-server (Ubuntu) = xserver-xorg-video-intel
(Ubuntu)

** Project changed: xorg-server = xserver-xorg-video-intel

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1271628

Title:
  Xorg crashed with SIGSEGV in memset()

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1271628/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1271628] Re: Xorg crashed with SIGSEGV in memset()

2014-01-22 Thread Bug Watch Updater
Launchpad has imported 30 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=73351.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2014-01-07T10:36:55+00:00 Mike Auty wrote:

Created attachment 91591
Xorg.0.log for the crashed session

I'm running into the following segfault every morning, after I've left
my machine unattended at night.  The monitor is switched off (which also
powers the graphics tablet), and when I return the next morning I'm met
with the segfault, which I've attached gdb to and recorded a bt full
of the crash.  The timings on this log will be wrong, because gdb
trapped the segfault and didn't start again until this morning, but I
can get the right timings tonight, if that would be useful?

This happened with 2.99.906 as well as 2.99.907, however I believe it
did not fail with 2.99.905.  I should also note that I had been using
2.99.906 since late November, but only started to experience problems
after I upgraded to gnome-3.10.2 over the Christmas period.

I'm attaching my Xorg.0.log.old (from after the crash and X restarted),
and the gdb bt full output.  Please let me know if there's any further
patches or tests I can conduct, but understand I can only reliably
reproduce this overnight.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/1271628/comments/0


On 2014-01-07T10:37:29+00:00 Mike Auty wrote:

Created attachment 91592
GDB bt full results for the segfault

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/1271628/comments/1


On 2014-01-07T10:56:15+00:00 Chris Wilson wrote:

Do you see the same issue with xorg-1.14?

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/1271628/comments/2


On 2014-01-07T11:09:50+00:00 Chris Wilson wrote:

Also can you please run with ./configure --enable-debug?

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/1271628/comments/3


On 2014-01-08T02:33:56+00:00 Mike Auty wrote:

Created attachment 91634
Xorg.0.log for 1.14.5 crashed session

Yes, this still happens with 1.14.5, here's the new Xorg.0.log with
--enable-debug used to compile the 2.99.907 drivers.  Very similar gdb
bt full to follow...

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/1271628/comments/4


On 2014-01-08T02:34:40+00:00 Mike Auty wrote:

Created attachment 91635
GDB bt full results for the 1.14.5 segfault

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/1271628/comments/5


On 2014-01-08T09:23:27+00:00 Chris Wilson wrote:

If it manages to get that far with assertions disabled, it is an
extremely subtle bug. :|

Can I ask if you can p *priv, p *priv-cpu_bo, p *priv-gpu_bo in frame
#2 (_sna_pixmap_move_to_cpu) ?

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/1271628/comments/6


On 2014-01-08T09:23:45+00:00 Chris Wilson wrote:

*assertions enabled.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/1271628/comments/7


On 2014-01-08T09:25:07+00:00 Mike Auty wrote:

I'm a bit of a beginner when it comes to gdb, could you let me know how
I should do that please?

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/1271628/comments/8


On 2014-01-08T09:29:46+00:00 Chris Wilson wrote:

From within gdb, after the break due to the segfault, either type frame
2 or up twice. Then type p *priv, p *priv-cpu_bo, p
*priv-gpu_bo. And hope gcc hasn't optimised away priv. If it complains
that priv is not available, try p *sna_pixmap(pixmap), p
*sna_pixmap(pixmap)-cpu_bo, p *sna_pixmap(pixmap)-gpu_bo. (And
cross your fingers.)

A last resort would be --enable-debug=full and hoping the error still
occurs. The Xorg.0.log will be massive (may even be greater than 2GiB)
but only the last 1000 lines will be enough to check to see if the bug
exposes itself.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/1271628/comments/9