From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S932242AbcFURDd (ORCPT <rfc822;w@1wt.eu>);
	Tue, 21 Jun 2016 13:03:33 -0400
Received: from mail-lf0-f65.google.com ([209.85.215.65]:33782 "EHLO
	mail-lf0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752732AbcFURDa (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Tue, 21 Jun 2016 13:03:30 -0400
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
Message-ID: <d2dceeba-439d-8325-9f77-e53ba13d1c1a@gmail.com>
Date: Tue, 21 Jun 2016 19:03:25 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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.