All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Andreas Hartmann <andihartmann@01019freenet.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.18.2] ide_core bug: kobject_add failed for ide ...
Date: Sun, 07 Jan 2007 14:05:00 -0500	[thread overview]
Message-ID: <1168196701.18788.69.camel@mindpipe> (raw)
In-Reply-To: <enrbhg$1m0$1@p54A18DCE.dip0.t-ipconnect.de>

On Sun, 2007-01-07 at 18:44 +0100, Andreas Hartmann wrote:
> Hello,
> 
> ide_core is loaded (while putting in an USB stick) as module the first
> time after reboot - all works fine. The USB stick got mounted and a ls
> is done to show the files on the root of the filesystem of the stick.
> Afterwards, the stick is securely removed from the system.
> Afterwards, ide_core is unloaded with rmmod (after usb-storage has been
> unloaded) - ok.
> 
> Next step is to load ide_core again. Now, the following error can be
> found in /var/log/messages:
> 
> 
> Jan  7 11:48:18 notebook1 kernel: Uniform Multi-Platform E-IDE driver
> Revision: 7.00alpha2
> Jan  7 11:48:18 notebook1 kernel: ide: Assuming 33MHz system bus speed
> for PIO modes; override with idebus=xx
> Jan  7 11:48:18 notebook1 kernel: kobject_add failed for ide with
> -EEXIST, don't try to register things with the same name in the same
> directory.

You seem to be running a SuSE kernel - please report the issue to them.

It's probably useful to repeat your test but run "find /sys/module >
sys1" before loading ide_core the first time, then "find /sys/module >
sys2" after "rmmod ide_core", and save the output of "diff sys1 sys2".

Lee



      reply	other threads:[~2007-01-07 19:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-07 17:44 [2.6.18.2] ide_core bug: kobject_add failed for ide Andreas Hartmann
2007-01-07 19:05 ` Lee Revell [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1168196701.18788.69.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=andihartmann@01019freenet.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.