Subject: Re: First impression on 14.10

From: Joseph Rushton Wakeling <[email-masked]>
Date: Fri, 03 Oct 2014 23:17:53 +0200

Cemil Azizoglu wrote:
> Thanks a lot for trying. I wasn't aware of the Xorg issue you've
> experienced.

It sounds a lot like the issue I encountered with XMir on 14.04: things would 
run nice and smooth, but after a while Xorg would get into this state with 100% 
CPU.  Not immediately, but invariably after a while.

I thought I'd reported it, but now that I look I can't find how or where. :-(  I 
suppose I could have a go at reinstalling the in-archive XMir now and see how it 
goes.

System is a ThinkPad T420 with Intel graphics.

---

From: Daniel van Vugt <[email-masked]>
Date: Mon, 06 Oct 2014 09:36:06 +0800

Joseph,

We would like to get to the bottom of your high CPU problem and fix it. 
Can you by any chance force a core dump of the spinning process when 
it's happening?... Like with:
    kill -ABRT <process ID>

If that fails to generate a problem report, then please log it here:
https://bugs.launchpad.net/xmir/+filebug

- Daniel

On 04/10/14 05:17, Joseph Rushton Wakeling wrote:
> It sounds a lot like the issue I encountered with XMir on 14.04: things
> would run nice and smooth, but after a while Xorg would get into this
> state with 100% CPU.  Not immediately, but invariably after a while.
>
> I thought I'd reported it, but now that I look I can't find how or
> where. :-(  I suppose I could have a go at reinstalling the in-archive
> XMir now and see how it goes.
>

---

From: Joseph Rushton Wakeling <[email-masked]>
Date: Tue, 07 Oct 2014 22:14:56 +0200

On 06/10/14 03:36, Daniel van Vugt wrote:
> Joseph,
>
> We would like to get to the bottom of your high CPU problem and fix it. Can you
> by any chance force a core dump of the spinning process when it's happening?...
> Like with:
>     kill -ABRT <process ID>
>

You mean kill Xorg?  I'll give it a go, but I'm not 100% sure I feel comfortable 
about doing that ... :-)

---

From: Joseph Rushton Wakeling <[email-masked]>
Date: Wed, 08 Oct 2014 00:56:42 +0200

On 06/10/14 03:36, Daniel van Vugt wrote:> Joseph,
> https://bugs.launchpad.net/xmir/+filebug

OK, I've reinstalled ubuntu-desktop-mir on my 14.04 system.  No sign of any 100% 
CPU issues so far, so I may have misremembered and the problem Cemil observed on 
14.10 may be new.

What _does_ happen on 14.04, which I recall as the principal reason I 
uninstalled ubuntu-desktop-mir, is that the system seems quite unresponsive to 
key strokes -- not cripplingly so, but certainly very irritatingly so.

---

From: Daniel van Vugt <[email-masked]>
Date: Wed, 08 Oct 2014 09:47:57 +0800

Joseph,

There is another way to gather information from a spinning process less 
destructively. Attach gdb to it (from a remote login, 2nd machine 
required) and get a backtrace ("bt") that way. I have a script I can 
provide you to do that if you open a bug.

As for the keystrokes, I think there's already a bug for that:
   https://bugs.launchpad.net/xmir/+bug/1295851

Also, I just noticed you say "14.04". Mir on 14.04 is effectively 
unsupported and now very out of date. As it's under heavy development we 
can only fix Mir issues on the development release (14.10).

- Daniel

On 08/10/14 06:56, Joseph Rushton Wakeling wrote:
> OK, I've reinstalled ubuntu-desktop-mir on my 14.04 system.  No sign of
> any 100% CPU issues so far, so I may have misremembered and the problem
> Cemil observed on 14.10 may be new.
>
> uninstalled ubuntu-desktop-mir, is that the system seems quite
> unresponsive to key strokes -- not cripplingly so, but certainly very
> irritatingly so.

---

From: Joseph Rushton Wakeling <[email-masked]>
Date: Wed, 08 Oct 2014 22:12:32 +0200

> can only fix Mir issues on the development release (14.10).

Yes, I know, which was why I was a bit surprised when you asked me to test 
things out.  I think it's Sam Segers who you want to get in touch with re the 
CPU issue.

I'm still mulling over whether to upgrade to 14.10 (I quite like my very solid 
14.04 system...), but if I do it'll probably be in advance of release and so in 
time to verify if https://bugs.launchpad.net/xmir/+bug/1295851 is still present 
there.

