Jump to content
Welcome to our new Citrix community!
  • 0

Panic and restart of the XEN server 6.0.2


Aditya Malviya

Question

Dear Forum Members,

 

We are frequently getting the crash situation at our customer locations which leads to the abrupt restart of the servers.

 

Setup : XenServer 6.0.2

 

[2018-09-10 00:44:11] (XEN) 00000000d7fefca0 0000000000000000 0000000000000000 0000000000000000 
[2018-09-10 00:44:11] (XEN) 0000000000000000 ffff82c48022a524 0000000000000000 0000000000000000 
[2018-09-10 00:44:11] (XEN) 0000000000000000 0000000000000000 00000000d7fefca0 0000000000000005 
[2018-09-10 00:44:11] (XEN) Xen call trace: 
[2018-09-10 00:44:11] (XEN) [<ffff82c4801eb118>] mtc_paging_mark_dirty+0x1c8/0xfc0 
[2018-09-10 00:44:11] (XEN) [<ffff82c48010c713>] gnttab_copy+0x843/0x9d0 
[2018-09-10 00:44:11] (XEN) [<ffff82c480110042>] compat_grant_table_op+0x902/0xe40 
[2018-09-10 00:44:11] (XEN) [<ffff82c4801266a4>] timer_softirq_action+0x154/0x220 
[2018-09-10 00:44:11] (XEN) [<ffff82c48022a524>] compat_hypercall+0x74/0x80 
[2018-09-10 00:44:11] (XEN) 
[2018-09-10 00:44:11] (XEN) Pagetable walk from ffff82fffffff000: 
[2018-09-10 00:44:11] (XEN) L4[0x105] = 00000000bdac2027 5555555555555555 
[2018-09-10 00:44:11] (XEN) L3[0x1ff] = 0000000000000000 ffffffffffffffff 
[2018-09-10 00:44:11] (XEN) 
[2018-09-10 00:44:11] (XEN) **************************************** 
[2018-09-10 00:44:11] (XEN) Panic on CPU 0: 
[2018-09-10 00:44:11] (XEN) FATAL PAGE FAULT 
[2018-09-10 00:44:11] (XEN) [error_code=0000] 
[2018-09-10 00:44:11] (XEN) Faulting linear address: ffff82fffffff000 
[2018-09-10 00:44:11] (XEN) **************************************** 
[2018-09-10 00:44:11] (XEN) 
[2018-09-10 00:44:11] (XEN) Reboot in five seconds... 

 

Is it a known situation for the citrix. Does citrix have any solution for this ?

 

 

Regards,

Aditya

Link to comment

2 answers to this question

Recommended Posts

  • 0

Page faults are usually due to bad (faulty) memory, which results in serious errors; if you can, do a full POST and set your BIOS to check all your memory. If you can identify the bad module. replace it.

It looks to me that it has nothing to do with XS, itself. That said, please consider upgrading XS to a newer, more secure version.

 

-=Tobias

Link to comment
  • 0

6.0.2 is completely unsupported, its going to be difficult to find any resolution if its software related

at this point. Be sure you have good backups of your VM's and if you think your hardware can 

support 7.x then upgrade. 7.1 LTSR if you are going to license or 8.0 if you are going to run free and

upgrade on demand as each new version is released. You probably should consider a hardware 

refresh as well. 

 

--Alan--

 

 

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...