Cannot load kvm and subsequent "oops"

Bug #92159 reported by aamukahvi
12
Affects Status Importance Assigned to Milestone
kvm (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: kvm

Hi,

This on Core 2 Duo E6600, Asrock 775-VSTA, nvidia-glx and Atheros.
Linux 2.6.20-10-generic #2 SMP Mon Mar 12 00:02:49 UTC 2007 i686 GNU/Linux
kvm | 16-1ubuntu1 | http://archive.ubuntu.com feisty/universe Packages

Modprobe of kvm-intel fails:
---------------------------------------
$ sudo modprobe kvm-intel
Password:
WARNING: Error inserting kvm (/lib/modules/2.6.20-10-generic/kernel/drivers/kvm/kvm.ko): Is a directory
FATAL: Error inserting kvm_intel (/lib/modules/2.6.20-10-generic/kernel/drivers/kvm/kvm-intel.ko): Unknown symbol in module, or unknown parameter (see dmesg)
---------------------------------------

dmesg present Unknown symbols, check attached dmesg-modprobe.

Then after a while a kernel "oops" appears and possible hard locks, check attached dmesg-oops

Revision history for this message
Alex Zvoleff (azvoleff) wrote :
Download full text (7.7 KiB)

Confirmed here. See bug 92291 regarding failure of kvm-intel to load. Then, I start to get a kernel "oops" with almost anything I run in a virutal terminal.

azvoleff@azvoleff-laptop:~$ mv
Segmentation fault
azvoleff@azvoleff-laptop:~$
Message from syslogd@localhost at Wed Mar 14 11:01:28 2007 ...
localhost kernel: [ 2105.692000] Oops: 0000 [#6]

Message from syslogd@localhost at Wed Mar 14 11:01:28 2007 ...
localhost kernel: [ 2105.692000] SMP

Message from syslogd@localhost at Wed Mar 14 11:01:28 2007 ...
localhost kernel: [ 2105.692000] CPU: 0

Message from syslogd@localhost at Wed Mar 14 11:01:28 2007 ...
localhost kernel: [ 2105.692000] EIP: 0060:[get_filesystem_list+39/128] Tainted: PF VLI

Message from syslogd@localhost at Wed Mar 14 11:01:28 2007 ...
localhost kernel: [ 2105.692000] EFLAGS: 00010297 (2.6.20-10-generic #2)

Message from syslogd@localhost at Wed Mar 14 11:01:28 2007 ...
localhost kernel: [ 2105.692000] EIP is at get_filesystem_list+0x27/0x80

Message from syslogd@localhost at Wed Mar 14 11:01:28 2007 ...
localhost kernel: [ 2105.692000] eax: 00000012 ebx: fa668180 ecx: 0000000b edx: 00000012

Message from syslogd@localhost at Wed Mar 14 11:01:28 2007 ...
localhost kernel: [ 2105.692000] esi: 0000011b edi: f7f43000 ebp: 00000000 esp: f50b1f10

Message from syslogd@localhost at Wed Mar 14 11:01:28 2007 ...
localhost kernel: [ 2105.692000] ds: 007b es: 007b ss: 0068

Message from syslogd@localhost at Wed Mar 14 11:01:28 2007 ...
localhost kernel: [ 2105.692000] Process mv (pid: 7513, ti=f50b0000 task=f5dc4030 task.ti=f50b0000)

Message from syslogd@localhost at Wed Mar 14 11:01:28 2007 ...
localhost kernel: [ 2105.692000] Stack: f7f43109 c0366b20 c0366bc3 f90fb40f f50b1f64 00000c00 f7f43000 c01aeae7

Message from syslogd@localhost at Wed Mar 14 11:01:28 2007 ...
localhost kernel: [ 2105.692000] f50b1f60 c01aeac0 00000c00 00000000 f7f43000 c01acf2f 00000c00 f50b1f64

Message from syslogd@localhost at Wed Mar 14 11:01:28 2007 ...
localhost kernel: [ 2105.692000] 00000000 00000fff 0805f0d0 dfffc640 00000000 00000000 f60ba600 0805f0d0

Message from syslogd@localhost at Wed Mar 14 11:01:28 2007 ...
localhost kernel: [ 2105.692000] Call Trace:

Message from syslogd@localhost at Wed Mar 14 11:01:28 2007 ...
localhost kernel: [ 2105.692000] [filesystems_read_proc+39/96] filesystems_read_proc+0x27/0x60

Message from syslogd@localhost at Wed Mar 14 11:01:28 2007 ...
localhost kernel: [ 2105.692000] [filesystems_read_proc+0/96] filesystems_read_proc+0x0/0x60

Message from syslogd@localhost at Wed Mar 14 11:01:28 2007 ...
localhost kernel: [ 2105.692000] [proc_file_read+527/720] proc_file_read+0x20f/0x2d0

Message from syslogd@localhost at Wed Mar 14 11:01:28 2007 ...
localhost kernel: [ 2105.692000] [proc_file_read+0/720] proc_file_read+0x0/0x2d0

Message from syslogd@localhost at Wed Mar 14 11:01:28 2007 ...
localhost kernel: [ 2105.692000] [sys_read+65/112] sys_read+0x41/0x70

Message from syslogd@localhost at Wed Mar 14 11:01:28 2007 ...
localhost kernel: [ 2105.692000] [sysenter_past_esp+103/153] sysenter_past_esp+0x67/0x99

Message from syslogd@localhost at Wed Mar 14 11:...

Read more...

Revision history for this message
Alfredo Matos (alfmatos) wrote :

I can confirm this. modprobe kvm fails, kvm-intel fails, and a subsequent oops is bound to happen (and did).

Attaching dmesg of the failed symbols

Revision history for this message
Alfredo Matos (alfmatos) wrote :

Also attached a cpuinfo for information.

Revision history for this message
Alfredo Matos (alfmatos) wrote :

Attached the Oops dmesg trace so we can cleanup the bug description.

description: updated
Revision history for this message
Alfredo Matos (alfmatos) wrote :

Added lspci -vvnn log as requested in https://wiki.ubuntu.com/DebuggingKernelProblems

Revision history for this message
Alfredo Matos (alfmatos) wrote :

Added uname -a log, as requested in https://wiki.ubuntu.com/DebuggingKernelProblems

Changed in kvm:
status: Unconfirmed → Confirmed
Revision history for this message
Alfredo Matos (alfmatos) wrote :

The linux-2.6.20-11 kernel release fixes the kvm problems.

Changed in kvm:
status: Confirmed → Fix Released
Revision history for this message
Matej Kenda (matejken) wrote :

Works on my machine as well.

$ uname -a
Linux mk 2.6.20-11-generic #2 SMP Thu Mar 15 08:03:07 UTC 2007 i686 GNU/Linux

$ cat /var/lib/acpi-support/*-*
68YVD Ver. F.0F
Hewlett-Packard
HP Compaq nw8440 (RH415EA#ABB)
F.0F

Revision history for this message
aamukahvi (aamukahvi) wrote :

Yeah works now for me as well.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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