This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-bugs] [Bug 626] New: Kernel oops when using domU's

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 626] New: Kernel oops when using domU's
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Sat, 22 Apr 2006 08:11:28 -0700
Delivery-date: Sat, 22 Apr 2006 08:12:04 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

           Summary: Kernel oops when using domU's
           Product: Xen
           Version: unstable
          Platform: x86
        OS/Version: Linux-2.6
            Status: NEW
          Severity: major
          Priority: P2
         Component: Unspecified
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: markus.woschank@xxxxxxxxx

reproduceable: yes
happens after starting one or more domU (gentoo), sometimes it runs for a
couple of minutes but not for long.

tried 3.0.1, 3.0.2, testing, and unstable (unstable from 06/05/21), all
versions seem to produce the same oops (have not saved the others, but look a

debian sarge

amd opteron

debugging difficult because i only have remote access to the machine

note that "Error: Device 2049 (vbd) could not be connected. Backend device not
found." only shows up from time to time, sometime the vm starts normally

kernel (xen) paramters:
tried with and without

kernel oops:
Error: Device 2049 (vbd) could not be connected. Backend device not found.
echo365 kernel: SMP
echo365 kernel: CPU:    0
echo365 kernel: EIP is at run_workqueue+0x52/0xf0
echo365 kernel: Oops: 0002 [#1]
echo365 kernel: eax: 00000020   ebx: c03f4b70   ecx: fbf47000   edx: c15302cc
echo365 kernel: esi: c03f4b74   edi: c15302c0   ebp: 6474e551   esp: c0c2df28
echo365 kernel: ds: 007b   es: 007b   ss: 0069
echo365 kernel: Process events/0 (pid: 5, threadinfo=c0c2c000 task=c091f560)
echo365 kernel: Stack: <0>00000000 c012daa0 c0c2df3c c15302e0 c15302cc 00000004
00000000 c15302d4
echo365 kernel:        c0c2df8c c15302cc c0c2c000 c01315ac c15302c0 c0c2df6c
00000000 ffffffff
echo365 kernel:        ffffffff 00000001 00000000 c0119150 00010000 00000000
00000000 c091f560
echo365 kernel: Call Trace:
echo365 kernel:  [do_sigaction+448/688] do_sigaction+0x1c0/0x2b0
echo365 kernel:  [worker_thread+332/368] worker_thread+0x14c/0x170
echo365 kernel:  [default_wake_function+0/32] default_wake_function+0x0/0x20
echo365 kernel:  [default_wake_function+0/32] default_wake_function+0x0/0x20
echo365 kernel:  [worker_thread+0/368] worker_thread+0x0/0x170
echo365 kernel:  [kthread+186/192] kthread+0xba/0xc0
echo365 kernel:  [kthread+0/192] kthread+0x0/0xc0
echo365 kernel:  [kernel_thread_helper+5/16] kernel_thread_helper+0x5/0x10
echo365 kernel: Code: 47 0c 89 44 24 10 8b 77 0c 39 c6 74 76 8d 47 20 89 44 24
0c 90 8d 74 26 00 8d 5e fc 8b 43 0c 89 44 24 14 8b 56 04 8b 06 8b 6b 10 <89> 50
04 89 02 89 f8 89 36 89 76 04 8b 54 24 18 e8 d9 13 1f 00

will attach (dmesg,xm info,xm dmesg,grub.conf)

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list