All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theo Gjaltema <gjalt007@chello.nl>
To: Wolfgang Denk <wd@denx.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: mpc8xx and ld.so problem
Date: Wed, 13 Jul 2005 23:32:17 +0200	[thread overview]
Message-ID: <42D58861.5040900@chello.nl> (raw)
In-Reply-To: <20050713203204.7F711353A37@atlas.denx.de>

Wolfgang Denk schreef:

>In message <42D5361B.2070402@chello.nl> you wrote:
>  
>
>>It appeard that on my mpc862 target I had also this problem. I am using
>>ELDK3.1.1 which includes a 2.4.25 kernel.
>>    
>>
>
>No, most definitely not.
>
>  
>
I don't understand this, on
/pub/Linux/distributions/eldk/3.1.1/ppc-linux-x86/distribution/common
there are the sources of a 2.4.25 kernel.

>>    Large application (20MB c++, mostly shared-libs) crashes (sigseg) at
>>startup BEFORE main() is called.
>>    Attempts to debug the application also fail: the debugger crashes
>>also (sigseg).
>>    
>>
>
>I bet that this is a FAQ. Your SDRAM initialization is broken.
>  
>
This was one of my guesses also. Since this is beyond my knowledge, I 
had the parametes initialisation parameters compared to an other 
platform which did not had the problems (rtos based), the same 
parameters were used. I did not investigate it any further.

>  
>
>>I didn't change the C-lib, I took the 2.4.30/arch/ppc/kernel/head_8xx.S
>>file and copied this over the 2.4.25 head_8xx.S file.
>>In the 2.4.30 version there is a piece of code mentioning the dcbX
>>instruction problems.
>>    
>>
>
>And did this fix the problem completely? I would be a bit surprised.
>
>  
>
No problem since.

>>This driver causes the CPM sometimes to hang when performing a memset,
>>can this be caused by the same problem?
>>    
>>
>
>Yes. When your SDRAM init is broken, strange things will happen.
>
>  
>
I'll try the kernel with the original atm/utopia to see what happens.

>Best regards,
>
>Wolfgang Denk
>
>  
>
Thanks,
    Theo Gjaltema.

  reply	other threads:[~2005-07-13 21:33 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <42C1AAC1.4060702@gmail.com>
     [not found] ` <20050629085913.GA2153@logos.cnet>
     [not found]   ` <faba7798050630071347d4ad63@mail.gmail.com>
2005-07-01  9:44     ` mpc8xx and ld.so problem Marcelo Tosatti
2005-07-01 14:55       ` Jason McMullan
2005-07-01 10:17         ` Marcelo Tosatti
2005-07-01 18:56           ` Jason McMullan
2005-07-01 14:42             ` Marcelo Tosatti
2005-07-04  8:22             ` Yuli Barcohen
2005-07-05 19:53               ` Tom Rini
2005-07-06  8:58                 ` Yuli Barcohen
2005-07-08  0:36               ` Marcelo Tosatti
2005-07-10  7:31                 ` Yuli Barcohen
2005-07-13 15:41                   ` Theo Gjaltema
2005-07-13 20:32                     ` Wolfgang Denk
2005-07-13 21:32                       ` Theo Gjaltema [this message]
2005-07-13 23:11                         ` Wolfgang Denk
2005-07-14  5:44                     ` Anton Wöllert
2005-07-14  8:23           ` ptrace on linux 2.6.12 causes oops Anton Wöllert
2005-07-14 13:31             ` Kumar Gala
2005-07-14 11:20               ` Marcelo Tosatti
     [not found]               ` <faba77980507140809ad923db@mail.gmail.com>
2005-07-14 15:11                 ` Anton Wöllert
2005-07-14 20:27             ` aris
2005-07-14 11:19               ` Marcelo Tosatti
2005-07-15  9:42                 ` Anton Wöllert
2005-07-15  5:03                   ` Marcelo Tosatti
2005-07-03 16:01       ` mpc8xx and ld.so problem Anton Wöllert
2005-07-01 18:40 Tjernlund
  -- strict thread matches above, loose matches on Subject: below --
2005-07-14 13:32 Joakim Tjernlund

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=42D58861.5040900@chello.nl \
    --to=gjalt007@chello.nl \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=wd@denx.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 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.