*** This bug is a duplicate of bug 1497593 ***
https://bugs.launchpad.net/bugs/1497593
** This bug has been marked a duplicate of bug 1497593
[nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion
`kref' failed.
--
You received this bug notification because you are a
** Changed in: mesa
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1553328
Title:
Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref()
especially
This should probably be tracked in bug 1497593 now.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1553328
Title:
Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref()
especially
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #1087
https://gitlab.freedesktop.org/mesa/mesa/-/issues/1087
** Also affects: mesa via
https://gitlab.freedesktop.org/mesa/mesa/-/issues/1087
Importance: Unknown
Status: Unknown
--
You received this bug notification
** Changed in: nouveau
Status: In Progress => Unknown
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1553328
Title:
Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref()
Launchpad has imported 42 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=92438.
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
** Changed in: mesa (Ubuntu)
Status: Invalid => Triaged
** Changed in: mesa (Ubuntu)
Importance: Critical => High
** Changed in: libdrm (Ubuntu)
Importance: Critical => High
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in
Actually, the snapshotting/screencasting thread could also trigger it.
If that's still a thing...?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1553328
Title:
Mir/Unity8/USC crashes/freezes
I don't think the problem description is clear that both the Mir and
Unity8 compositors are affected. (It can be read as applying to the
stack including Unity8.) Thanks for clarifying.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in
Well, yes. The problem description before that covers the fact that
Mir's multi-threaded compositor manifests the problem (assuming you have
multiple monitors). And comment #20 states that avoiding multiple
threads (a single headed or cloned config) avoids the instability.
--
You received this
Daniel, you are saying comment #20 states that Mir's thread-per-monitor
rendering manifests the problem? (I don't have any nouveau based kit to
test on.)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
Alan, that question was already answered in comment #20. Single threaded
rendering works.
** Changed in: mir
Status: Incomplete => Triaged
** Changed in: mir
Importance: Undecided => High
** Changed in: mir (Ubuntu)
Status: Incomplete => Triaged
** Changed in: mir (Ubuntu)
The nouveau isn't threadsafe and the Qt renderer uses threaded GL by
default.
We don't know if Mir's default renderer would also exhibit the same
issue when running multimonitor. (The Mir renderer uses a thread per
monitor, but this is a simpler usage pattern than Qt and may not
manifest
** Branch linked: lp:~gerboland/qtmir/nouveau-workaround
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1553328
Title:
Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref()
I've an ancient NVidia box at home, can try it out. I'm attaching
patches for qtubuntu/qtmir to force Qt to use single threaded GL on
nouveau.
** Branch linked: lp:~gerboland/qtubuntu/nouveau-workaround
--
You received this bug notification because you are a member of Ubuntu-X,
which is
I made an attempt at a workaround for nouveau crashes today (and
discovered more nouveau bugs).
I can confirm with mir-demos that forcing the compositor into single-
threaded mode makes it stable. The only problem is the unity-system-
compositor option for doing this gets ignored (Unity8
** Changed in: canonical-devices-system-image
Milestone: u8c-1 => u8c-2
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1553328
Title:
Mir/Unity8/USC crashes/freezes on nouveau (nv50) in
** Changed in: canonical-devices-system-image
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1553328
Title:
Mir/Unity8/USC crashes/freezes on nouveau (nv50)
Even easier workaround for Mir/USC: Just default to clone mode instead
of side-by-side, which is the problem in today's duplicate bug 1672793.
Mir's legacy clone mode will at least ensure there is only one
compositor thread, so nouveau should be stable then.
** Also affects:
Per comment #17 it might actually be easiest to build a workaround in
Mir for now... Either disable secondary compositor threads, or build a
SingleThreadedCompositor to replace MultiThreadedCompositor.
In my spare time I'm working on an idea where post() could be made non-
blocking. So that would
** Summary changed:
- Mir/Unity8 crashes/freezes on nouveau (nv50) in pushbuf_kref() especially
with multiple monitors, webbrowser-app or system settings
+ Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially
with multiple monitors, webbrowser-app or system settings
**
21 matches
Mail list logo
