From: Andreas Schwab <schwab@suse.de>
To: Jan Vrany <jan.vrany@fit.cvut.cz>
Cc: "gdb\@sourceware.org" <gdb@sourceware.org>,
Andrew Burgess <andrew.burgess@embecosm.com>,
Palmer Dabbelt <palmer@sifive.com>,
Boris Shingarov <boris@shingarov.com>
Subject: Re: Commit 90af06793e breaks RISC-V native target
Date: Tue, 08 Jan 2019 11:04:00 -0000 [thread overview]
Message-ID: <mvmwonfh0l5.fsf@suse.de> (raw)
In-Reply-To: <2cda8aec3f030f6cbf5f2176621b01d8194d1521.camel@fit.cvut.cz> (Jan Vrany's message of "Tue, 08 Jan 2019 10:26:14 +0000")
On Jan 08 2019, Jan Vrany <jan.vrany@fit.cvut.cz> wrote:
> This is in Debian RISC-V using 4.15 kernel (commit c9dc587367 from [1] which
> is essentially SiFive's 4.15 kernel used on Unleashed plus few patches apparently
> needed to make GDB native target working).
This is a kernel bug. Make sure you have commit 732e8e4130.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2019-01-08 11:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 10:26 Jan Vrany
2019-01-08 11:04 ` Andreas Schwab [this message]
2019-01-08 21:03 ` Jan Vrany
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=mvmwonfh0l5.fsf@suse.de \
--to=schwab@suse.de \
--cc=andrew.burgess@embecosm.com \
--cc=boris@shingarov.com \
--cc=gdb@sourceware.org \
--cc=jan.vrany@fit.cvut.cz \
--cc=palmer@sifive.com \
/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