kernel: WARNING: at fs/sysfs/dir.c:536 sysfs_add_one+0xbb/0xe0
Hi all,
Please help me to find the root cause of the below warning:
kernel: WARNING: at fs/sysfs/dir.c:536 sysfs_add_one+0xbb/0xe0
Here is the whole log:
May 2 18:23:16 npascors2n1 kernel: WARNING: at fs/sysfs/dir.c:536 sysfs_add_one+0xbb/0xe0()
May 2 18:23:16 npascors2n1 kernel: Hardware name: VMware7,1
May 2 18:23:16 npascors2n1 kernel: sysfs: cannot create duplicate filename '/firmware/efi/vars/dump-type2-0-0-1493749396-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0'
May 2 18:23:16 npascors2n1 kernel: Modules linked in: vmw_vsock_vmci_transport vsock oracleasm autofs4 ipv6 vfat fat uinput vmw_balloon coretemp crc32c_intel ghash_clmulni_intel microcode pcspkr sg ixgbe hwmon dca vmw_vmci i2c_piix4 shpchp ext4 jbd2 mbcache dm_round_robin scsi_dh_emc sd_mod crc_t10dif sr_mod cdrom aesni_intel ablk_helper cryptd lrw aes_x86_64 xts gf128mul vmxnet3 qla2xxx scsi_transport_fc scsi_tgt mptspi mptscsih mptbase scsi_transport_spi pata_acpi ata_generic ata_piix vmwgfx ttm drm i2c_core dm_multipath dm_mirror dm_region_hash dm_log dm_mod scsi_dh_alua [last unloaded: speedstep_lib]
May 2 18:23:16 npascors2n1 kernel: Pid: 5934, comm: kworker/60:2 Tainted: G W 3.8.13-16.2.1.el6uek.x86_64 #1
May 2 18:23:16 npascors2n1 kernel: Call Trace:
May 2 18:23:16 npascors2n1 kernel: [] warn_slowpath_common+0x7f/0xc0
May 2 18:23:16 npascors2n1 kernel: [] warn_slowpath_fmt+0x46/0x50
May 2 18:23:16 npascors2n1 kernel: [] ? strlcat+0x69/0x80
May 2 18:23:16 npascors2n1 kernel: [] sysfs_add_one+0xbb/0xe0
May 2 18:23:16 npascors2n1 kernel: [] create_dir+0x82/0xe0
May 2 18:23:16 npascors2n1 kernel: [] sysfs_create_dir+0x8a/0xf0
May 2 18:23:16 npascors2n1 kernel: [] kobject_add_internal+0xaa/0x260
May 2 18:23:16 npascors2n1 kernel: [] kobject_add_varg+0x38/0x60
May 2 18:23:16 npascors2n1 kernel: [] kobject_init_and_add+0x53/0x70
Responses
You have an UEFI-style system, and your kernel includes a CONFIG_EFI_VARS_PSTORE feature, and a feature that dumps kernel message log (= the "dmesg" command output) into UEFI variables for persistent storage if the system is crashing (or even if the system is working normally, depending on the options chosen).
The system is trying to add a dump variable, but another variable with the same name already exists (i.e. you haven't deleted a previous dump).
The space available for the UEFI variables is fairly limited, so you probably should delete the /sys/firmware/efi/vars/dump-type2-* variables as soon as you have saved the dump data somewhere else. Some buggy UEFI firmware implementations react badly to the variable space filling up: according to the Internet, some physical systems have even been bricked in such a situation. But since you have a virtual machine, this is probably not a risk for you.
You're also using Oracle Unbreakable Enterprise Kernel, so any paid support for this issue should come from Oracle.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
