From: Vitaly Bordug <vbordug@ru.mvista.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Sasa Ostrouska <casaxa@gmail.com>,
linux-kernel@vger.kernel.org, Jeff Garzik <jeff@garzik.org>,
netdev@vger.kernel.org
Subject: Re: STRANGE ERROR
Date: Sun, 20 May 2007 20:51:24 +0400 [thread overview]
Message-ID: <20070520165124.GA12025@server.dev.rtsoft.ru> (raw)
In-Reply-To: <20070519163402.b087b9d7.akpm@linux-foundation.org>
On Sat, May 19, 2007 at 16:34 -0700, Andrew Morton wrote:
> On Sun, 20 May 2007 00:30:55 +0200 "Sasa Ostrouska" <casaxa@gmail.com> wrote:
>
> > Hi everybody,
> >
> > I tried today to upgrade the kernel to 2.6.21.1 and i got the same
> > error during the boot time.
> > Here is the dmesg of the 2.6.20.2, can somebody tell me what this is ?
> >
> > ...
> >
> > Marvell 88E1101: Registered new driver
> > Fixed PHY: Registered new driver
> > driver_bound: device fixed@100:1 already bound
>
> I don't know what caused that one.
>
this is because of issue in fixed phy driver initialisation
- have a patch but need to test it a bit more.
> > Device 'fixed@100:1' does not have a release() function, it is broken
> > and must be fixed.
> > BUG: at drivers/base/core.c:104 device_release()
> >
> > Call Trace:
> > [<ffffffff802ec380>] kobject_cleanup+0x53/0x7e
> > [<ffffffff802ec3ab>] kobject_release+0x0/0x9
> > [<ffffffff802ecf3f>] kref_put+0x74/0x81
> > [<ffffffff8035493b>] fixed_mdio_register_device+0x230/0x265
> > [<ffffffff80564d31>] fixed_init+0x1f/0x35
> > [<ffffffff802071a4>] init+0x147/0x2fb
> > [<ffffffff80223b6e>] schedule_tail+0x36/0x92
> > [<ffffffff8020a678>] child_rip+0xa/0x12
> > [<ffffffff80311714>] acpi_ds_init_one_object+0x0/0x83
> > [<ffffffff8020705d>] init+0x0/0x2fb
> > [<ffffffff8020a66e>] child_rip+0x0/0x12
>
> This appears to have happened because fixed_mdio_register_device() (or
> phy_device_create) didn't suitably initialise phy_device.dev.
>
> But I don't immediately see why this doesn't affect all phy drivers.
> Presumably it's the fixed driver which is at fault. Jeff, how is this
> supposed to work?
>
the fixed phy used to have "specific" bus bound stuff
but I've reworked this point.
prev parent reply other threads:[~2007-05-20 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <dcf706c60705191530x5a78f9aewbb520a97ad516f6d@mail.gmail.com>
2007-05-19 23:34 ` STRANGE ERROR Andrew Morton
2007-05-20 16:51 ` Vitaly Bordug [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=20070520165124.GA12025@server.dev.rtsoft.ru \
--to=vbordug@ru.mvista.com \
--cc=akpm@linux-foundation.org \
--cc=casaxa@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).