libvirtd crashed with SIGABRT in __kernel_vsyscall()

[Joshua R. Poulson]

Logging after clean boot.

Natty Beta 1

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: libvirt-bin 0.8.8-1ubuntu5
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic-pae 2.6.38
Uname: Linux 2.6.38-7-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Mon Apr 4 12:12:43 2011
ExecutablePath: /usr/sbin/libvirtd
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
ProcAttrCurrent: /usr/sbin/libvirtd (enforce)
ProcCmdline: /usr/sbin/libvirtd -d
ProcEnviron: PATH=(custom, no user)
Signal: 6
SourcePackage: libvirt
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
Title: libvirtd crashed with SIGABRT in __kernel_vsyscall()
UpgradeStatus: Upgraded to natty on 2011-03-31 (4 days ago)
UserGroups:

[Serge Hallyn (serge-hallyn)]

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)

[Joshua R. Poulson (jrp)]

I had booted and the error appeared as I was logging in. I don't I logged in particularly early in the boot.

[Serge Hallyn (serge-hallyn)]

Could you attach the output of 'sudo lspci -v'? If it happens again - or if you have not yet rebooted since that happened - could you attach /var/log/boot.log?

Thanks, still trying to reproduce.