All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thiemo Seufer <ths@networkno.de>
To: Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp>
Cc: Kishore K <hellokishore@gmail.com>, linux-mips@linux-mips.org
Subject: Re: Problem booting malta with 2.4.33-rc1
Date: Mon, 7 Aug 2006 11:09:36 +0100	[thread overview]
Message-ID: <20060807100936.GD4383@networkno.de> (raw)
In-Reply-To: <20060807181020.37d94241.yoichi_yuasa@tripeaks.co.jp>

Yoichi Yuasa wrote:
> Hi,
> 
> On Mon, 7 Aug 2006 12:01:43 +0530
> "Kishore K" <hellokishore@gmail.com> wrote:
> 
> > Hi,
> > When trying to bring up Malta (4KC) board with 2.4.33-rc1 from linux-mips,
> > the kernel crashes. Boot log is enclosed along with this mail. I am using
> > the tool chain based on gcc 3.3.6, uClibc-0.9.27, binutils 2.14.90.0.8.
> > When the same tool chain is used for 2.4.31 kernel, the board comes up
> > without any issues.
> > 
> > Observed the same issue with tool chain based on gcc 3.4.4, uClibc-0.9.28,
> > binutils 2.15.94. Same result is observed even with  Malta 24KEC and
> > 2.4.33-rc1 kernel.
> > 
> > Does any one observe the same behaviour ? Am I missing something obvious
> > here ?
> 
> I have seen the same problem with gcc 3.4.4 mipssde-6.03.01-20051114 and
>  binutils 2.15.94 mipssde-6.03.01-20051114 with 2.6.6 kernel.
> gcc 3.3.2 and binutils 2.14.90.0.8 20040114 has no problem with same kernel.

Linux 2.4 has known issues with gcc 3.4 and higher, gcc 3.3 is the last
recommended version. The Malta configuration was fixed at some point to
work with 3.4, other configurations weren't.

The usual recommendation is an upgrade to a reasonably recent Linux 2.6. :-)


Thiemo

  reply	other threads:[~2006-08-07 10:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-07  6:31 Problem booting malta with 2.4.33-rc1 Kishore K
2006-08-07  9:10 ` Yoichi Yuasa
2006-08-07 10:09   ` Thiemo Seufer [this message]
2006-08-07 15:52     ` Ralf Baechle
2006-08-07 19:31 ` Ralf Baechle
     [not found] ` <08f801c6ba47$7ee0e4b0$e90d11ac@spb.in.rosprint.ru>
     [not found]   ` <f07e6e0608080241i6a928d6dh35be89f9dfdefb65@mail.gmail.com>
     [not found]     ` <f07e6e0608080250n782e50dci2dd1c61057cd72ce@mail.gmail.com>
2006-08-08 12:03       ` Alexander Voropay
2006-08-08 12:03         ` Alexander Voropay

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=20060807100936.GD4383@networkno.de \
    --to=ths@networkno.de \
    --cc=hellokishore@gmail.com \
    --cc=linux-mips@linux-mips.org \
    --cc=yoichi_yuasa@tripeaks.co.jp \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.