Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 224221 - kobject_add failed for vcs1 with -EEXIST
Summary: kobject_add failed for vcs1 with -EEXIST
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 7
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2007-01-24 17:52 UTC by Nuno Dias
Modified: 2008-02-16 01:51 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-02-16 01:51:33 UTC

Attachments (Terms of Use)
dmesg with debug in udev.conf (deleted)
2007-01-24 17:52 UTC, Nuno Dias
no flags Details

Description Nuno Dias 2007-01-24 17:52:15 UTC
Description of problem:
Failed Starting udev

Version-Release number of selected component (if applicable):

How reproducible:
Boot the system

Steps to Reproduce:
1. Boot the system
Actual results:
Starting udev failed

Expected results:
Starting udev OK

Additional info: Addition information in attach file (dmesg) with debug enable
in udev.conf

Comment 1 Nuno Dias 2007-01-24 17:52:15 UTC
Created attachment 146427 [details]
dmesg with debug in udev.conf

Comment 2 Harald Hoyer 2007-08-24 10:27:56 UTC
is this still an issue?

Comment 3 Nuno Dias 2007-08-24 10:53:05 UTC
Yes, it is, with Fedora 7 the problem is the same.

Comment 4 Harald Hoyer 2007-08-24 11:20:42 UTC
kobject_add failed for vcs1 with -EEXIST, don't try to register things with the
same name in the same directory.

this is a kernel issue..

Comment 5 Christopher Brown 2008-01-09 00:06:00 UTC

I'm reviewing this bug as part of the kernel bug triage project, an attempt to
isolate current bugs in the Fedora kernel.

I am CC'ing myself to this bug and will try and assist you in resolving it if I can.

There hasn't been much activity on this bug for a while. Could you tell me if
you are still having problems with the latest kernel?

If the problem no longer exists then please close this bug or I'll do so in a
few days if there is no additional information lodged.

Comment 6 Christopher Brown 2008-02-16 01:51:33 UTC
Closing as per previous comment. Please re-open if this is still an issue for you.

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