Bug 500860 - [RHEL5 U4] IA64 kernel-xen panic while booting
[RHEL5 U4] IA64 kernel-xen panic while booting
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel-xen (Show other bugs)
5.4
ia64 Linux
low Severity medium
: rc
: ---
Assigned To: Xen Maintainance List
Red Hat Kernel QE team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-05-14 11:15 EDT by Jeff Burke
Modified: 2009-05-14 16:52 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-05-14 16:52:38 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jeff Burke 2009-05-14 11:15:38 EDT
Description of problem:
When booting a ia64 system with kernel-xen the Dom0 panics

Version-Release number of selected component (if applicable):
2.6.18-147.el5xen

How reproducible:
Very often

Steps to Reproduce:
1. Install RHEL5.4 tree. Install 2.6.18-147.el5 kernel-xen
2. Install xen
3. Reboot
  
Actual results:
libvirtd[2843]: NaT consumption 17179869216 [1]
Modules linked in: deflate zlib_deflate ccm serpent blowfish twofish ecb xcbc crypto_hash cbc md5 sha256 sha512 des testmgr_cipher testmgr crypto_blkcipher aes_generic ipcomp6 ipcomp ah6 ah4 esp6 xfrm6_esp esp4 xfrm4_esp aead crypto_algapi xfrm4_tunnel tunnel4 xfrm4_mode_tunnel xfrm4_mode_transport xfrm6_mode_transport xfrm6_mode_tunnel xfrm6_tunnel tunnel6 af_key autofs4 hidp rfcomm l2cap bluetooth sunrpc ipv6 xfrm_nalgo crypto_api ib_iser rdma_cm ib_cm iw_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi2 scsi_transport_iscsi2 scsi_transport_iscsi vfat fat dm_multipath scsi_dh button parport_pc lp parport joydev sr_mod cdrom e1000 shpchp sg dm_raid45 dm_message dm_region_hash dm_mem_cache dm_snapshot dm_zero dm_mirror dm_log dm_mod usb_storage cciss sd_mod scsi_mod ext3 jbd uhci_hcd ohci_hcd ehci_hcd

Pid: 2843, CPU 0, comm:             libvirtd
psr : 00001010085a6010 ifs : 800000000000050d ip  : [<a000000100146670>]    Not tainted (2.6.18-147.el5xen)
ip is at follow_page+0x10/0x4e0
unat: 0000000000000000 pfs : 8000000000000207 rsc : 000000000000000b
rnat: 0000000000000000 bsps: 0000000000000000 pr  : 0000000000559999
ldrs: 0000000000000000 ccv : 0000000000000000 fpsr: 0009804c0270033f
csd : 0000000000000000 ssd : 0000000000000000
b0  : a00000010006d950 b6  : a00000010041ad00 b7  : a0000001000180b0
f6  : 1003e0000000000000002 f7  : 1003eaf8af8af8af8af8b
f8  : 1003e0000000000000046 f9  : 1003e0000000000000002
f10 : 1003e0000000000000046 f11 : 1003eaf8af8af8af8af8b
r1  : a000000100c57f80 r2  : 60000fffffcb0000 r3  : e0000001ba881bc8
r8  : e0000001ba881bb8 r9  : 60000fffffcac000 r10 : e0000001b58c5200
r11 : 0ffb0a2bc0000000 r12 : e0000001a621fb40 r13 : e0000001a6218000
r14 : e0000001b58c5210 r15 : 0000000000000001 r16 : 00000000000000ff
r17 : 00000009eb94a8af r18 : e0000001a746c004 r19 : 0000000a3d80ae20
r20 : 0000000051ec0571 r21 : 00000000146f6e6d r22 : 000000000144122b
r23 : 0000000001725de8 r24 : 0000000001725de8 r25 : a0007ffffe780000
r26 : a000000100a70ff8 r27 : a000000100a70ff8 r28 : a0007fffffea5e00
r29 : a000000000000000 r30 : e0000001a6218358 r31 : e0000001a6218148

Call Trace:
 [<a00000010001d220>] show_stack+0x40/0xa0
                                sp=e0000001a621f560 bsp=e0000001a62195f0
 [<a00000010001db30>] show_regs+0x850/0x8a0
                                sp=e0000001a621f730 bsp=e0000001a6219598
 [<a000000100043520>] die+0x1c0/0x380
                                sp=e0000001a621f730 bsp=e0000001a6219550
 [<a000000100043730>] die_if_kernel+0x50/0x80
                                sp=e0000001a621f750 bsp=e0000001a6219520
 [<a000000100677700>] ia64_fault+0x11a0/0x12c0
                                sp=e0000001a621f750 bsp=e0000001a62194c8
 [<a00000010006aea0>] xen_leave_kernel+0x0/0x3e0
                                sp=e0000001a621f970 bsp=e0000001a62194c8
 [<a000000100146670>] follow_page+0x10/0x4e0
                                sp=e0000001a621fb40 bsp=e0000001a6219460
 [<a00000010006d950>] xencomm_vaddr_to_paddr+0x230/0x340
                                sp=e0000001a621fb40 bsp=e0000001a6219440
 [<a00000010006db30>] xencomm_init_desc+0xd0/0x2a0
                                sp=e0000001a621fb40 bsp=e0000001a62193f0
 [<a00000010006df50>] xencomm_create+0xb0/0x180
                                sp=e0000001a621fb40 bsp=e0000001a62193b0
 [<a000000100070440>] privcmd_hypercall+0xa80/0x19c0
                                sp=e0000001a621fb40 bsp=e0000001a6219358
 [<a00000010041ae00>] privcmd_ioctl+0x100/0x920
                                sp=e0000001a621fda0 bsp=e0000001a62192f8
 [<a0000001001b4910>] do_ioctl+0x90/0x180
                                sp=e0000001a621fde0 bsp=e0000001a62192b8
 [<a0000001001b57c0>] vfs_ioctl+0xdc0/0xec0
                                sp=e0000001a621fde0 bsp=e0000001a6219270
 [<a0000001001b5990>] sys_ioctl+0xd0/0x140
                                sp=e0000001a621fe20 bsp=e0000001a62191e8
 [<a00000010006aba0>] xen_trace_syscall+0x100/0x140
                                sp=e0000001a621fe30 bsp=e0000001a62191e8
 [<a000000000010620>] __start_ivt_text+0xffffffff00010620/0x400
                                sp=e0000001a6220000 bsp=e0000001a62191e8
 <0>Kernel panic - not syncing: Fatal exception
 (XEN) Domain 0 crashed: rebooting machine in 5 seconds.


Expected results:
Ssytm should not panic

Additional info:
Comment 1 Chris Lalancette 2009-05-14 11:26:34 EDT
This seems to be a problem with this patch: linux-2.6-Re-fork-o_direct-race.patch.  Andrea, I think this was one of your patches, correct?

Chris Lalancette

Note You need to log in before you can comment on or make changes to this bug.