mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Stranz Jan-Marc <JM.Stranz@gantner-instruments.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: [ptxdist] Booting kernel crashes when using OSELAS.Toolchain-2014.12.1 for ARMv5TE
Date: Tue, 25 Aug 2015 13:37:48 +0000	[thread overview]
Message-ID: <f61c69047651406e8446fa39272a8317@GINS-EXC01.gins.local> (raw)

Hi Juergen,

thank you for the hint.

But I need some help: where can I check if there any known issues with specific gcc versions and specific Linux kernel versions.
Concrete: I'm using Linux kernel 3.3.0 (with some hardware specific adaptions) and the OSELAS.Toolchain-2014.12.1 provides gcc 4.9.2.

Best regards
Jan-Marc.


-----Ursprüngliche Nachricht-----
Von: Juergen Borleis [mailto:jbe@pengutronix.de] 
Gesendet: Dienstag, 25. August 2015 14:53
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 25 August 2015 13:56:15 Stranz Jan-Marc wrote:
> 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?

You should also check if there are some known issues with specific gcc versions and specific Linux kernel versions.

Regards,
Juergen

--
Pengutronix e.K.                              | Juergen Borleis             | Industrial Linux Solutions                    | http://www.pengutronix.de/  |
-- 
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2015-08-25 13:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-25 13:37 Stranz Jan-Marc [this message]
2015-08-25 14:01 ` Juergen Borleis
2015-08-25 14:40   ` Erwin Rol
  -- 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 11:56 Stranz Jan-Marc
2015-08-25 12:23 ` Lucas Stach
2015-08-25 12:52 ` Juergen Borleis
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=f61c69047651406e8446fa39272a8317@GINS-EXC01.gins.local \
    --to=jm.stranz@gantner-instruments.com \
    --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