From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Hisashi Kanda <hikanda@zlab.co.jp>,
sparclinux@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sparc64: Swap registers for fault code and address in mna trap
Date: Tue, 21 Jun 2016 17:03:25 +0000 [thread overview]
Message-ID: <d2dceeba-439d-8325-9f77-e53ba13d1c1a@gmail.com> (raw)
In-Reply-To: <TYXPR01MB058946C0AC6B6523F82004FC99570@TYXPR01MB0589.jpnprd01.prod.outlook.com>
Hisashi Kanda wrote:
> In fact, BUG() in do_sparc64_fault occurred in modified version
> of linux-2.6.25.8 on SPARC64VIIIfx. I'm misunderstanding that
> the same problem remains in the latest.
Fujitsu K computer, with SPARC64 VIIIfx, runs a heavily modified
2.6.25.8 kernel. And maybe also binutils, glibc, gcc, gdb, ...
Even UTS_MACHINE was changed from sparc64 to s64fx.
WARNING: multiple messages have this Message-ID (diff)
From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Hisashi Kanda <hikanda@zlab.co.jp>,
sparclinux@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sparc64: Swap registers for fault code and address in mna trap
Date: Tue, 21 Jun 2016 19:03:25 +0200 [thread overview]
Message-ID: <d2dceeba-439d-8325-9f77-e53ba13d1c1a@gmail.com> (raw)
Hisashi Kanda wrote:
> In fact, BUG() in do_sparc64_fault occurred in modified version
> of linux-2.6.25.8 on SPARC64VIIIfx. I'm misunderstanding that
> the same problem remains in the latest.
Fujitsu K computer, with SPARC64 VIIIfx, runs a heavily modified
2.6.25.8 kernel. And maybe also binutils, glibc, gcc, gdb, ...
Even UTS_MACHINE was changed from sparc64 to s64fx.
next prev parent reply other threads:[~2016-06-21 17:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 0:05 [PATCH] sparc64: Swap registers for fault code and address in mna trap 神田 尚
2016-06-17 0:47 ` Julian Calaby
2016-06-17 0:47 ` Julian Calaby
2016-06-17 1:49 ` 神田 尚
2016-06-17 1:49 ` 神田 尚
2016-06-18 6:12 ` David Miller
2016-06-18 6:12 ` David Miller
2016-06-21 10:36 ` 神田 尚
2016-06-22 18:48 ` David Miller
2016-06-22 18:48 ` David Miller
2016-06-21 17:03 ` Xose Vazquez Perez [this message]
2016-06-21 17:03 ` Xose Vazquez Perez
[not found] <CAEZrgNam=ZO5JEijHBkpDQvhULrymutHVyzY4P4wfhJvCb_hgA@mail.gmail.com>
2016-06-16 18:00 ` David Miller
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=d2dceeba-439d-8325-9f77-e53ba13d1c1a@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=hikanda@zlab.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@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 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.