Bug 242788 - kobject_add failed for vcs7, vcsa7 with -EEXIST
kobject_add failed for vcs7, vcsa7 with -EEXIST
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
rawhide
All Linux
low Severity medium
: ---
: ---
Assigned To: Kernel Maintainer List
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-06-05 15:28 EDT by James
Modified: 2008-02-11 14:08 EST (History)
0 users

See Also:
Fixed In Version: 2.6.22
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-02-11 14:05:02 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description James 2007-06-05 15:28:28 EDT
Description of problem:
Error message and backtrace found in system logs (see below).

Version-Release number of selected component (if applicable):
kernel 2.6.20-1.2952.fc6

How reproducible:
Not entirely known. This appeared to happen in conjuction with an X.org
i810/Xv/I830WaitLpRing crash,
  
Actual results:

Jun  5 19:48:03 harmony kernel: kobject_add failed for vcs7 with -EEXIST, don't
try to register things with the same name in the same directory.
Jun  5 19:48:03 harmony kernel:  [<c04e98af>] kobject_add+0x165/0x18e
Jun  5 19:48:03 harmony kernel:  [<c04e9a69>] kobject_set_name+0x2b/0x92
Jun  5 19:48:03 harmony kernel:  [<c0557097>] device_add+0x8b/0x49c
Jun  5 19:48:03 harmony kernel:  [<c04378e6>] init_waitqueue_head+0x12/0x20
Jun  5 19:48:03 harmony kernel:  [<c0557532>] device_create+0x7a/0x9a
Jun  5 19:48:03 harmony kernel:  [<c053ced4>] vcs_make_sysfs+0x34/0x6e
Jun  5 19:48:03 harmony kernel:  [<c0541d0b>] con_open+0x6f/0x7c
Jun  5 19:48:03 harmony kernel:  [<c05387b4>] tty_open+0x175/0x2b4
Jun  5 19:48:03 harmony kernel:  [<c04748d4>] chrdev_open+0xf7/0x12b
Jun  5 19:48:03 harmony kernel:  [<c04747dd>] chrdev_open+0x0/0x12b
Jun  5 19:48:03 harmony kernel:  [<c0470ff4>] __dentry_open+0xc3/0x17a
Jun  5 19:48:03 harmony kernel:  [<c0471125>] nameidata_to_filp+0x24/0x33
Jun  5 19:48:03 harmony kernel:  [<c0471166>] do_filp_open+0x32/0x39
Jun  5 19:48:03 harmony kernel:  [<c0470f27>] get_unused_fd+0xb3/0xbd
Jun  5 19:48:03 harmony kernel:  [<c04711af>] do_sys_open+0x42/0xbe
Jun  5 19:48:03 harmony kernel:  [<c0471264>] sys_open+0x1c/0x1e
Jun  5 19:48:03 harmony kernel:  [<c0403f64>] syscall_call+0x7/0xb
Jun  5 19:48:03 harmony kernel:  [<c0620033>] rt_mutex_slowlock+0x251/0x44f
Jun  5 19:48:03 harmony kernel:  =======================
Jun  5 19:48:03 harmony kernel: kobject_add failed for vcsa7 with -EEXIST, don't
try to register things with the same name in the same directory.
Jun  5 19:48:03 harmony kernel:  [<c04e98af>] kobject_add+0x165/0x18e
Jun  5 19:48:03 harmony kernel:  [<c04e9a69>] kobject_set_name+0x2b/0x92
Jun  5 19:48:03 harmony kernel:  [<c0557097>] device_add+0x8b/0x49c
Jun  5 19:48:03 harmony kernel:  [<c04378e6>] init_waitqueue_head+0x12/0x20
Jun  5 19:48:03 harmony kernel:  [<c0557532>] device_create+0x7a/0x9a
Jun  5 19:48:03 harmony kernel:  [<c053cf09>] vcs_make_sysfs+0x69/0x6e
Jun  5 19:48:03 harmony kernel:  [<c0541d0b>] con_open+0x6f/0x7c
Jun  5 19:48:04 harmony kernel:  [<c05387b4>] tty_open+0x175/0x2b4
Jun  5 19:48:04 harmony kernel:  [<c04748d4>] chrdev_open+0xf7/0x12b
Jun  5 19:48:04 harmony kernel:  [<c04747dd>] chrdev_open+0x0/0x12b
Jun  5 19:48:04 harmony kernel:  [<c0470ff4>] __dentry_open+0xc3/0x17a
Jun  5 19:48:04 harmony kernel:  [<c0471125>] nameidata_to_filp+0x24/0x33
Jun  5 19:48:04 harmony kernel:  [<c0471166>] do_filp_open+0x32/0x39
Jun  5 19:48:04 harmony kernel:  [<c0470f27>] get_unused_fd+0xb3/0xbd
Jun  5 19:48:04 harmony kernel:  [<c04711af>] do_sys_open+0x42/0xbe
Jun  5 19:48:04 harmony kernel:  [<c0471264>] sys_open+0x1c/0x1e
Jun  5 19:48:04 harmony kernel:  [<c0403f64>] syscall_call+0x7/0xb
Jun  5 19:48:04 harmony kernel:  [<c0620033>] rt_mutex_slowlock+0x251/0x44f
Jun  5 19:48:04 harmony kernel:  =======================

Expected results:
No such messages (and no X.org crashes?).

Note You need to log in before you can comment on or make changes to this bug.