From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: Vasil Kolev <vasil@ludost.net>,
linux-kernel@vger.kernel.org, andre@linux-ide.org,
frankt@promise.com, linux-ide@vger.kernel.org
Subject: Re: kobject_register failed for Promise_Old_IDE (-17)
Date: Tue, 24 Jan 2006 23:58:11 +0100 [thread overview]
Message-ID: <58cb370e0601241458y6cdf702ey9caa261702a7948a@mail.gmail.com> (raw)
In-Reply-To: <20060124223527.GA26337@kroah.com>
On 1/24/06, Greg KH <greg@kroah.com> wrote:
> On Tue, Jan 24, 2006 at 11:08:47AM +0200, Vasil Kolev wrote:
> > Hello,
> > I have a machine that's currently running 2.4.28 with the promise_old
> > driver, which runs ok. I tried upgrading it last night to 2.6.15, and
> > the following error occured, and no drives were detected/made available:
> >
> > [17179598.940000] kobject_register failed for Promise_Old_IDE (-17)
> > [17179598.940000] [dump_stack+21/23] dump_stack+0x15/0x17
> > [17179598.940000] [kobject_register+52/64] kobject_register+0x34/0x40
> > [17179598.940000] [bus_add_driver+69/163] bus_add_driver+0x45/0xa3
> > [17179598.940000] [driver_register+57/60] driver_register+0x39/0x3c
> > [17179598.940000] [__pci_register_driver+125/132] __pci_register_driver+0x7d/0x84
> > [17179598.940000] [__ide_pci_register_driver+19/53] __ide_pci_register_driver+0x13/0x35
> > [17179598.940000] [pg0+945449588/1069855744] pdc202xx_ide_init+0x12/0x16 [pdc202xx_old]
> > [17179598.940000] [sys_init_module+193/430] sys_init_module+0xc1/0x1ae
> > [17179598.940000] [syscall_call+7/11] syscall_call+0x7/0xb
>
> This means that some other driver tried to register with the same exact
> name for the same bus. As it looks like this is the ide bus, I suggest
> asking on the linux ide mailing list.
I don't see a way how this can happen. There is only one driver with
.name = "Promise_Old_IDE" and code dealing with driver registration
looks more or less sane (+ hasn't been changed recently except
.owner fixes).
Vasil, are you using vanilla 2.6.15 without any distro etc patches?
[ just to be 100% sure ]
Could you send dmesg command output?
Bartlomiej
next prev parent reply other threads:[~2006-01-24 22:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 9:08 Vasil Kolev
2006-01-24 22:35 ` Greg KH
2006-01-24 22:58 ` Bartlomiej Zolnierkiewicz [this message]
2006-01-25 7:54 ` Vasil Kolev
[not found] ` <58cb370e0601250157n17e113d2p683cb287107efea7@mail.gmail.com>
2006-01-25 10:12 ` Vasil Kolev
2006-01-26 23:01 ` Adrian Bunk
2006-01-26 23:21 ` Greg KH
2006-01-26 23:48 ` Adrian Bunk
2006-01-27 18:58 ` Greg KH
2006-01-26 23:56 ` Bartlomiej Zolnierkiewicz
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=58cb370e0601241458y6cdf702ey9caa261702a7948a@mail.gmail.com \
--to=bzolnier@gmail.com \
--cc=andre@linux-ide.org \
--cc=frankt@promise.com \
--cc=greg@kroah.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vasil@ludost.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®