mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Lucas Stach <l.stach@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Booting kernel crashes when using OSELAS.Toolchain-2014.12.1 for ARMv5TE
Date: Tue, 25 Aug 2015 14:23:34 +0200	[thread overview]
Message-ID: <1440505414.3066.36.camel@pengutronix.de> (raw)
In-Reply-To: <3f5c43d1e27f442ba3d1dc5c03d90707@GINS-EXC01.gins.local>

Hi Jan-Marc,

Am Dienstag, den 25.08.2015, 11:56 +0000 schrieb Stranz Jan-Marc:
> Hi Juergen,
> 
> I also think it is hard to find out the root of the problem.
> But  I have to find it out otherwise the new OSELAS-Toolchain isn't usable for our project and maybe also for others too.
> 
> I would underline the point again, that I didn't change the configuration of the bsp project (same kernel version, same versions of packages, ...).
> I've only build a new cross toolchain with OSELAS.Toolchain-2014.12.1 and I use this toolchain to build the bsp project.
> 
> What can I do?
> Would it help if I provide the boot messages?
> I can also enable the "linux kernel early printk debugging" in order to get more information.
> Is there any other think I can do to get additional useful information?
> 
Yes, please provide at least the kernel logs with the crash, so we can
see where things are going wrong. Ideally the logs from a successful
boot with the old toolchain are also interesting.

Regards,
Lucas

> -----Ursprüngliche Nachricht-----
> Von: Juergen Borleis [mailto:jbe@pengutronix.de] 
> Gesendet: Montag, 24. August 2015 11:20
> An: ptxdist@pengutronix.de
> Cc: Stranz Jan-Marc <JM.Stranz@gantner-instruments.com>
> Betreff: Re: [ptxdist] Booting kernel crashes when using OSELAS.Toolchain-2014.12.1 for ARMv5TE
> 
> Hi Jan-Marc,
> 
> On Tuesday 11 August 2015 16:45:44 Stranz Jan-Marc wrote:
> > Sorry, I've done a mistake in writing:
> > The configuration for the new toolchain is  
> >"arm-v5te-linux-gnueabi_gcc-4.9.2_glibc-2.20_binutils-2.24_kernel-3.16-
> >sani tized.ptxconfig" (gcc is "gcc-4.9.2" and not "gcc-4.6.2").
> >
> > Hello,
> >
> > I'm building linux kernel and root-fs for "TI OMAP-L138" (ARM-V5TE) 
> >using  an existing (and well working) BSP project. Until now I've used  
> >"OSELAS.Toolchain-2012.12.1" for building the toolchain using the  
> >configuration  
> >"arm-v5te-linux-gnueabi_gcc-4.7.2_glibc-2.16.0_binutils-2.22_kernel-3.6
> >-san
> >itized.ptxconfig".
> >
> > Now I've tried to use a newer toolchain project  
> >"OSELAS.Toolchain-2014.12.1". I've build the toolchain successfully 
> >(using  the configuration  
> >"arm-v5te-linux-gnueabi_gcc-4.6.2_glibc-2.20.0_binutils-2.24_kernel-3.1
> >6-sa nitized.ptxconfig"). I've also rebuild my BSP project (linux 
> >kernel and
> > root-fs) with this new toolchain (configuration of BSP project has 
> >been  unchanged!), but booting the kernel leads to a crash (kernel panic).
> >
> > I've attached the configuration files from my BSP project in order if 
> > someone can help me.
> 
> Hard to guess the root cause without more context.
> 
> Regards,
> Juergen
> 
> --
> Pengutronix e.K.                              | Juergen Borleis             | Industrial Linux Solutions                    | http://www.pengutronix.de/  |
> 

-- 
Pengutronix e.K.             | Lucas Stach                 |
Industrial Linux Solutions   | http://www.pengutronix.de/  |


-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2015-08-25 12:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-25 11:56 Stranz Jan-Marc
2015-08-25 12:23 ` Lucas Stach [this message]
2015-08-25 12:52 ` Juergen Borleis
  -- strict thread matches above, loose matches on Subject: below --
2015-08-25 15:17 Stranz Jan-Marc
2015-08-26  7:23 ` Juergen Borleis
2015-08-26  7:27   ` Bruno Thomsen
2015-08-25 14:34 Stranz Jan-Marc
2015-08-26  7:23 ` Juergen Borleis
2015-08-25 13:37 Stranz Jan-Marc
2015-08-25 14:01 ` Juergen Borleis
2015-08-25 14:40   ` Erwin Rol
2015-08-11 14:45 Stranz Jan-Marc
2015-08-24  9:19 ` Juergen Borleis
2015-08-11 14:16 Stranz Jan-Marc

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=1440505414.3066.36.camel@pengutronix.de \
    --to=l.stach@pengutronix.de \
    --cc=ptxdist@pengutronix.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