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 120] New: Hard reboot on xm destroy of crashed domain

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 120] New: Hard reboot on xm destroy of crashed domain
From: ryanh@xxxxxxxxxx
Date: Wed, 27 Jul 2005 19:52:11 +0000
Delivery-date: Wed, 27 Jul 2005 19:52:15 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

           Summary: Hard reboot on xm destroy of crashed domain
           Product: Xen
           Version: unstable
          Platform: x86
        OS/Version: Linux-2.6
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: ryanh@xxxxxxxxxx

% hg tip
changeset:   5897:c02e5214247ee75f9cfa3d89b9792110c324cc3d
tag:         tip
user:        cl349@xxxxxxxxxxxxxxxxxxxx
date:        Wed Jul 27 13:41:49 2005
summary:     Get rid of internet_copy.jpg once more.
Hardware: 2-way Opteron, running in 32-bit mode, SATA harddrive, bcm5700 nic

When attempting to destroy a crashed domain, kernel bugs in dcache.h:294, and
causes hypervisor to reboot.

root@bebop:~ # xm list
Name              Id  Mem(MB)  CPU VCPU(s)  State  Time(s)  Console
Domain-0           0      507    0      2   r----     13.2
debian_sarge_1     1      128    1      8   r----     11.1     9601
debian_sarge_2     2      128    1      8   -----     22.8     9602
debian_sarge_3     3      128    1      8   -----     15.3     9603
debian_sarge_4     4      128    1      3   ----c      0.2     9604
root@bebop:~ # xm destroy 4

kernel BUG at include/linux/dcache.h:294 (dget)!
 [<c019e26e>] sysfs_remove_dir+0x13e/0x150
 [<c021ccb3>] kobject_del+0x13/0x30
 [<c040dc4a>] br_del_if+0x3a/0x64
 [<c040ec91>] br_device_event+0xe1/0x120
 [<c013165d>] notifier_call_chain+0x2d/0x50
 [<c03c1dff>] unregister_netdevice+0x13f/0x290
 [<c03c1f68>] unregister_netdev+0x18/0x30
 [<c02cfff8>] netif_destroy+0x78/0x90
 [<c02cf9bb>] netif_ctrlif_rx+0x4b/0x90
 [<c0105adc>] __ctrl_if_rxmsg_deferred+0x4c/0x60
 [<c01344c5>] worker_thread+0x1b5/0x280
 [<c042478c>] schedule+0x40c/0x700
 [<c0105a90>] __ctrl_if_rxmsg_deferred+0x0/0x60
 [<c011d420>] default_wake_function+0x0/0x20
 [<c011d420>] default_wake_function+0x0/0x20
 [<c0134310>] worker_thread+0x0/0x280
 [<c01393fa>] kthread+0xba/0xc0
 [<c0139340>] kthread+0x0/0xc0
 [<c0108415>] kernel_thread_helper+0x5/0x10
Kernel panic - not syncing: BUG!
 smp_send_stop disable_local_APIC
stop_this_cpu disable_local_APIC
(XEN) Domain 0 shutdown: rebooting machine.

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

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 120] New: Hard reboot on xm destroy of crashed domain, ryanh <=