qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] [Bug 546458] Re: kernel NULL pointer in -virtual (-server)


From: C de-Avillez
Subject: [Qemu-devel] [Bug 546458] Re: kernel NULL pointer in -virtual (-server) kernel
Date: Thu, 10 Jun 2010 18:23:58 -0000

Just to confirm -- still present, 10.04 LTS up-to-date, UEC images also
10.04 up-to-date. A 2,000 run creating KVM instances under Eucalyptus
shows 6 occurences of this OOPS:

WARNING:INSTANCE i-3EDE078A:[  129.998256] BUG: unable to handle kernel NULL 
pointer dereference at 00000358
WARNING:INSTANCE i-406C06CE:[   89.245841] BUG: unable to handle kernel NULL 
pointer dereference at 0000000000000358
WARNING:INSTANCE i-411D0851:[  158.375444] BUG: unable to handle kernel NULL 
pointer dereference at 00000358
WARNING:INSTANCE i-4E1C08D4:[  196.089623] BUG: unable to handle kernel NULL 
pointer dereference at 0000000000000358
WARNING:INSTANCE i-54800A8D:[   67.825483] BUG: unable to handle kernel NULL 
pointer dereference at 0000000000000358
WARNING:INSTANCE i-5E970AA3:[   87.610866] BUG: unable to handle kernel NULL 
pointer dereference at 00000358

-- 
kernel NULL pointer in -virtual (-server) kernel
https://bugs.launchpad.net/bugs/546458
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

Status in QEMU: Invalid
Status in “linux” package in Ubuntu: Triaged
Status in “qemu-kvm” package in Ubuntu: Confirmed
Status in “linux” package in Fedora: Unknown

Bug description:
When stress testing eucalyptus we have run into this oops inside VMs
[   82.907577] BUG: unable to handle kernel NULL pointer dereference at 
0000000000000358^M
[   82.908842] IP: [<ffffffff813982e8>] sym_int_sir+0x2a8/0x750^M
[   82.909773] PGD 0 ^M
[   82.910110] Thread overran stack, or stack corrupted^M
[   82.910870] Oops: 0000 [#1] SMP ^M
[   82.911407] last sysfs file: /sys/devices/virtual/block/ram9/uevent^M

We launched 18 instances, 2 of them failed this way.  The instances run with 
192M of memory.  With 6 VM launches on a single node all at the same time the 
host is under heavy load.

This occurred in 20100323 lucid x86_64 uec-image instance.

ProblemType: Bug
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: 
ls: cannot access /dev/snd/: No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
CurrentDmesg:
 
Date: Wed Mar 24 22:06:32 2010
DistroRelease: Ubuntu 10.04
Frequency: Once a day.
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Bochs Bochs
Package: linux-image-2.6.32-16-virtual 2.6.32-16.25
PciMultimedia:
 
ProcCmdLine: root=/dev/sda1 console=ttyS0
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: User Name 2.6.32-16.25-server
Regression: No
Reproducible: No
SourcePackage: linux
TestedUpstream: No
Uname: Linux 2.6.32-16-server x86_64
dmi.bios.date: 01/01/2007
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias: 
dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr:
dmi.product.name: Bochs
dmi.sys.vendor: Bochs





reply via email to

[Prev in Thread] Current Thread [Next in Thread]