[lkml]   [2007]   [May]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: STRANGE ERROR
    On Sun, 20 May 2007 00:30:55 +0200 "Sasa Ostrouska" <> wrote:

    > Hi everybody,
    > I tried today to upgrade the kernel to and i got the same
    > error during the boot time.
    > Here is the dmesg of the, 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.

    > 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

    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?


    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2007-05-20 01:39    [W:0.029 / U:30.808 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site