From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: linux-sh@vger.kernel.org
Subject: Re: Bug report: kernel BUG at arch/sh/kernel/dwarf.c:547!
Date: Tue, 26 Sep 2017 12:52:57 +0000 [thread overview]
Message-ID: <20170926145257.66f6596c@windsurf.lan> (raw)
In-Reply-To: <20170926142902.36e9539e@windsurf.lan>
Hello,
On Tue, 26 Sep 2017 14:36:42 +0200, John Paul Adrian Glaubitz wrote:
> On 09/26/2017 02:29 PM, Thomas Petazzoni wrote:
> > I'm using Linux 4.13 on a big endian SH4A system,
>
> Wow, that's the first time I hear someone use SuperH in Big-Endian mode.
Hehe, yes, I know, it's pretty uncommon. The hardware platform I'm
using was not running Linux... until now. And the big endian choice is
made at the HW level, so it's not trivial to change it to little endian.
> May I ask what kind of hardware you are using? I'm still looking for
> new/used SH4 boards to add additional buildd resources in Debian.
It's a custom platform using the SH7786 SoC. Sadly, this is clearly not
a HW platform that I can provide to help Debian having more build
resources.
> > You'll find below the full kernel panic log. You'll also notice that
> > the layout of the kernel panic message is really weird, with many
> > newlines all over the place, which probably is another bug.
> I think it might be a better idea to report this issue to the kernel
> bugzilla [1] so your bug report doesn't get lost. SuperH can now be
> selected as the target architecture, too.
I thought about this, but I'm not sure the SH maintainers are actively
looking at the kernel bug tracker.
Let's see if Rich and/or Yoshinori have some feedback about my issue.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-09-26 12:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 12:29 Bug report: kernel BUG at arch/sh/kernel/dwarf.c:547! Thomas Petazzoni
2017-09-26 12:36 ` John Paul Adrian Glaubitz
2017-09-26 12:52 ` Thomas Petazzoni [this message]
2017-09-26 12:55 ` John Paul Adrian Glaubitz
2017-09-26 13:04 ` Thomas Petazzoni
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=20170926145257.66f6596c@windsurf.lan \
--to=thomas.petazzoni@free-electrons.com \
--cc=linux-sh@vger.kernel.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