public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: "Ph. Marek" <marek@mail.bmlv.gv.at>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.[01] and duron - unresolved symbol _mmx_memcpy
Date: Mon, 12 Feb 2001 19:49:36 +1100	[thread overview]
Message-ID: <22453.981967776@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Mon, 12 Feb 2001 08:04:59 BST." <3.0.6.32.20010212080459.0090ce80@pop3.bmlv.gv.at>

On Mon, 12 Feb 2001 08:04:59 +0100, 
"Ph. Marek" <marek@mail.bmlv.gv.at> wrote:
>Some time ago I tried 2.4.0 compiled with option for duron-processors,
>yesterday I tried 2.4.1; both give problems on insmod/modprobe with some
>modules, eg. tulip.
>
>The offending function is _mmx_memcpy

I need the output from these commands on a running 2.4.x kernel
compiled for duron.

grep _mmx_memcpy /proc/ksyms
strings -a `/sbin/modprobe -l '*tulip*'` | grep _mmx_memcpy

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-02-12  8:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-12  7:04 2.4.[01] and duron - unresolved symbol _mmx_memcpy Ph. Marek
2001-02-12  8:49 ` Keith Owens [this message]
     [not found]   ` <Your message of "Mon, 12 Feb 2001 08:04:59 BST."             <3.0.6.32.20010212080459.0090ce80@pop3.bmlv.gv.at>
2001-02-13  6:47     ` Ph. Marek
2001-02-13  7:23       ` Keith Owens
2001-02-12  9:54 ` Jan Niehusmann

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=22453.981967776@ocs3.ocs-net \
    --to=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marek@mail.bmlv.gv.at \
    /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