Bug 742673

Summary: sysfs: cannot create duplicate filename '/devices/platform/GHES.9' message during boot
Product: Red Hat Enterprise Linux 6 Reporter: Marcin Garski <mgarski>
Component: kernelAssignee: Red Hat Kernel Manager <kernel-mgr>
Status: CLOSED DUPLICATE QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.1CC: atodorov
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-05 05:07:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 767187    

Description Marcin Garski 2011-10-01 09:03:24 UTC
Description of problem:
Update kernel from 2.6.32-71.29.1.el6 to 2.6.32-131.12.1.el6 caused that below message appear in boot logs.

Version-Release number of selected component (if applicable):
CentOS 6.0 with Continuous Release ( CR ) repository
kernel 2.6.32-131.12.1.el6.x86_64
  
Actual results:
------------[ cut here ]------------
WARNING: at fs/sysfs/dir.c:491 sysfs_add_one+0xc9/0x130() (Not tainted)
Hardware name: PRIMERGY TX100 S2
sysfs: cannot create duplicate filename '/devices/platform/GHES.9'
Modules linked in:
Pid: 1, comm: swapper Not tainted 2.6.32-131.12.1.el6.x86_64 #1
Call Trace:
 [<ffffffff810670f7>] ? warn_slowpath_common+0x87/0xc0
 [<ffffffff810671e6>] ? warn_slowpath_fmt+0x46/0x50
 [<ffffffff811e7149>] ? sysfs_add_one+0xc9/0x130
 [<ffffffff811e7218>] ? create_dir+0x68/0xb0
 [<ffffffff811e7299>] ? sysfs_create_dir+0x39/0x50
 [<ffffffff812651e9>] ? kobject_add_internal+0xb9/0x260
 [<ffffffff81265498>] ? kobject_add_varg+0x38/0x60
 [<ffffffff81265574>] ? kobject_add+0x44/0x70
 [<ffffffff8126501a>] ? kobject_get+0x1a/0x30
 [<ffffffff81338379>] ? device_add+0xc9/0x640
 [<ffffffff813373e1>] ? dev_set_name+0x41/0x50
 [<ffffffff8133d5c5>] ? platform_device_add+0x125/0x200
 [<ffffffff81c510ac>] ? hest_parse_ghes+0x0/0x8a
 [<ffffffff81c51104>] ? hest_parse_ghes+0x58/0x8a
 [<ffffffff812eb0bf>] ? apei_hest_parse+0x9f/0x140
 [<ffffffff81c51218>] ? hest_init+0xe2/0x138
 [<ffffffff81c51136>] ? hest_init+0x0/0x138
 [<ffffffff8100204c>] ? do_one_initcall+0x3c/0x1d0
 [<ffffffff81c1d884>] ? kernel_init+0x29d/0x2f9
 [<ffffffff8100c1ca>] ? child_rip+0xa/0x20
 [<ffffffff81c1d5e7>] ? kernel_init+0x0/0x2f9
 [<ffffffff8100c1c0>] ? child_rip+0x0/0x20
---[ end trace a22d306b065d4a66 ]---
kobject_add_internal failed for GHES.9 with -EEXIST, don't try to register things with the same name in the same directory.
Pid: 1, comm: swapper Tainted: G        W  ----------------   2.6.32-131.12.1.el6.x86_64 #1
Call Trace:
 [<ffffffff8126528d>] ? kobject_add_internal+0x15d/0x260
 [<ffffffff81265498>] ? kobject_add_varg+0x38/0x60
 [<ffffffff81265574>] ? kobject_add+0x44/0x70
 [<ffffffff8126501a>] ? kobject_get+0x1a/0x30
 [<ffffffff81338379>] ? device_add+0xc9/0x640
 [<ffffffff813373e1>] ? dev_set_name+0x41/0x50
 [<ffffffff8133d5c5>] ? platform_device_add+0x125/0x200
 [<ffffffff81c510ac>] ? hest_parse_ghes+0x0/0x8a
 [<ffffffff81c51104>] ? hest_parse_ghes+0x58/0x8a
 [<ffffffff812eb0bf>] ? apei_hest_parse+0x9f/0x140
 [<ffffffff81c51218>] ? hest_init+0xe2/0x138
 [<ffffffff81c51136>] ? hest_init+0x0/0x138
 [<ffffffff8100204c>] ? do_one_initcall+0x3c/0x1d0
 [<ffffffff81c1d884>] ? kernel_init+0x29d/0x2f9
 [<ffffffff8100c1ca>] ? child_rip+0xa/0x20
 [<ffffffff81c1d5e7>] ? kernel_init+0x0/0x2f9
 [<ffffffff8100c1c0>] ? child_rip+0x0/0x20

