Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Kumba <kumba@gentoo.org>
To: linux-mips@linux-mips.org
Subject: 2.4 kernels + >=binutils-2.14.90.0.8
Date: Mon, 08 Mar 2004 18:26:42 -0500	[thread overview]
Message-ID: <404D0132.3020202@gentoo.org> (raw)


Having an odd issue with booting 2.4 kernels built with 
binutils-2.14.90.0.8 and newer on an Indy R5000:

System Maintenance Menu

1) Start System
2) Install System Software
3) Run Diagnostics
4) Recover System
5) Enter Command Monitor

Option? 5
Command Monitor.  Type "exit" to return to the menu.
 >> ls
scsi(0)disk(4)rdisk(0)partition(8)/:
2422x0  2425p6x1  2603x0  arcboot  2425x0  2423x0  2422x1
/dev/sda3/: no such device
 >> boot -f 2425x0

Cannot load scsi(0)disk(4)rdisk(0)partition(8)/2425x0.
Text start 0x8000000, size 0x194400 doesn't fit in a FreeMemory area.
Unable to load 2425x0: ``2425x0'' is not a valid file to boot.
 >>

This issue started appearing with binutils-2.14.90.0.8, and still exists 
in binutils-2.15.90.0.1.1.  If I downgrade to binutils-2.14.90.0.7, the 
issue goes away (This is a cross-compiled kernel, btw).  So this seems 
to be a binutils-specific issue.  I'm not sure what the change was that 
led to this.  Any binutils people have an idea or need more test data run?

For reference, the compiler used was gcc-3.3.3, and has been tried on 
2.4.22, 2.4.23, and 2.4.25 kernels.  I haven't tried it with 2.6.x 
kernels yet.  Other binaries built with these binutils don't seem to 
show any outward signs of problems, just seems to be kernels.


--Kumba

-- 
"Such is oft the course of deeds that move the wheels of the world: 
small hands do them because they must, while the eyes of the great are 
elsewhere."  --Elrond

             reply	other threads:[~2004-03-08 23:23 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-08 23:26 Kumba [this message]
2004-03-08 23:44 ` 2.4 kernels + >=binutils-2.14.90.0.8 Thiemo Seufer
2004-03-09  0:04   ` Kumba
2004-03-09  0:34     ` Thiemo Seufer
2004-03-09  1:08       ` Kumba
2004-03-09  1:38         ` Thiemo Seufer
2004-03-09  2:15           ` Kumba
2004-03-09  2:37             ` Thiemo Seufer
2004-03-09  2:37               ` Thiemo Seufer
2004-03-09  6:07               ` Kumba
2004-03-17 18:51               ` Maciej W. Rozycki
2004-03-17 21:00                 ` Kumba
2004-03-17 21:04                   ` Maciej W. Rozycki
2004-03-17 23:10                     ` Kumba
2004-03-17 23:25                       ` Thiemo Seufer
2004-03-17 23:46                       ` Maciej W. Rozycki
2004-03-18  0:08                         ` Kumba
2004-03-18  0:46                           ` Maciej W. Rozycki
2004-03-23 11:49                             ` Maciej W. Rozycki
2004-03-23 12:00                               ` Ralf Baechle
2004-03-23 12:50                                 ` Maciej W. Rozycki
2004-03-23 13:04                                   ` Ralf Baechle
2004-03-23 14:22                                     ` Thiemo Seufer
2004-03-09  4:09         ` Ralf Baechle
2004-03-09  6:11           ` Kumba
2004-03-09 15:12           ` Tiago Assumpção
2004-03-09 16:48             ` Ralf Baechle

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=404D0132.3020202@gentoo.org \
    --to=kumba@gentoo.org \
    --cc=linux-mips@linux-mips.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