From: Marc-Christian Petersen <m.c.p@wolk-project.de>
To: "Alasdair McWilliam" <allymcw2000@hotmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Unresolved symbols of _mmx_memcpy in modules on an Athlon XP system
Date: Thu, 14 Aug 2003 04:46:45 +0200 [thread overview]
Message-ID: <200308140446.45208.m.c.p@wolk-project.de> (raw)
In-Reply-To: <LAW10-F56d2h2jXi2Qd0001e84d@hotmail.com>
[-- Attachment #1: Type: text/plain, Size: 575 bytes --]
On Thursday 14 August 2003 03:02, Alasdair McWilliam wrote:
Hi Alasdair,
> 1. PROBLEM: Unresolved symbols of _mmx_memcpy in modules on an Athlon XP
> 8. I've done research and found that people have been experiencing this
> problem from linux-2.4.0-test releases. Can someone please fix it?! Or
> point me to a patch that works? :( The server's running on a chunky kernel
> optimised for the old K6-II (i586).
urgs, for that long? surprising :)
Could you please try attached patch? Completely untested and just a guess.
Please report success/failure. Thanks
ciao, Marc
[-- Attachment #2: mmx_memcpy-fix.patch --]
[-- Type: text/x-diff, Size: 432 bytes --]
--- old/arch/i386/kernel/Makefile 2002-11-29 00:53:09.000000000 +0100
+++ wolk4/arch/i386/kernel/Makefile 2003-08-14 04:42:43.000000000 +0200
@@ -40,5 +40,6 @@ obj-$(CONFIG_SMP) += smp.o smpboot.o tr
obj-$(CONFIG_X86_LOCAL_APIC) += mpparse.o apic.o nmi.o
obj-$(CONFIG_X86_IO_APIC) += io_apic.o acpitable.o
obj-$(CONFIG_X86_VISWS_APIC) += visws_apic.o
+obj-$(CONFIG_X86_USE_3DNOW) += i386_ksyms.o
include $(TOPDIR)/Rules.make
next prev parent reply other threads:[~2003-08-14 2:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-14 1:02 PROBLEM: Unresolved symbols of _mmx_memcpy in modules on an Athlon XP system Alasdair McWilliam
2003-08-14 2:41 ` Otto Solares
2003-08-14 2:46 ` Marc-Christian Petersen [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-14 15:22 Alasdair McWilliam
2003-08-14 18:19 ` Otto Solares
2003-08-14 15:24 Alasdair McWilliam
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=200308140446.45208.m.c.p@wolk-project.de \
--to=m.c.p@wolk-project.de \
--cc=allymcw2000@hotmail.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