[Bug 1630711] Re: fwupd using 200% CPU, but status of systemd services is "inactive (dead)"

2016-10-06 Thread Mario Limonciello
OK thanks.

We have had "some" problems with fwupd and relevant dependencies caused
by corrupted archive metadata.  There have also been some instances of
bad USB devices or bad USB host controllers causing spinning.  When this
happened there was also an associated mess in the kernel log.

For now i'll close it out.  Open it back up if/when it happens again.
Ideally if you could just keep the debug symbols installed that will
make attaching to gdb for figuring out what it's spinning on when this
happens easier.

** Changed in: fwupd (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  fwupd using 200% CPU, but status of systemd services is  "inactive
  (dead)"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1630711/+subscriptions

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


[Bug 1630711] Re: fwupd using 200% CPU, but status of systemd services is "inactive (dead)"

2016-10-06 Thread Jason Gerard DeRose
So far I haven't encountered this again... so might have been a fluke
with the state of Yakkety for a brief period, phase of the moon, or
whatever. But if I do encounter it again, I'll collect as many details
as I can.

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

Title:
  fwupd using 200% CPU, but status of systemd services is  "inactive
  (dead)"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1630711/+subscriptions

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


[Bug 1630711] Re: fwupd using 200% CPU, but status of systemd services is "inactive (dead)"

2016-10-05 Thread Jason Gerard DeRose
Oops, I attached the wrong screenshot, here's the correct one.

** Attachment added: "Screenshot from 2016-10-05 12-06-26.png"
   
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1630711/+attachment/4755346/+files/Screenshot%20from%202016-10-05%2012-06-26.png

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

Title:
  fwupd using 200% CPU, but status of systemd services is  "inactive
  (dead)"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1630711/+subscriptions

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


[Bug 1630711] Re: fwupd using 200% CPU, but status of systemd services is "inactive (dead)"

2016-10-05 Thread Mario Limonciello
Thanks.  FYI, it starts using D-Bus activation.  Will happen when gnome-
software service starts with your session or when you use something that
needs fwupd (like fwupdmgr or gnome-software client)

** Changed in: fwupd (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/1630711

Title:
  fwupd using 200% CPU, but status of systemd services is  "inactive
  (dead)"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1630711/+subscriptions

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


[Bug 1630711] Re: fwupd using 200% CPU, but status of systemd services is "inactive (dead)"

2016-10-05 Thread Jason Gerard DeRose
** Attachment removed: "Screenshot from 2013-11-11 11:45:50.png"
   
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1630711/+attachment/4755311/+files/Screenshot%20from%202013-11-11%2011%3A45%3A50.png

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

Title:
  fwupd using 200% CPU, but status of systemd services is  "inactive
  (dead)"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1630711/+subscriptions

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


[Bug 1630711] Re: fwupd using 200% CPU, but status of systemd services is "inactive (dead)"

2016-10-05 Thread Jason Gerard DeRose
Yeah, I can do this, assuming I can reproduce it again. This is on my
work machine, so I had to just kill `fwupd` so I could get on with my
work in the meantime :D

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

Title:
  fwupd using 200% CPU, but status of systemd services is  "inactive
  (dead)"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1630711/+subscriptions

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


[Bug 1630711] Re: fwupd using 200% CPU, but status of systemd services is "inactive (dead)"

2016-10-05 Thread Mario Limonciello
Could you by chance installed debug symbols and attach to the the
process with GDB to see what it's spinning on?

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

Title:
  fwupd using 200% CPU, but status of systemd services is  "inactive
  (dead)"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1630711/+subscriptions

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


[Bug 1630711] Re: fwupd using 200% CPU, but status of systemd services is "inactive (dead)"

2016-10-05 Thread Jason Gerard DeRose
One other useful detail. There are actually 2 fwupd processes running,
both started by PID 1:

ps -ef | grep fwupd
root  2823 1 99 11:41 ?01:35:03 
/usr/lib/x86_64-linux-gnu/fwupd/fwupd
root  4712 1  0 11:44 ?00:00:00 
/usr/lib/x86_64-linux-gnu/fwupd/fwupd

But it's only process "2823" that's chewing up all the CPU.

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

Title:
  fwupd using 200% CPU, but status of systemd services is  "inactive
  (dead)"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1630711/+subscriptions

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