From: Andi Kleen <ak@muc.de>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Andi Kleen <ak@muc.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.68-bk11: .text.exit errors in .altinstructions
Date: Fri, 2 May 2003 20:52:29 +0200 [thread overview]
Message-ID: <20030502185229.GA27169@averell> (raw)
In-Reply-To: <20030502171355.GU21168@fs.tum.de>
On Fri, May 02, 2003 at 07:13:56PM +0200, Adrian Bunk wrote:
> Hi Andi,
>
> I'm getting the following .text.exit errors in 2.5.68-bk11 (kernel
> compiled with gcc 2.95 for a K6):
That's what I feared. You have a prefetch or mb() in an __exit
function. Basically it's an binutils design bug, but hard to fix
according to the binutils hackers.
The only fix I know currently is to remove the .exit.text
discard from arch/i386/vmlinux.lds.S. It'll increase the kernel
text size slightly because functions that would only be needed
for module unload in some drivers will be compiled in too.
But it's probably not too bad, at worst a few KB.
-Andi
Index: linux/arch/i386/vmlinux.lds.S
===================================================================
RCS file: /home/cvs/linux-2.5/arch/i386/vmlinux.lds.S,v
retrieving revision 1.18
diff -u -u -r1.18 vmlinux.lds.S
--- linux/arch/i386/vmlinux.lds.S 30 Apr 2003 14:32:05 -0000 1.18
+++ linux/arch/i386/vmlinux.lds.S 2 May 2003 17:52:38 -0000
@@ -106,7 +106,6 @@
/* Sections to be discarded */
/DISCARD/ : {
- *(.exit.text)
*(.exit.data)
*(.exitcall.exit)
}
next prev parent reply other threads:[~2003-05-02 18:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-02 17:13 2.5.68-bk11: .text.exit errors in .altinstructions Adrian Bunk
2003-05-02 18:52 ` Andi Kleen [this message]
2003-05-03 13:52 ` Ingo Oeser
2003-05-05 23:04 ` Grzegorz Jaskiewicz
2003-05-06 0:53 ` Andi Kleen
2003-05-06 2:14 ` Andrew Morton
2003-05-06 5:13 ` Andi Kleen
2003-05-06 8:18 ` Grzegorz Jaskiewicz
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=20030502185229.GA27169@averell \
--to=ak@muc.de \
--cc=bunk@fs.tum.de \
--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