Additional info:
Probably patch (if this is the same bug): https://lkml.org/lkml/2010/9/2/52

Comment 2 RHEL Program Management 2011-10-07 15:52:35 UTC
Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 3 Alexander Todorov 2011-11-02 09:41:28 UTC
Same issue on RHEL 6.1 on TX 100 S1

architecture: i686
cmdline: not_applicable
component: kernel
executable: kernel
kernel: 2.6.32-131.0.15.el6.i686
package: kernel
reason: WARNING: at fs/sysfs/dir.c:491 sysfs_add_one+0xb1/0x110() (Not tainted)
release: Red Hat Enterprise Linux Workstation release 6.1 (Santiago)
sosreport.tar.xz: /var/spool/abrt/kerneloops-1319806341-6122-1/sosreport.tar.xz
time: 1320224423
uid: 0

backtrace
-----
WARNING: at fs/sysfs/dir.c:491 sysfs_add_one+0xb1/0x110() (Not tainted)
Hardware name: PRIMERGY TX100 S1             
sysfs: cannot create duplicate filename '/devices/platform/GHES.9'
Modules linked in:
Pid: 1, comm: swapper Not tainted 2.6.32-131.0.15.el6.i686 #1
Call Trace:
[<c0452a31>] ? warn_slowpath_common+0x81/0xc0
[<c0585051>] ? sysfs_add_one+0xb1/0x110
[<c0585051>] ? sysfs_add_one+0xb1/0x110
[<c0452b03>] ? warn_slowpath_fmt+0x33/0x40
[<c0585051>] ? sysfs_add_one+0xb1/0x110
[<c05850f8>] ? create_dir+0x48/0x90
[<c0585169>] ? sysfs_create_dir+0x29/0x40
[<c05f1d3f>] ? kobject_get+0xf/0x20
[<c05f1e9b>] ? kobject_add_internal+0x9b/0x250
[<c051a280>] ? kmem_cache_alloc_notrace+0xa0/0xb0
[<c05f21cd>] ? kobject_add+0x2d/0x60
[<c06afcf3>] ? device_add+0xa3/0x5f0
[<c06b442c>] ? platform_device_add+0xfc/0x1e0
[<c0a8bb5b>] ? hest_parse_ghes+0x49/0x73
[<c06686a7>] ? apei_hest_parse+0x77/0x100
[<c0a8bc3a>] ? hest_init+0xb5/0x119
[<c0a8bb12>] ? hest_parse_ghes+0x0/0x73
[<c0a8bb85>] ? hest_init+0x0/0x119
[<c0a8bc50>] ? hest_init+0xcb/0x119
[<c0a8af17>] ? dock_init+0x0/0x79
[<c040303f>] ? do_one_initcall+0x2f/0x1c0
[<c0a603f3>] ? kernel_init+0x1df/0x235
[<c0a60214>] ? kernel_init+0x0/0x235
[<c040a03f>] ? kernel_thread_helper+0x7/0x10

Comment 4 Linda Wang 2011-12-05 05:07:43 UTC

*** This bug has been marked as a duplicate of bug 693830 ***

Comment 5 Marcin Garski 2011-12-12 22:44:29 UTC
Could you give me more information, as I'm "not authorized to access bug #693830." and I see that bug is "CLOSED WORKSFORME" but I still see this message (kernel 2.6.32-131.21.1.el6.x86_64), Alexander also confirmed bug. So I don't know what to do?