From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: mikpe@csd.uu.se
Cc: Olaf Hering <olh@suse.de>, linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.4.20-ben8 vmlinux.coff CLAIM error on PowerMac 4400
Date: 14 Mar 2003 17:13:53 +0100 [thread overview]
Message-ID: <1047658433.558.28.camel@zion.wanadoo.fr> (raw)
In-Reply-To: <15985.64740.932276.359232@gargle.gargle.HOWL>
On Fri, 2003-03-14 at 17:01, mikpe@csd.uu.se wrote:
> Benjamin Herrenschmidt writes:
> >
> > > vmlinux.coff built from 2.4.18, both vanilla and with Olaf's patch in
> > > http://penguinppc.org/~olaf/2.4.18/01_linux-2.4.18-rc4-lxppc_devel-0.diff.gz,
> > > boots Ok. However, 2.4.18 has the "excessively slow swim3 floppy writes"
> > > problem I mentioned earlier that 2.2.24 doesn't have.
> > >
> > > I also tried 2.4.20-ben8 with coffmain.c from 2.4.18 as you suggested,
> > > but it got the same CLAIM error as before. (hack-coff.c was unchanged
> > > and I didn't find anything else coff-related.)
> >
> > Can you try -ben8 and change _both_ ALIGN(8) to ALIGN(4096) ?
>
> In ld.script you mean? I noticed the second ALIGN(8) for bss and
> changed it to 4096 yesterday: it doesn't fix the problem.
Ok, thanks
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-03-14 16:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 14:53 2.4.20-ben8 vmlinux.coff CLAIM error on PowerMac 4400 mikpe
2003-03-13 15:25 ` Olaf Hering
2003-03-13 15:58 ` mikpe
2003-03-13 16:00 ` Olaf Hering
2003-03-13 16:05 ` Benjamin Herrenschmidt
2003-03-13 16:07 ` Olaf Hering
2003-03-13 16:11 ` Benjamin Herrenschmidt
2003-03-13 17:08 ` mikpe
2003-03-13 17:23 ` Benjamin Herrenschmidt
2003-03-13 23:13 ` mikpe
2003-03-13 23:18 ` Olaf Hering
2003-03-13 23:25 ` Benjamin Herrenschmidt
2003-03-14 13:32 ` Benjamin Herrenschmidt
2003-03-14 16:01 ` mikpe
2003-03-14 16:13 ` Benjamin Herrenschmidt [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=1047658433.558.28.camel@zion.wanadoo.fr \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mikpe@csd.uu.se \
--cc=olh@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).