Hi,
Im trying to get OpenShift Origin running on a F17 EC2 image but keep running into a kernel panic. The panic happens in random places and I haven't really been able to narrow it down to a specific service or part of Fedora. Can anyone help me track this down? or point me to someone who could help?
Thanks Krishna
[53896281.125197] ------------[ cut here ]------------ [53896281.125213] kernel BUG at arch/x86/mm/fault.c:396! [53896281.125218] invalid opcode: 0000 [#1] SMP [53896281.125224] CPU 0 [53896281.125226] Modules linked in: ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack xen_netfront xen_blkfront [last unloaded: scsi_wait_scan] [53896281.125248] [53896281.125252] Pid: 609, comm: mongod Not tainted 3.3.4-5.fc17.x86_64 #1 [53896281.125259] RIP: e030:[<ffffffff815eef4f>] [<ffffffff815eef4f>] vmalloc_fault+0x11f/0x208 [53896281.125275] RSP: e02b:ffff8801d15d3a18 EFLAGS: 00010046 [53896281.125280] RAX: ffff8801d11c9ff8 RBX: ffffe8fffffc7008 RCX: 0000000000000000 [53896281.125286] RDX: 00003ffffffff000 RSI: ffff880000000ff8 RDI: 0000000000000000 [53896281.125291] RBP: ffff8801d15d3a38 R08: 0000000000000001 R09: 0000000000000001 [53896281.125298] R10: 0000000000000001 R11: 0000000000000001 R12: ffff8801d3ef2e88 [53896281.125304] R13: ffff8801d11c9ff8 R14: ffff880000000ff8 R15: 0000000000000002 [53896281.125314] FS: 00007f7d49272740(0000) GS:ffff8801dff7c000(0000) knlGS:0000000000000000 [53896281.125320] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b [53896281.125325] CR2: ffffe8fffffc7008 CR3: 00000001d3ef2000 CR4: 0000000000002660 [53896281.125331] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [53896281.125337] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [53896281.125344] Process mongod (pid: 609, threadinfo ffff8801d15d2000, task ffff8801d0c3ae40) [53896281.125350] Stack: [53896281.125352] ffffe8fffffc7008 0000000000000029 ffff8801d15d3b58 0000000000000000 [53896281.125361] ffff8801d15d3b48 ffffffff815ef4e9 ffff880100000041 ffff8801dff8f580 [53896281.125369] ffff8801d0c3ae40 0000000000000070 0000000000000010 0000000000000001 [53896281.125378] Call Trace: [53896281.125384] [<ffffffff815ef4e9>] do_page_fault+0x399/0x4b0 [53896281.125392] [<ffffffff81004560>] ? load_TLS_descriptor+0x40/0xc0 [53896281.125398] [<ffffffff81004a72>] ? xen_mc_flush+0xb2/0x1b0 [53896281.125404] [<ffffffff815ebef5>] page_fault+0x25/0x30 [53896281.125413] [<ffffffff81172f70>] ? mem_cgroup_charge_statistics.isra.15+0x30/0x50 [53896281.125422] [<ffffffff81175e38>] __mem_cgroup_uncharge_common+0xf8/0x2f0 [53896281.125428] [<ffffffff81004ea1>] ? __raw_callee_save_xen_pte_val+0x11/0x1e [53896281.125434] [<ffffffff81178e1b>] mem_cgroup_uncharge_page+0x2b/0x40 [53896281.125441] [<ffffffff8114df4d>] page_remove_rmap+0x3d/0xc0 [53896281.125450] [<ffffffff81142946>] unmap_vmas+0x5c6/0x930 [53896281.125455] [<ffffffff8114ae72>] exit_mmap+0xa2/0x150 [53896281.125463] [<ffffffff81053c1b>] mmput+0x7b/0x100 [53896281.125469] [<ffffffff8105a714>] exit_mm+0x104/0x130 [53896281.125475] [<ffffffff8105a8c3>] do_exit+0x183/0x8c0 [53896281.125483] [<ffffffff81084bdb>] ? finish_task_switch+0x4b/0xe0 [53896281.125490] [<ffffffff8105b34f>] do_group_exit+0x3f/0xa0 [53896281.125495] [<ffffffff8105b3c7>] sys_exit_group+0x17/0x20 [53896281.125502] [<ffffffff815f38e9>] system_call_fastpath+0x16/0x1b [53896281.125506] Code: 4c 89 e7 e8 8d 25 ff ff 4c 89 ef 48 89 de 49 89 c6 e8 7f 25 ff ff 48 83 38 00 49 89 c5 0f 84 e5 00 00 00 49 8b 3e 48 85 ff 75 02 <0f> 0b ff 14 25 20 74 a1 81 48 89 c2 49 8b 7d 00 ff 14 25 20 74 [53896281.125552] RIP [<ffffffff815eef4f>] vmalloc_fault+0x11f/0x208 [53896281.125559] RSP <ffff8801d15d3a18> [53896281.125564] ---[ end trace c7ba81a3d7f88704 ]--- [53896281.125569] Fixing recursive fault but reboot is needed!
On Tue, Jan 29, 2013 at 04:51:06PM -0800, Krishna Raman wrote:
Im trying to get OpenShift Origin running on a F17 EC2 image but keep running into a kernel panic.
What kernel version are you running in the image? If you update to the latest F17 kernel (rather than the one that comes built-in) does that hepl?
On Jan 30, 2013, at 6:55 AM, Matthew Miller wrote:
On Tue, Jan 29, 2013 at 04:51:06PM -0800, Krishna Raman wrote:
Im trying to get OpenShift Origin running on a F17 EC2 image but keep running into a kernel panic.
What kernel version are you running in the image? If you update to the latest F17 kernel (rather than the one that comes built-in) does that hepl?
I have tried running with the stock kernel that comes with the image as well as the latest kernel from updates. Both of then are resulting in a kernel panic. Im not really sure how to proceed at this point.
--Krishna
-- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ mattdm@fedoraproject.org _______________________________________________ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud
On Thu, Jan 31, 2013 at 02:50:09PM -0800, Krishna Raman wrote:
On Tue, Jan 29, 2013 at 04:51:06PM -0800, Krishna Raman wrote:
Im trying to get OpenShift Origin running on a F17 EC2 image but keep running into a kernel panic.
What kernel version are you running in the image? If you update to the latest F17 kernel (rather than the one that comes built-in) does that hepl?
I have tried running with the stock kernel that comes with the image as well as the latest kernel from updates. Both of then are resulting in a kernel panic. Im not really sure how to proceed at this point.
If you want to track it down further, get whatever log information you can and file a bug in http://bugzilla.redhat.com/
Alternately or also, does the same thing happen on F18?
On Jan 31, 2013, at 5:28 PM, Matthew Miller mattdm@fedoraproject.org wrote:
On Thu, Jan 31, 2013 at 02:50:09PM -0800, Krishna Raman wrote:
On Tue, Jan 29, 2013 at 04:51:06PM -0800, Krishna Raman wrote:
Im trying to get OpenShift Origin running on a F17 EC2 image but keep running into a kernel panic.
What kernel version are you running in the image? If you update to the latest F17 kernel (rather than the one that comes built-in) does that hepl?
I have tried running with the stock kernel that comes with the image as well as the latest kernel from updates. Both of then are resulting in a kernel panic. Im not really sure how to proceed at this point.
If you want to track it down further, get whatever log information you can and file a bug in http://bugzilla.redhat.com/
Alternately or also, does the same thing happen on F18?
F18 ec2 images seem to be a lot more stable and I am going to switch development to these instead.
Thanks --Krishna
-- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ mattdm@fedoraproject.org _______________________________________________ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud
On Thu, Jan 31, 2013 at 10:50:10PM -0800, Krishna Raman wrote:
F18 ec2 images seem to be a lot more stable and I am going to switch development to these instead.
Glad to hear it!
Hi Matthew,
It looks like F18 suffers from the same problem. It might have something to do with CGroups or selinux. I will file a bug against Fedora.
--Krishna
On Jan 31, 2013, at 10:50 PM, Krishna Raman kraman@gmail.com wrote:
On Jan 31, 2013, at 5:28 PM, Matthew Miller mattdm@fedoraproject.org wrote:
On Thu, Jan 31, 2013 at 02:50:09PM -0800, Krishna Raman wrote:
On Tue, Jan 29, 2013 at 04:51:06PM -0800, Krishna Raman wrote:
Im trying to get OpenShift Origin running on a F17 EC2 image but keep running into a kernel panic.
What kernel version are you running in the image? If you update to the latest F17 kernel (rather than the one that comes built-in) does that hepl?
I have tried running with the stock kernel that comes with the image as well as the latest kernel from updates. Both of then are resulting in a kernel panic. Im not really sure how to proceed at this point.
If you want to track it down further, get whatever log information you can and file a bug in http://bugzilla.redhat.com/
Alternately or also, does the same thing happen on F18?
F18 ec2 images seem to be a lot more stable and I am going to switch development to these instead.
Thanks --Krishna
-- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ mattdm@fedoraproject.org _______________________________________________ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud
On Sat, Feb 02, 2013 at 05:32:33PM -0800, Krishna Raman wrote:
It looks like F18 suffers from the same problem. It might have something to do with CGroups or selinux. I will file a bug against Fedora.
Yes, please do, and post the link here. Thanks!