mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Eger <random-temp_addy-1067947802.46b228@theboonies.us>
To: linux-kernel@vger.kernel.org
Subject: gcc 3.2+ alignment issue with 2.6 kernel (was Re: 2.6.0-test6 + fb patch = dead PowerBook)
Date: Tue, 28 Oct 2003 06:09:57 -0600	[thread overview]
Message-ID: <1067342997.3f9e5c95beefb@mail.theboonies.us> (raw)
In-Reply-To: <1067035133.3f99a9fd94647@mail.theboonies.us>

FYI:

My issue seems to be a bad interaction of new versions of gcc (me gcc-3.2.3, him
gcc-3.3.1) with alignments in the kernel.  My problems have gone away with the
following patch presented on linuxppc-dev by Sam Ravnborg.  I do not know if
other platforms are affected, so similar patches might be needed elsewhere.

Why this misalignment would turn my machine into a brick even through reboots...
I do not know. 

-Eger David


===== arch/ppc/kernel/vmlinux.lds.S 1.24 vs edited =====
--- 1.24/arch/ppc/kernel/vmlinux.lds.S Fri Sep 12 18:26:52 2003
+++ edited/arch/ppc/kernel/vmlinux.lds.S Sun Oct 12 20:17:25 2003
@@ -47,13 +47,17 @@

.fixup : { *(.fixup) }

- __start___ex_table = .;
- __ex_table : { *(__ex_table) }
- __stop___ex_table = .;
+ __ex_table : {
+ __start___ex_table = .;
+ *(__ex_table)
+ __stop___ex_table = .;
+ }

- __start___bug_table = .;
- __bug_table : { *(__bug_table) }
- __stop___bug_table = .;
+ __bug_table : {
+ __start___bug_table = .;
+ *(__bug_table)
+ __stop___bug_table = .;
+ }

/* Read-write section, merged into data segment: */
. = ALIGN(4096);


      reply	other threads:[~2003-10-28 10:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-24 18:44 2.6.0-test6 + fb patch = dead PowerBook David Eger
2003-10-24 22:38 ` David Eger
2003-10-28 12:09   ` David Eger [this message]

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=1067342997.3f9e5c95beefb@mail.theboonies.us \
    --to=random-temp_addy-1067947802.46b228@theboonies.us \
    --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

all inboxes | Powered by JetHome®