---

From: Daniel van Vugt <[email-masked]>
Date: Thu, 09 Oct 2014 09:42:41 +0800

Absolutely, if you want stability then stick to 14.04.

However Mir being under development can't afford to have maintenance 
branches actually being maintained in every Ubuntu release (yet). So Mir 
is primarily developed on the bleeding edge.

Note this does mean even if we did fix all of the problems you're 
experiencing, any fixes for Mir will probably never be backported to 14.04.

On 09/10/14 04:12, Joseph Rushton Wakeling wrote:
> Yes, I know, which was why I was a bit surprised when you asked me to
> test things out.  I think it's Sam Segers who you want to get in touch
> with re the CPU issue.
>
> I'm still mulling over whether to upgrade to 14.10 (I quite like my very
> solid 14.04 system...), but if I do it'll probably be in advance of
> release and so in time to verify if
> https://bugs.launchpad.net/xmir/+bug/1295851 is still present there.

---

From: Sam Segers <[email-masked]>
Date: Sat, 11 Oct 2014 00:56:53 +0200

I was going to investigate the high CPU usage. But after package updates,
my PC no longer boots on the radeon driver. X crashes after login. Mir also
doesn't boot. I tried a clean install of current 14.10, but that also
doesn't boot. With fglrx I have no issues.
My syslog has a lot of these lines:

    [   51.495859] traps: compiz[2730] trap invalid opcode ip:7f186f59c6e5
sp:7fff8e230020 error:0

Any idea?

2014-10-09 3:42 GMT+02:00 Daniel van Vugt <[email-masked]>:

> branches actually being maintained in every Ubuntu release (yet). So Mir is
> primarily developed on the bleeding edge.
>
> --
> Mir-devel mailing list
> [email-masked]
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/mir-devel
>

---

From: Daniel van Vugt <[email-masked]>
Date: Mon, 13 Oct 2014 10:22:48 +0800

Sorry to hear. That's a Compiz (or probably Unity 7 Shell) crash, so 
please log an automatic crash report if given the option.

Being separate processes there is almost certainly no way Mir or XMir 
can make Compiz/Unity crash. It's just a coincidence.

- Daniel

On 11/10/14 06:56, Sam Segers wrote:
> I was going to investigate the high CPU usage. But after package
> updates, my PC no longer boots on the radeon driver. X crashes after
> login. Mir also doesn't boot. I tried a clean install of current 14.10,
> but that also doesn't boot. With fglrx I have no issues.
>      [   51.495859] traps: compiz[2730] trap invalid opcode
> ip:7f186f59c6e5 sp:7fff8e230020 error:0
>
> Any idea?
>
> 2014-10-09 3:42 GMT+02:00 Daniel van Vugt <[email-masked]
> <mailto:[email-masked]>>:
>
>     branches actually being maintained in every Ubuntu release (yet). So
>     Mir is primarily developed on the bleeding edge.
>
>         https://bugs.launchpad.net/__xmir/+bug/1295851
>         <https://bugs.launchpad.net/xmir/+bug/1295851> is still present
>         there.
>
>
>     --
>     Mir-devel mailing list
>     [email-masked] <mailto:[email-masked]>
>     Modify settings or unsubscribe at:
>     https://lists.ubuntu.com/__mailman/listinfo/mir-devel
>     <https://lists.ubuntu.com/mailman/listinfo/mir-devel>
>
>
>
>