mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Donald Duckie <schipperke2000@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: unresolved symbol __udivsi3_i4
Date: Thu, 23 Sep 2004 19:59:17 -0700	[thread overview]
Message-ID: <20040923195917.26089252.rddunlap@osdl.org> (raw)
In-Reply-To: <20040924021050.689.qmail@web53608.mail.yahoo.com>

On Thu, 23 Sep 2004 19:10:50 -0700 (PDT) Donald Duckie wrote:

| hi!

Hi again, Donald-

Note:  I haven't forgotten your other question.
Is is still a problem?

| can somebody please help me how to overcome this
| problem:
| unresolved symbol __udivsi3_i4

That clearly shouldn't be happening, and that symbol isn't in
snull.o when I build it (on x86).

| I compiled the snull files that i got from 
| http://www.oreilly.com.tw/editor_column/a138_read.htmland
| ran depmod -a -F /proc/ksyms 2.4.18 snull.o

How did you build snull (or all of the LDD drivers)?
What command(s)?

| And in another machine (my running machine), I got the
| following files from my compilation machine:
| snull.o
| /lib/modules/2.4.18/*
| 
| In my running machine, I ran modprobe but got this
| error:
| Using /lib/modules/2.4.18-sh/kernel/drivers/net/snull.
|   <cut>
| modprobe: unresolved symbol __udivsi3_i4
|   <cut>

So the problem machine is an sh-arch machine?
Maybe gcc 3.0.3 has some problem on sh.
Can you try this on some other architecture machine?

| The gcc version that is used is:
| [aprhodite@aphrodite2 bin]$ sh-linux-gcc -v
| Reading specs from
| /usr/lib/gcc-lib/sh-linux/3.0.3/specs
| Configured with: ../configure --prefix=/usr
| --mandir=/usr/share/man --target=sh-linux
| --host=i686-pc-linux-gnu --build=i
| 686-pc-linux-gnu --disable-c99 --disable-nls
| --enable-languages=c,c++ --with-system-zlib
| --with-gxx-include-dir=/usr/sh-
| linux/include/g++-v3
| --includedir=/usr/sh-linux/include
| --enable-threads=posix --enable-long-long
| Thread model: posix
| gcc version 3.0.3
| 
| 
| Running nm -l-s snull.o
| 00000000 a *ABS*
|   <cut>
|          U __udivsi3_i4
| /home/aphrodite/snull/snull3/snull/snull.c:355
|   <cut>

Seeing an objdump of that function (snull_hw_tx) should/could be helpful.

| the block in snull.c that contains ine 355 is:
|     352     if (lockup && ((priv->stats.tx_packets +
| 1) % lockup) == 0) {
|     353         /* Simulate a dropped transmit
| interrupt */
|     354         netif_stop_queue(dev);
|     355         PDEBUG("Simulate lockup at %ld, txp
| %ld\n", jiffies,
|     356                         (unsigned long)
| priv->stats.tx_packets);
|     357     }
| (which seems to  be okey)

Yes.

| The only modification to the downloaded snull files is
| on snull.c:
|      30 //#include <linux/malloc.h> /* kmalloc() */
|      31 #include <linux/slab.h> /* kmalloc()
| deprecated use slab.h instead*/
| 
| 
| can anyone please tell me how to deal with this
| unresolved symbol __udivsi3_i4?


--
~Randy

  reply	other threads:[~2004-09-24  3:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-24  2:10 Donald Duckie
2004-09-24  2:59 ` Randy.Dunlap [this message]
2004-09-24  3:23 ` Randy.Dunlap
2004-09-24  4:49   ` Donald Duckie
2004-09-24 23:14     ` Randy.Dunlap
2004-09-24  6:01 ` Paweł Sikora
2004-09-24  8:33   ` Geert Uytterhoeven
2004-09-24 10:52     ` Jan-Benedict Glaw
2004-09-24 11:15       ` Geert Uytterhoeven
2004-09-24 11:29         ` Jan-Benedict Glaw
2004-09-24 12:49           ` Andreas Schwab

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=20040923195917.26089252.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schipperke2000@yahoo.com \
    /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®