xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Cris Daniluk <cris.daniluk@gmail.com>
To: xen-devel@lists.xensource.com
Subject: Dom0 panic on xen 3.4.3
Date: Fri, 20 Aug 2010 14:15:25 -0400	[thread overview]
Message-ID: <AANLkTikDAAfS83wP5QFddXaRNGNzDkTfFondxa=XrdL9@mail.gmail.com> (raw)

I'm running Xen 3.4.3 final and observing the following kernel panic
when I fire up the 9th domU. dom0 is CentOS 5.5 running a XenLinux
kernel. grub.conf entry is below, followed by the dump. The kernel
crash is immediately after the 9th domU is unpaused.

title Xen 3.4.3 CentOS (2.6.18-194.11.1.el5xen)
        root (hd0,0)
        kernel /xen-3.4.3.gz dom0_mem=768M loglvl=all guest_loglvl=all
com1=38400
0,8n1 console=com1 sync_console noreboot
        module /vmlinuz-2.6.18-194.11.1.el5xen ro root=/dev/vg_internal/lv_base
console=hvc0,38400 norhgb netloop.nloopbacks=100
        module /mpp-2.6.18-194.11.1.el5xen.img
title CentOS (2.6.18-194.11.1.el5) with MPP
        root (hd0,0)



Unable to handle kernel paging request at ffff88002e864000 RIP:
 [<ffffffff8041a95f>] skb_copy_bits+0x114/0x1d3
PGD 11a5067 PUD 11a6067 PMD 131b067 PTE 0
Oops: 0000 [1] SMP
last sysfs file: /devices/xen-backend/vbd-2-51712/statistics/wr_sect
CPU 2
Modules linked in: xt_tcpudp xt_state ip_conntrack nfnetlink
xt_physdev bridge nfs lockd fscache nfs_acl sunrpc iptable_filter
ip_tables x_tables be2iscsi ib_iser rdma_cm ib_cm iw_cm ib_sa ib_mad
ib_core ib_addr iscsi_tcp bnx2i cnic ipv6 xfrm_nalgo crypto_api uio
cxgb3i cxgb3 8021q libiscsi_tcp libiscsi2 scsi_transport_iscsi2
scsi_transport_iscsi dm_round_robin dm_multipath scsi_dh video
backlight sbs power_meter hwmon i2c_ec dell_wmi wmi button battery
asus_acpi ac blkbk netbk blktap pciback parport_pc lp parport joydev
cdc_ether serial_core usbnet pcspkr bnx2 ide_cd i2c_i801 e1000e
i2c_core cdrom dm_raid45 dm_message dm_region_hash dm_mem_cache
dm_snapshot dm_zero dm_mirror dm_log dm_mod mppVhba(U) ata_piix libata
shpchp megaraid_sas mppUpper(U) sg sd_mod scsi_mod ext3 jbd uhci_hcd
ohci_hcd ehci_hcd
Pid: 0, comm: swapper Tainted: G      2.6.18-194.11.1.el5xen #1
RIP: e030:[<ffffffff8041a95f>]  [<ffffffff8041a95f>] skb_copy_bits+0x114/0x1d3
RSP: e02b:ffff88000112fdd0  EFLAGS: 00010246
RAX: 0000000000000042 RBX: ffff88001ef04480 RCX: 0000000000000b50
RDX: ffff8800238f0d00 RSI: ffff88002e864000 RDI: ffff880027bc0000
RBP: 0000000000000000 R08: ffff8800238f0d10 R09: 0000000000000b92
R10: 0000000000000b50 R11: 0000000000000000 R12: 0000000000000042
R13: 0000000000000042 R14: 0000000000000000 R15: ffff880027bc0000
FS:  00002b2e6ab313f0(0000) GS:ffffffff805d2100(0000) knlGS:0000000000000000
CS:  e033 DS: 002b ES: 002b
Process swapper (pid: 0, threadinfo ffff880006186000, task ffff8800000657e0)
Stack:  ffff88002c8b27c0  ffff88002b7c8b80  0000000000000b50  ffff88001e5abe80
 ffff8800289cf500  ffff88001ef04480  ffff880001be3200  ffffffff8836b732
 ffff8800289cf000  0000000000000042
Call Trace:
 <IRQ>  [<ffffffff8836b732>] :netbk:netif_be_start_xmit+0x241/0x471
 [<ffffffff8041fbde>] dev_hard_start_xmit+0x1b7/0x28a
 [<ffffffff8042fff5>] __qdisc_run+0x136/0x1f9
 [<ffffffff803b348c>] unmask_evtchn+0x2d/0xd7
 [<ffffffff80420f33>] net_tx_action+0xc9/0xf1
 [<ffffffff80212cd3>] __do_softirq+0x8d/0x13b
 [<ffffffff80260da4>] call_softirq+0x1c/0x278
 [<ffffffff8026e0c1>] do_softirq+0x31/0x98
 [<ffffffff8026df4d>] do_IRQ+0xec/0xf5
 [<ffffffff803b3e14>] evtchn_do_upcall+0x13b/0x1fb
 [<ffffffff802608d6>] do_hypervisor_callback+0x1e/0x2c
 <EOI>  [<ffffffff802063aa>] hypercall_page+0x3aa/0x1000
 [<ffffffff802063aa>] hypercall_page+0x3aa/0x1000
 [<ffffffff8026f4eb>] raw_safe_halt+0x84/0xa8
 [<ffffffff8026ca80>] xen_idle+0x38/0x4a
 [<ffffffff8024add7>] cpu_idle+0x97/0xba


Code: f3 a4 0f 84 a2 00 00 00 45 01 d4 49 89 ff 41 ff c6 45 89 cd
RIP  [<ffffffff8041a95f>] skb_copy_bits+0x114/0x1d3
 RSP <ffff88000112fdd0>
CR2: ffff88002e864000
test6: no IPv6 routers present
 <0>Kernel panic - not syncing: Fatal exception
 BUG: warning at
arch/x86_64/kernel/genapic_xen.c:92/xen_send_IPI_mask() (Tainted: G
 )

             reply	other threads:[~2010-08-20 18:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-20 18:15 Cris Daniluk [this message]
2010-08-20 23:59 ` Dom0 panic on xen 3.4.3 Pasi Kärkkäinen
2010-08-21  0:20   ` Cris Daniluk
2010-08-21 10:12     ` Pasi Kärkkäinen
2010-08-21 22:27       ` Cris Daniluk
2010-11-01 10:28         ` Paolo Bonzini
2010-12-28  0:50           ` prickett233
2010-12-28 10:38             ` Pasi Kärkkäinen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='AANLkTikDAAfS83wP5QFddXaRNGNzDkTfFondxa=XrdL9@mail.gmail.com' \
    --to=cris.daniluk@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).