From: James Bottomley <James.Bottomley@steeleye.com>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: PARISC list <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] Panic on boot in 64 bit 2.6.6-rc1-pa0
Date: 23 Apr 2004 09:51:56 -0400 [thread overview]
Message-ID: <1082728316.2017.18.camel@mulgrave> (raw)
In-Reply-To: <200404231340.i3NDejFp003662@hiauly1.hia.nrc.ca>
On Fri, 2004-04-23 at 09:40, John David Anglin wrote:
> If you look at the .level directive in the assembler output for one of
> these files, do you see "2.0w". The branches should also appear as "b,l"
> instead of the PA 1.x "bl". This should tell us whether this is a gcc
> or assembler problem.
The file causing the problems is entry.S, so it's an assembler file, not
a gcc file.
It has a .level 2.0w (with the appropriate #ifdefs) at the top.
Now, if you look at an objdump of the .o, it shows:
000000000000205c <syscall_do_resched>:
205c: e8 40 00 00 b,l 2064 <syscall_do_resched+0x8>,rp
205c: R_PARISC_PCREL17F schedule
2060: 37 dd 3f e1 ldo -10(sp),ret1
2064: e8 1f 1b ed b,l 1e60 <syscall_check_bh>,r0
2068: 08 00 02 40 nop
I suppose this means gas thinks it has to emit short relocations.
You have access to what I'm seeing; my kernel build environment is on
gsyprf11:~jejb/cvsnode/linux-2.6
James
next prev parent reply other threads:[~2004-04-23 13:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-22 22:32 [parisc-linux] Panic on boot in 64 bit 2.6.6-rc1-pa0 James Bottomley
2004-04-22 22:50 ` 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 [this message]
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=1082728316.2017.18.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=dave@hiauly1.hia.nrc.ca \
--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