From: Phil Stracchino <alaric@babcom.com>
To: linux-kernel@vger.kernel.org
Cc: alaric@babcom.com
Subject: FOLLOWUP: Kernel 2.4.19 does not export _mmx_memcpy when compiled with gcc-3.2 and Athlon optimizations
Date: Wed, 4 Sep 2002 14:48:54 -0400 [thread overview]
Message-ID: <20020904184854.GA9141@babylon5.babcom.com> (raw)
In-Reply-To: <20020904181952.GA1158@babylon5.babcom.com>
FOLLOWUP:
I built a K6-optimized kernel and manually turned on CONFIG_X86_USE_3DNOW
before beginning compilation, installed the kernel, and ran depmod -a.
The result:
babylon5:root:/usr/src/linux-2.4.19:65 # depmod -a
depmod: *** Unresolved symbols in /lib/modules/2.4.19/kernel/drivers/block/rd.o
depmod: *** Unresolved symbols in /lib/modules/2.4.19/kernel/drivers/cdrom/cdrom.o
depmod: *** Unresolved symbols in /lib/modules/2.4.19/kernel/drivers/char/serial.o
depmod: *** Unresolved symbols in /lib/modules/2.4.19/kernel/drivers/ide/ide-cd.o
...
...
... well, you get the idea. A total of 40 modules fail, all with the
same error. The following is the list of failed modules:
drivers/block/rd.o
drivers/cdrom/cdrom.o
drivers/char/serial.o
drivers/ide/ide-cd.o
drivers/md/lvm-mod.o
drivers/md/raid5.o
drivers/net/ppp_async.o
drivers/net/ppp_deflate.o
drivers/net/ppp_generic.o
drivers/net/slhc.o
drivers/net/slip.o
drivers/parport/parport.o
drivers/parport/parport_pc.o
drivers/pcmcia/pcmcia_core.o
drivers/scsi/aic7xxx/aic7xxx.o
drivers/scsi/ide-scsi.o
drivers/scsi/sg.o
drivers/scsi/sr_mod.o
drivers/scsi/st.o
drivers/usb/hid.o
drivers/usb/storage/usb-storage.o
drivers/usb/usb-uhci.o
drivers/usb/usbcore.o
fs/fat/fat.o
fs/inflate_fs/inflate_fs.o
fs/intermezzo/intermezzo.o
fs/isofs/isofs.o
fs/lockd/lockd.o
fs/minix/minix.o
fs/nfs/nfs.o
fs/nfsd/nfsd.o
fs/reiserfs/reiserfs.o
fs/smbfs/smbfs.o
fs/udf/udf.o
fs/ufs/ufs.o
fs/vfat/vfat.o
net/ipv4/netfilter/ip_tables.o
net/ipv4/netfilter/ipt_REJECT.o
net/ipv4/netfilter/iptable_nat.o
net/sunrpc/sunrpc.o
So it definitely looks like something is unhappy with CONFIG_X86_USE_3DNOW,
possibly only when compiled with gcc-3.2, possibly not. Why it's not
being exported, I have no idea; as far as I can tell, it should be.
I haven't tried building an Athlon-optimized kernel *without* using
CONFIG_X86_USE_3DNOW.
--
********* Fight Back! It may not be just YOUR life at risk. *********
phil stracchino :: alaric@babcom.com :: halmayne@sourceforge.net
unix ronin :::: renaissance man :::: mystic zen biker geek
2000 CBR929RR, 1991 VFR750F3 (foully murdered), 1986 VF500F (sold)
Linux Now! ...because friends don't let friends use Microsoft.
next prev parent reply other threads:[~2002-09-04 18:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-04 18:19 PROBLEM: Kernel 2.4.19 does not export _mmx_memcpy when compiled with gcc-3.2 and Athlon optimizations Phil Stracchino
2002-09-04 18:48 ` Phil Stracchino [this message]
2002-09-04 23:35 ` Alan Cox
2002-09-05 1:16 ` Phil Stracchino
2002-09-11 21:19 ` CDROM driver does not support Linux partition tables Phil Stracchino
2002-09-11 21:28 ` Alan Cox
2002-09-12 5:06 ` Jens Axboe
2002-09-12 7:59 ` Alan Cox
2002-09-12 19:58 ` Phil Stracchino
2002-09-11 21:30 ` Måns Rullgård
2002-09-11 21:39 ` Phil Stracchino
2002-09-11 21:37 ` Thunder from the hill
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=20020904184854.GA9141@babylon5.babcom.com \
--to=alaric@babcom.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