From: Alan Chandler <alan@chandlerfamily.org.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: Unresolved symbol hotplug_path in usbcore.o as a module (2.4.12)
Date: Sat, 20 Oct 2001 08:12:14 +0100 [thread overview]
Message-ID: <E15uqJ1-0008Mq-01@roo.home> (raw)
In-Reply-To: <28682.1003560517@ocs3.intra.ocs.com.au>
In-Reply-To: <28682.1003560517@ocs3.intra.ocs.com.au>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Saturday 20 October 2001 7:48 am, Keith Owens wrote:
> On Fri, 19 Oct 2001 20:21:17 +0100,
>
> Alan Chandler <alan@chandlerfamily.org.uk> wrote:
> >I have built the the 2.4.12 kernel with CONFIG_HOTPLUG set and the usb
> > stuff all compiled as modules.
> >
> >depmod -e shows that usbcore.o has an unresolved symbol (which of course
> >fails when the module tries to load) of hot_plug path.
>
> I need the output from
> nm -A `/sbin/modprobe -l` | grep hotplug_path
alan@kanger:~$ nm -A `/sbin/modprobe -l` | grep hotplug_path
/lib/modules/2.4.12/kernel/drivers/usb/usbcore.o: U hotplug_path
alan@kanger:~$
> grep hotplug_path /proc/ksyms System.map
alan@kanger:/$ grep hotplug_path /proc/ksyms System.map
/proc/ksyms:c0290960 hotplug_path_R__ver_hotplug_path
System.map:c02810a0 ? __kstrtab_hotplug_path
System.map:c028bb98 ? __ksymtab_hotplug_path
System.map:c0290960 D hotplug_path
alan@kanger:/$
- --
Alan - alan@chandlerfamily.org.uk
http://www.chandlerfamily.org.uk
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE70SPa1mf3M5ZDr2kRAkb6AJ0eyEL3EDiCdrrZdNGeT5utXP+rRwCgzaDY
MkVDEVYXdsfCWrin8w30w0M=
=qjMd
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2001-10-20 7:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-19 19:21 Alan Chandler
2001-10-20 6:48 ` Keith Owens
2001-10-20 7:12 ` Alan Chandler [this message]
2001-10-20 7:25 ` Keith Owens
2001-10-20 19:52 ` Alan Chandler
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=E15uqJ1-0008Mq-01@roo.home \
--to=alan@chandlerfamily.org.uk \
--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®