Maarten: Filled in test case stuff (what did you mean about eth2?)
I wonder if this should be marked security; we know it's
scribbling over bits of the X server, that's running as root,
although I don't know how to control what is scribbled where
(I'll get
Precise won't get Unity 3D up (even with some forcing); so I'll say not
repeatable.
[If as per previous question it's a security issue though that may need some
more looking at]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can you reproduce this on precise too? Might be worth it to have it
there as well..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1043513
Title:
Xorg crashed with SIGABRT in memcpy() via
** Description changed:
- No login possible on KVM-based virtual machine (with virt-manager) and
- network settings
+ [Impact]
+ * Fixes a null pointer dereference when shadowfb is out of bounds, in a
similar way to other ddx drivers.
+
+ [Test Case]
+ * Start virt-manager, create
Anyway if you can fill out the testcase part, I should be able to get it
sru'd for quantal, and if that works maybe precise as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1043513
Title:
Thanks Maarten; that does seem to have nailed it in Raring; SRU for
Quantal?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1043513
Title:
Xorg crashed with SIGABRT in memcpy() via cirRefreshArea()
should be fixed in xf86-video-cirrus 1.5.2 then. I just pushed this
upstream, and will do a release to raring shortly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1043513
Title:
Xorg crashed with
** Branch linked: lp:ubuntu/raring-proposed/xserver-xorg-video-cirrus
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1043513
Title:
Xorg crashed with SIGABRT in memcpy() via cirRefreshArea() under
This bug was fixed in the package xserver-xorg-video-cirrus -
1:1.5.2-0ubuntu1
---
xserver-xorg-video-cirrus (1:1.5.2-0ubuntu1) raring; urgency=low
* Sync from unreleased debian git.
- Upstream release fixes cirRefreshArea SEGV (LP: #1043513)
* Drop fix-fallback.diff,
Thanks Maarten, that looks good; I guess with cirrus module loaded it's
probably not actually that important on a raring release; but it's good
to fix anyway, and I'd say backport to Quantal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
ok I added a if (width = 0 || height = 0) continue; to cope with this,
similar to other drivers. Can you retest?
** Attachment added: revised attempt
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-cirrus/+bug/1043513/+attachment/3472500/+files/patch
--
You received this bug
** Changed in: xserver-xorg-video-cirrus (Ubuntu)
Assignee: (unassigned) = Maarten Lankhorst (mlankhorst)
** Changed in: xserver-xorg-video-cirrus (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: xserver-xorg-video-cirrus (Ubuntu)
Status: Incomplete = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1043513
Title:
Xorg crashed with SIGABRT in memcpy() via
Maarten:
OK, it still crashes, and the reason is you're MIN/MAX aren't sufficient:
cirRefreshArea: pbox: (-958,52 / -236,486) clipped: (0,52 / -236,486)
pScrn-vX/Y 1024,768 rotate=0
you need to use both MIN and MAX on each coordinate to cope with the box
being completely off one side of the
** Changed in: xserver-xorg-video-cirrus (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1043513
Title:
Xorg crashed with SIGABRT in memcpy() via
** Changed in: xserver-xorg-video-cirrus (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1043513
Title:
Xorg crashed with SIGABRT in memcpy() via
You can disable the cirrus driver in raring by blacklisting it in
/etc/modprobe.d/blacklist.conf or temporarily removing it from
/lib/modules
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1043513
Hang on, scrap that analysis - I noticed the logs show it's not loading
the rebuilt cirrus module with that change; It's now showing an EABI
mismatch error. I'll get back to you.
Dave
** Changed in: xserver-xorg-video-cirrus (Ubuntu)
Status: Triaged = Incomplete
--
You received this
and to compound things, the kernel driver is now working on raring, so I
can't load this one to test it; let me get back to you next weekend.
Dave
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: lankhostversion.png
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-cirrus/+bug/1043513/+attachment/3460902/+files/lankhostversion.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: myversion.png
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-cirrus/+bug/1043513/+attachment/3460904/+files/myversion.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Maarten,
That patch isn't happy; but I'm not sure why yet; I've attached three screen
captures:
1) The version with the ubuntu built package - which shows the strange
crosshatching from bug 1080674
2) myversion.png - the version with my patch, looks the same as (1) but
doesn't
well since nobody was forthcoming I've taken a look. The reason those
specialized exist is because they're used for rotations.
I think your patch is slightly overdesigned, could you try if this patch
works for you?
I also fixed up the other rotated versions
** Attachment added: patch
** Tags added: raring
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1043513
Title:
Xorg crashed with SIGABRT in memcpy() via cirRefreshArea() under KVM
virtual machine
To manage notifications
Hi,
Attached is a patch that seems to fix this; however it needs looking at by
someone who understands the code; in particular I have some questions:
1) Does this also need to go in cirRefreshArea8/16/24/32 ?
2) Why is the generic one being called if there are those specialised ones
The attachment Clip the range in cirRefreshArea of this bug report has
been identified as being a patch. The ubuntu-reviewers team has been
subscribed to the bug report so that they can review the patch. In the
event that this is in fact not a patch you can resolve this situation by
removing the
Confirmed still happening in Raring (That's a raring guest with Quantal
host) as of today's install.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1043513
Title:
Xorg crashed with SIGABRT in
To simplify my instructions from comment #15:
1) Open a terminal (sits in top left)
2) Ctrl-alt-down arrow to move down one virtual deskop
It blows up at (2).
(pScrn-virtual X/y in cirRefreshArea is 1024/768)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Some random extra debug (from a separate run):
(gdb) up
#3 0x7f0485ef1af3 in ShadowCopyArea (pSrc=0x7f048ba948f0,
pDst=0x7f048c4ca910, pGC=0x7f048c3def70,
srcx=optimised out, srcy=optimised out, width=optimised out,
height=434, dstx=0, dsty=0)
at
Hi Bryce,
See backtrace attached; just generated, on an up to date Quantal:
ii xserver-xorg-video-cirrus 1:1.5.1-0ubuntu2
amd64X.Org X server -- Cirrus display driver
Looks the same one to me; it's a lot harder to hit this than it was a
few weeks ago - this survived an
actually, I seem to have found a reasonably repeatable sequence:
1) Login
2) open a gnome-terminal
3) Walk through the 4 workspaces with ctrl-alt-arrows, within 2 or 3 times of
doing that reasonably quickly it blows up.
--
You received this bug notification because you are a member of
Some more diags;
(gdb) p *pbox
$2 = {x1 = -958, y1 = -716, x2 = -236, y2 = -282}
I'm not sure what the space these values are working is supposed to be; if
they're supposed to be -ve then they're in a sensible
range as far as I can tell - but are they supposed to be -ve?
(gdb) p
Bug 1056511 has a proposed fix posted to it; if you suspect this might
be a dupe of that bug then it would be worthwhile to test that patch.
Bug 1053702 (and bug 1045845) is another recent cirrus crash that was
fixed about a month ago. If you've not reproduced the crash in October
it is
Timo: As mentioned in #10 It's worth checking that bug 1056511 as well
which is nouveau based, the backtrace looks similar enough to me to make
me wonder if it's not driver specific.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Package changed: xorg-server (Ubuntu) = xserver-xorg-video-cirrus
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1043513
Title:
Xorg crashed with SIGABRT in memcpy() via cirRefreshArea()
Things also became better with the Cirrus driver and VMs. After being able to
login I noticed that my KVM VM (which runs on a rather power efficient, iow not
too fast, machine) still has occasional crashes of this type. And there you can
see (and have to wait) every graphical goodness like
Looks like 1048304 is another dupe of this?
1056511 looks like a very similar backtrace to me as well, even though the
driver at the last stage is nouveau rather than cirrus, the rest of it looks
the same.
As of todays Quantal update it's stable enough to allow me to login and
get a few minutes
The X crash happens when using the cirrus X driver. For KVM there is a
new modeset driver in Quantal which should avoid this but there are
currently races which cause that not to load properly (see bug
#1038055). However the same problem hits Xen HVM guests and for those
(and likely all real hw
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (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/1043513
Title:
Booting freshly installed quantal beta1 amd64 desktop under kvm (20120903.4)
As soon as I login, it kicks me back out to the graphical login. This was seen
on the boot right after installation. If I manually reboot the system after
that (i.e. shutdown kvm, properly start it back up without the
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1043513
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
41 matches
Mail list logo
