Re:Re: kernel panic.if it is xen bug?attached pic

[yue <ooolinux@163.com>]

[-- Attachment #1.1: Type: text/plain, Size: 5385 bytes --]

xen-4.0.1-6.fc12.x86_64
kernel-2.6.32.23-170.xendom0.fc12.x86_64
intel x86_64,GenuineIntel,16cpus
because panic info just has one screen,so no more details.
guest os  is hosted on image file. many physical nodes share one lun  with ocfs2.
 
1)kernel panic:not syncing:fatal exception in interrupt. comm swapper (occur many times)
2)BUG soft lockup CPU#4 stuck for 61s![events/4:55].(occur many times)
comm:events/4
3)BUG:unable to handle kernel paging request at 000000180000018....
oops: 0000 [#6] SMP
Apr 18 03:40:45 res-hy024 kernel: ------------[ cut here ]------------
Apr 18 03:40:45 res-hy024 kernel: kernel BUG at mm/slub.c:2969!
Apr 18 03:40:45 res-hy024 kernel: invalid opcode: 0000 [#1] SMP
Apr 18 03:40:45 res-hy024 kernel: last sysfs file: /sys/devices/system/cpu/cpu15/cache/index2/shared_cpu_map
Apr 18 03:40:45 res-hy024 kernel: CPU 3
Apr 18 03:40:45 res-hy024 kernel: Modules linked in: ocfs2 ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue configfs blktap fuse xt_temac 8021q garp ip6table_filter ip6_tables ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_nat bridge stp llc sunrpc ib_iser rdma_cm ib_cm iw_cm ib_sa ib_mad ib_core ib_addr ipv6 iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi xen_netback xen_blkback blkback_pagemap xen_gntdev xen_evtchn xenfs igb i2c_i801 ioatdma shpchp dca joydev iTCO_wdt iTCO_vendor_support serio_raw pata_acpi ata_generic usb_storage pata_jmicron megaraid_sas floppy radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core [last unloaded: scsi_wait_scan]
Apr 18 03:40:45 res-hy024 kernel: Pid: 7117, comm: ifconfig Not tainted 2.6.32.23-170.xendom0.fc12.x86_64 #1 X8DTN
Apr 18 03:40:45 res-hy024 kernel: RIP: e030:[<ffffffff8110ed21>]  [<ffffffff8110ed21>] kfree+0x62/0xd4
Apr 18 03:40:45 res-hy024 kernel: RSP: e02b:ffff8801a2619d68  EFLAGS: 00010246
Apr 18 03:40:45 res-hy024 kernel: RAX: 0040000000080000 RBX: ffff8801c7995080 RCX: 0000000000000003
Apr 18 03:40:45 res-hy024 kernel: RDX: ffffea0000000000 RSI: ffffea0003800000 RDI: ffff880100000009
Apr 18 03:40:45 res-hy024 kernel: RBP: ffff8801a2619d88 R08: 0000000000000000 R09: 0000000000000000
Apr 18 03:40:45 res-hy024 kernel: R10: ffff8801c8f18c48 R11: ffff8801c9387e30 R12: ffff880100000009
Apr 18 03:40:45 res-hy024 kernel: R13: ffffffff811eeaad R14: ffff8801c217eb40 R15: ffff8801c60113f8
Apr 18 03:40:45 res-hy024 kernel: FS:  00007f277792c7a0(0000) GS:ffff8800280ac000(0000) knlGS:0000000000000000
Apr 18 03:40:45 res-hy024 kernel: CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
Apr 18 03:40:45 res-hy024 kernel: CR2: 00007f277722b050 CR3: 0000000001001000 CR4: 0000000000002660
Apr 18 03:40:45 res-hy024 kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Apr 18 03:40:45 res-hy024 kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Apr 18 03:40:45 res-hy024 kernel: Process ifconfig (pid: 7117, threadinfo ffff8801a2618000, task ffff8801ae11c5f0)
Apr 18 03:40:45 res-hy024 kernel: Stack:
Apr 18 03:40:45 res-hy024 kernel: ffff8801c7995080 ffff8801c7995080 0000000000000010 ffff8801c60113f8
Apr 18 03:40:45 res-hy024 kernel: <0> ffff8801a2619d98 ffffffff811eeaad ffff8801a2619da8 ffffffff811e8551
Apr 18 03:40:45 res-hy024 kernel: <0> ffff8801a2619df8 ffffffff8111e711 ffff8801c217eb40 ffff8801c29eea00
Apr 18 03:40:45 res-hy024 kernel: Call Trace:
Apr 18 03:40:45 res-hy024 kernel: [<ffffffff811eeaad>] selinux_file_free_security+0x23/0x25
Apr 18 03:40:45 res-hy024 kernel: [<ffffffff811e8551>] security_file_free+0x16/0x18
Apr 18 03:40:45 res-hy024 kernel: [<ffffffff8111e711>] __fput+0x132/0x1dc
Apr 18 03:40:45 res-hy024 kernel: [<ffffffff8111e7d5>] fput+0x1a/0x1c
Apr 18 03:40:45 res-hy024 kernel: [<ffffffff810f609f>] remove_vma+0x56/0x8c
Apr 18 03:40:45 res-hy024 kernel: [<ffffffff810f61e5>] exit_mmap+0x110/0x132
Apr 18 03:40:45 res-hy024 kernel: [<ffffffff81054fbb>] mmput+0x5e/0xca
Apr 18 03:40:45 res-hy024 kernel: [<ffffffff810599a3>] exit_mm+0x109/0x115
Apr 18 03:40:45 res-hy024 kernel: [<ffffffff8105b47b>] do_exit+0x212/0x6f9
Apr 18 03:40:45 res-hy024 kernel: [<ffffffff8145f495>] ? do_page_fault+0x2c2/0x2f2
Apr 18 03:40:45 res-hy024 kernel: [<ffffffff8105b9e3>] do_group_exit+0x81/0xab
Apr 18 03:40:45 res-hy024 kernel: [<ffffffff8105ba24>] sys_exit_group+0x17/0x1b
Apr 18 03:40:45 res-hy024 kernel: [<ffffffff81012d32>] system_call_fastpath+0x16/0x1b
Apr 18 03:40:45 res-hy024 kernel: Code: 83 c3 08 48 83 3b 00 eb ec 49 83 fc 10 0f 86 82 00 00 00 4c 89 e7 e8 f7 e4 ff ff 48 89 c6 48 8b 00 84 c0 78 14 66 a9 00 c0 75 04 <0f> 0b eb fe 48 89 f7 e8 aa 19 fd ff eb 5c 48 8b 4d 08 48 8b 7e
Apr 18 03:40:45 res-hy024 kernel: RIP  [<ffffffff8110ed21>] kfree+0x62/0xd4
Apr 18 03:40:45 res-hy024 kernel: RSP <ffff8801a2619d68>
Apr 18 03:40:45 res-hy024 kernel: ---[ end trace d94776bc505e025a ]---
Apr 18 03:40:45 res-hy024 kernel: Fixing recursive fault but reboot is needed!

4) panic  capture is attached.
 
thanks all



At 2011-04-22 20:00:40，"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com> wrote:

>On Fri, Apr 22, 2011 at 02:21:39PM +0800, yue wrote:
>> what is the core root?
>
>You have to provide more details. What you did, did it work before. What kind of hardware,
>does it work with baremetal? What version of Xen.
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel

[-- Attachment #1.2: Type: text/html, Size: 6373 bytes --]

[-- Attachment #2: QuickShot.rar --]
[-- Type: application/octet-stream, Size: 479419 bytes --]

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel