Linux PARISC architecture development
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: PARISC list <parisc-linux@lists.parisc-linux.org>
Subject: [parisc-linux] Panic on boot in 64 bit 2.6.6-rc1-pa0
Date: 22 Apr 2004 18:32:15 -0400	[thread overview]
Message-ID: <1082673135.1714.118.camel@mulgrave> (raw)

I've traced this to an apparent linker fault.  It seems to be being
caused by having the scheduling function in its own section.

The offending code is in entry.S; this is what the code actually says:

syscall_do_resched:
        bl      schedule,%r2
#ifdef __LP64__
        ldo     -16(%r30),%r29          /* Reference param save area */
#else
        nop
#endif
        b       syscall_check_bh  /* if resched, we start over again */
        nop

And this is what it assembles to in the final vmlinux:

000000001010d05c <syscall_do_resched>:
    1010d05c:   e8 54 12 ac     b,l 101369b8 <dbl_to_sgl_fcnvxf+0xd0>,rp
    1010d060:   37 dd 3f e1     ldo -10(sp),ret1
    1010d064:   e8 1f 1b ed     b,l 1010ce60 <syscall_check_bh>,r0
    1010d068:   08 00 02 40     nop

Apparently ld has simply loaded an out of range value for the branch.  I
can't see that this is a global fault, otherwise calling init functions
wouldn't work either, but it does.

I've hacked a temporary work around in vmlinux.lds.S (simply make all of
the required functions close enough to entry.S that they don't need
stubs), but I'd really like some input from the toolchain people about
what the real problem actually is.

James

Index: arch/parisc/kernel/vmlinux.lds.S
===================================================================
RCS file: /var/cvs/linux-2.6/arch/parisc/kernel/vmlinux.lds.S,v
retrieving revision 1.10
diff -u -r1.10 vmlinux.lds.S
--- a/arch/parisc/kernel/vmlinux.lds.S	15 Apr 2004 18:04:14 -0000	1.10
+++ b/arch/parisc/kernel/vmlinux.lds.S	22 Apr 2004 22:30:16 -0000
@@ -49,8 +49,13 @@
 
   _text = .;			/* Text and read-only data */
   .text ALIGN(16) : {
-	*(.text*)
+	*(.text)
 	SCHED_TEXT
+	*(.text.do_softirq)
+	*(.text.sys_exit)
+	*(.text.do_sigaltstack)
+	*(.text.do_fork)
+	*(.text.*)
 	*(.PARISC.unwind)
 	*(.fixup)
 	*(.lock.text)		/* out-of-line lock text */

             reply	other threads:[~2004-04-22 22:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-22 22:32 James Bottomley [this message]
2004-04-22 22:50 ` [parisc-linux] Panic on boot in 64 bit 2.6.6-rc1-pa0 John David Anglin
2004-04-22 22:54   ` James Bottomley
2004-04-22 23:13     ` John David Anglin
2004-04-23 12:46       ` James Bottomley
2004-04-23 13:40         ` John David Anglin
2004-04-23 13:51           ` James Bottomley
2004-04-23 16:57             ` John David Anglin
2004-04-23 17:09               ` James Bottomley
2004-04-23 17:50                 ` John David Anglin
2004-04-23 19:01                   ` James Bottomley
2004-04-23 19:27                     ` John David Anglin
2004-04-23 19:43                       ` James Bottomley
2004-04-23 20:13                         ` John David Anglin

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=1082673135.1714.118.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=parisc-linux@lists.parisc-linux.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