Kernel Oops - unable to handle kernel paging request; when starting libvirtd

Bug #1478672 reported by koen_92
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Kernel Oops occur as soon as I start the libvirtd daemon (/usr/bin/libvirtd from package libvirt-bin). This happens only on this system (MS-7640/990XA-GD55), but it happens every time I try to start libvirtd. Creating/Starting a VM is not needed to trigger this oops.

libvirtd will hang forever after starting: interaction with libvirtd isn't possible (i.e. the command 'virsh' will also hang forever).

I also tried a new mainline kernel (linux-image-4.1.3-040103-generic_4.1.3-040103.201507220129_amd64), but that gives the same problem.

Steps to reproduce:
1. Boot Linux on this hardware
2. run libvirtd

I ran a memtest, which gave no errors.

Kernel cmdline: ro quiet splash iommu=pt iommu=1
CPU: AMD FX(tm)-4100 Quad-Core Processor
Kernel: Ubuntu 3.13.0-59.98-generic 3.13.11-ckt22 (but also happens on 4.1+)
Ubuntu version: 14.04.2

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-59-generic 3.13.0-59.98
ProcVersionSignature: Ubuntu 3.13.0-59.98-generic 3.13.11-ckt22
Uname: Linux 3.13.0-59-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC1', '/dev/snd/pcmC1D0c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Date: Mon Jul 27 20:59:40 2015
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: MSI MS-7640
ProcFB:

ProcKernelCmdLine: root=UUID=7be2b569-ee1b-4dd2-b8a5-99398f731235 ro quiet splash iommu=pt iommu=1
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-59-generic N/A
 linux-backports-modules-3.13.0-59-generic N/A
 linux-firmware 1.127.13
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/06/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V23.2
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: 990XA-GD55 (MS-7640)
dmi.board.vendor: MSI
dmi.board.version: 4.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 4.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV23.2:bd03/06/2013:svnMSI:pnMS-7640:pvr4.0:rvnMSI:rn990XA-GD55(MS-7640):rvr4.0:cvnMSI:ct3:cvr4.0:
dmi.product.name: MS-7640
dmi.product.version: 4.0
dmi.sys.vendor: MSI

Revision history for this message
koen_92 (koenvaningen) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Chris J Arges (arges) wrote :

1) Does this happen even with a clean libvirt install? I.e. install Ubuntu, then install ubuntu-virt-server and see if the crashes happen on libvirtd starting?
2) You could get a crashdump of this when it happens. This may let us know which string is causing the oops and what led up to it.
https://wiki.ubuntu.com/Kernel/CrashdumpRecipe

--chris

Changed in linux (Ubuntu):
importance: Undecided → High
assignee: nobody → Chris J Arges (arges)
importance: High → Medium
Revision history for this message
koen_92 (koenvaningen) wrote :

I reinstalled Ubuntu server 14.04.2 (which was delivered with 3.16), applied all the updates and installed ubuntu-virt-server. And now seems everything to be fine! I even copied over the old configuration/xml files to this new system, and still no kernel oops.

So now I don't know what could have happened? Silent disk corruption?

At least I'm not able to reproduce this bug in a completely clean system, so I'm closing the bug now.

Thanks for your suggestions!

Changed in linux (Ubuntu):
status: Confirmed → Invalid
Chris J Arges (arges)
Changed in linux (Ubuntu):
assignee: Chris J Arges (arges) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.