ubuntu-x-swat team mailing list archive

Thread
Date

[Bug 750645] Re: libvirtd crashed with SIGABRT in __kernel_vsyscall()

To: ubuntu-x-swat@xxxxxxxxxxxxxxxxxxx
From: Serge Hallyn <750645@xxxxxxxxxxxxxxxxxx>
Date: Mon, 04 Apr 2011 21:12:44 -0000
Reply-to: Bug 750645 <750645@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

Thanks for taking the time to report this bug and helping to make Ubuntu
better.

Hm, once again libpciaccess shows up in the stack trace.

Did you do anything in particular before the crash happened?  Can you
trigger this kind of crash with just 'restart libvirt-bin', or is it
only, unpredictably, with a reboot?

(Probably a dup, but still looking through the logs)

** Changed in: libvirt (Ubuntu)
       Status: New => Incomplete

** Changed in: libvirt (Ubuntu)
   Importance: Undecided => Critical

** Also affects: libpciaccess (Ubuntu)
   Importance: Undecided
       Status: New

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

Title:
  libvirtd crashed with SIGABRT in __kernel_vsyscall()