mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Avuton Olrich" <avuton@gmail.com>
To: LMKL <linux-kernel@vger.kernel.org>
Subject: Device does not have a release() function
Date: Sat, 30 Dec 2006 16:12:05 -0800	[thread overview]
Message-ID: <3aa654a40612301612g4702e2cs4fba5151170183b@mail.gmail.com> (raw)

Please excuse me if this has already been discussed. Anything else
that's needed please let me know.

kernel: Linux version 2.6.20-rc2 (sbh@rocket) (gcc version 4.1.1
(Gentoo 4.1.1-r3)) #6 SMP PREEMPT Thu Dec 28 21:07:58 PST 2006

Spotted this in the dmesg:

---
Fixed PHY: Registered new driver
driver_bound: device fixed@100:1 already bound
Device 'fixed@100:1' does not have a release() function, it is broken
and must be fixed.
WARNING at /usr/src/linux-stable/drivers/base/core.c:104 device_release()
 [<c027bbf9>] kobject_cleanup+0x49/0x90
 [<c027bc40>] kobject_release+0x0/0x10
 [<c027c8ea>] kref_put+0x2a/0xa0
 [<c05762bc>] fixed_init+0x1bc/0x210
 [<c01003f0>] init+0x70/0x2a0
 [<c0102f82>] ret_from_fork+0x6/0x1c
 [<c0100380>] init+0x0/0x2a0
 [<c0100380>] init+0x0/0x2a0
 [<c0103c73>] kernel_thread_helper+0x7/0x14
 =======================
---

Sorry for all the links, but it's about 80K of info:

http://avuton.googlepages.com/config.txt
http://avuton.googlepages.com/cpuinfo.txt
http://avuton.googlepages.com/dmesg.txt
http://avuton.googlepages.com/lspci-vvv.txt
http://avuton.googlepages.com/proc-iomem.txt
http://avuton.googlepages.com/proc-ioports.txt
http://avuton.googlepages.com/ver_linux.txt
-- 
avuton
--
 Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

             reply	other threads:[~2006-12-31  0:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-31  0:12 Avuton Olrich [this message]
2007-01-02 11:04 ` Vitaly Bordug
2007-01-02 14:50   ` Avuton Olrich

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=3aa654a40612301612g4702e2cs4fba5151170183b@mail.gmail.com \
    --to=avuton@gmail.com \
    --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 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®