<!-- keep this as a security measure: #uncomment if the subject should only be modifiable by the listed groups # * Set ALLOWTOPICCHANGE = Main.TWikiAdminGroup,Main.CMSAdminGroup # * Set ALLOWTOPICRENAME = Main.TWikiAdminGroup,Main.CMSAdminGroup #uncomment this if you want the page only be viewable by the listed groups # * Set ALLOWTOPICVIEW = Main.TWikiAdminGroup,Main.CMSAdminGroup --> ---+!! %TOPIC% %TOC% ---++ Symptoms Summary: %FORMFIELD{"Symptom summary"}% <pre> <4>------------[ cut here ]------------ <2>kernel BUG at mm/truncate.c:489! <4>invalid opcode: 0000 [#1] SMP <4>last sysfs file: /sys/devices/system/cpu/online <4>CPU 13 <4>Modules linked in: fuse libafs(P)(U) autofs4 nfs lockd fscache auth_rpcgss nfs_acl sunrpc cpufreq_ondemand acpi_cpufreq freq_table mperf ipv6 ext2 xfs exportfs iTCO_wdt iTCO_vendor_support microcode raid1 power_meter acpi_ipmi ipmi_si ipmi_msghandler sg sb_edac edac_core joydev i2c_i801 lpc_ich mfd_core igb i2c_algo_bit i2c_core ioatdma ixgbe dca ptp pps_core mdio ext4 jbd2 mbcache raid10 sd_mod crc_t10dif mpt3sas scsi_transport_sas raid_class ahci wmi dm_mirror dm_region_hash dm_log dm_mod [last unloaded: scsi_wait_scan] <4> <4>Pid: 62449, comm: python Tainted: P -- ------------ 2.6.32-573.26.1.el6.x86_64 #1 DALCO AG S2600TPR/S2600TPR <4>RIP: 0010:[<ffffffff81140118>] [<ffffffff81140118>] invalidate_inode_pages2_range+0x388/0x3b0 <4>RSP: 0018:ffff881a5a8e7bb8 EFLAGS: 00010246 <4>RAX: 0000000000000000 RBX: ffffea001d891640 RCX: ffff8811179eb818 <4>RDX: ffff8811179eb818 RSI: ffff881a5a8e7a88 RDI: ffff881a5a8e7ac8 <4>RBP: ffff881a5a8e7c98 R08: 0000000000000000 R09: 0000000000000000 <4>R10: 0000000000000000 R11: 0000000000000064 R12: 0000000000000222 <4>R13: 000000000000000c R14: ffff881a5a8e7c60 R15: ffff881a5a8e9ae0 <4>FS: 00002abe77470d80(0000) GS:ffff880061fa0000(0000) knlGS:0000000000000000 <4>CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b <4>CR2: 00002abe79c50100 CR3: 000000124cf0f000 CR4: 00000000001407e0 <4>DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 <4>DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 <4>Process python (pid: 62449, threadinfo ffff881a5a8e4000, task ffff881386be7520) <4>Stack: <4> ffff881a5a8e99c0 ffff881a5a8e9af8 ffff881a5a8e7c00 0000000000000000 <4><d> 0000000000000001 ffffffffffffffff 000000000000000e 0000000000000000 <4><d> ffffea0034d0e350 ffffea0020fcadc8 ffffea002b871740 ffffea0015010db8 <4>Call Trace: <4> [<ffffffff81140157>] invalidate_inode_pages2+0x17/0x20 <4> [<ffffffffa0379e25>] fuse_finish_open+0xd5/0xe0 [fuse] <4> [<ffffffffa037a118>] fuse_open_common+0x78/0x80 [fuse] <4> [<ffffffffa037a120>] ? fuse_open+0x0/0x20 [fuse] <4> [<ffffffffa037a130>] fuse_open+0x10/0x20 [fuse] <4> [<ffffffff8118f1f2>] __dentry_open+0x122/0x380 <4> [<ffffffff812331af>] ? security_inode_permission+0x1f/0x30 <4> [<ffffffff8118f564>] nameidata_to_filp+0x54/0x70 <4> [<ffffffff811a5440>] do_filp_open+0x6d0/0xd20 <4> [<ffffffff810663f3>] ? perf_event_task_sched_out+0x33/0x70 <4> [<ffffffff8129e58a>] ? strncpy_from_user+0x4a/0x90 <4> [<ffffffff811b25f2>] ? alloc_fd+0x92/0x160 <4> [<ffffffff8118ef97>] do_sys_open+0x67/0x130 <4> [<ffffffff8118f0a0>] sys_open+0x20/0x30 <4> [<ffffffff8100b0d2>] system_call_fastpath+0x16/0x1b <4>Code: ff ff ff e9 81 fe ff ff 48 89 df e8 93 77 fe ff e9 d5 fd ff ff be cf 01 00 00 48 c7 c7 51 b1 7c 81 e8 5d 77 f3 ff e9 c9 fd ff ff <0f> 0b eb fe 48 89 df 90 e8 fb 51 01 00 e9 86 fe ff ff 0f 0b 0f <1>RIP [<ffffffff81140118>] invalidate_inode_pages2_range+0x388/0x3b0 <4> RSP <ffff881a5a8e7bb8> [root@t3wn51 127.0.0.1-2016-09-17-13:47:43]# </pre> ---++ Occurrences At what times did this problem occur (used to estimate frequency): | 2016-08-01 | | 2016-09-19 | | 2016-09-21 | ---++ Observations <!-- #collect here the information which may help to better understand the state of the system or services, e.g. #log excerpts, strace output, etc. #this also may help to identify the problem if similar conditions arise again --> ---++ Solution or Workaround Too much old kernel was running. ---++ Monitoring for this condition <!-- #how can this condition be recognized automatically, if at all? --> not yet
IssueForm
Affected Service
t3wn51
Symptom summary
t3wn51 reboots
Reason Understood
yes
Solution Exists
yes
Obsolete
yes
This topic: CmsTier3
>
WebHome
>
AdminArea
>
IssueT3WN51reboots
Topic revision: r2 - 2016-09-21 - FabioMartinelli
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki?
Send feedback