[abrt] a crash has been detected again
I found Aleart [abrt] a crash has been detected again
Please provide solution and maybe root cuase.
abrt_version: 2.0.8
cmdline: ro root=UUID=582fdb4d-c526-410b-9a7d-f673d5ee140e nomodeset rd_NO_LUKS KEYBOARDTYPE=pc KEYTABLE=us LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=129M@0M rd_NO_LVM rd_NO_DM rhgb pcie_aspm=off biosdevname=0
event_log:
hostname: s1.egtmedia.net
kernel: 2.6.32-642.el6.x86_64
last_occurrence: 1478872976
machineid: sosreport_uploader-dmidecode=0de861102b39323ecd02c2ffd8278377633883a86fae288e36923173d40e911d
not-reportable: The backtrace does not contain enough meaningful function frames to be reported. It is annoying but it does not necessary signalize a problem with your computer. ABRT will not allow you to create a report in a bug tracking system but you can contact kernel maintainers via e-mail.
pkg_arch: x86_64
pkg_epoch: 0
pkg_fingerprint: 0946 FCA2 C105 B9DE
pkg_name: kernel
pkg_release: 642.el6
pkg_vendor: CentOS
pkg_version: 2.6.32
time: Sat 11 Jun 2016 12:04:38 AM AEST
uid: 0
username: root
sosreport.tar.xz: Binary file, 1492976 bytes
backtrace:
:WARNING: at fs/dcache.c:759 d_delete+0x250/0x2b0() (Not tainted)
:Hardware name: X9SCD
:Modules linked in: autofs4 ipv6 xt_multiport ipt_REJECT nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack iptable_filter ip_tables ext3 jbd ext2 ipmi_devintf ipmi_si ipmi_msghandler microcode iTCO_wdt iTCO_vendor_support joydev serio_raw i2c_i801 sg lpc_ich mfd_core igb dca i2c_algo_bit i2c_core ptp pps_core ext4 jbd2 mbcache sd_mod crc_t10dif ahci video output dm_mirror dm_region_hash dm_log dm_mod [last unloaded: speedstep_lib]
:Pid: 19944, comm: httpd Not tainted 2.6.32-642.el6.x86_64 #1
:Call Trace:
:[<ffffffff8107c911>] ? warn_slowpath_common+0x91/0xe0
:[<ffffffff8107c97a>] ? warn_slowpath_null+0x1a/0x20
:[<ffffffff811b6b10>] ? d_delete+0x250/0x2b0
:[<ffffffff811a8d48>] ? vfs_rmdir+0xe8/0xf0
:[<ffffffff811abf34>] ? do_rmdir+0x184/0x1f0
:[<ffffffff8119fbb6>] ? sys_newlstat+0x36/0x50
:[<ffffffff810ee687>] ? audit_syscall_entry+0x1d7/0x200
:[<ffffffff811abff6>] ? sys_rmdir+0x16/0x20
:[<ffffffff8100b0d2>] ? system_call_fastpath+0x16/0x1b
|
