Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: mroos@linux.ee
Cc: sparclinux@vger.kernel.org, netdev@vger.kernel.org,
	gregkh@linuxfoundation.org, jslaby@suse.com
Subject: Re: sparc64 mystery with Cheetah+ D-cache parity error (n_tty_set_termios, bpf_check, cheetah_copy_page_insn)
Date: Wed, 10 Oct 2018 10:08:57 -0700 (PDT)	[thread overview]
Message-ID: <20181010.100857.951754034539960711.davem@davemloft.net> (raw)
In-Reply-To: <a4391645-0c4f-bd99-7371-b0e2cb505542@linux.ee>

From: Meelis Roos <mroos@linux.ee>
Date: Wed, 10 Oct 2018 16:24:59 +0300

> I have seen multiple strange messages like this, on multiple sparc64
> machines:
> 
> [ 55.523882] CPU[1]: Cheetah+ D-cache parity error at
> TPC[0000000000707e8c]
> [   55.626033] TPC<n_tty_set_termios+0x2c/0x3c0>
> 
> This specfic one ise from n_tty_set_termios and it is currently
> repeatable on a Sun V210.
> I have seen these on V245 and V445 too, with different addresses. On
> V445, the same address caused
> errors on multiple CPUs so it does not seem like a hardware problem,
> rather something software releated,
> that's why I am reporting it here.
> 
> On V445 it is gone with my current custom kernels but was there with
> 4.16.0-1-sparc64-smp Debian kernel package,
> probabaly because I do not have bpfilter compiled in:

I just started getting my older machines up again and I get these
kinds of errors sometimes too, usually in the TSB copy routine.

I'll definitely be looking into this and thanks for the report and
data.

      reply	other threads:[~2018-10-11  0:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-10 13:24 sparc64 mystery with Cheetah+ D-cache parity error (n_tty_set_termios, bpf_check, cheetah_copy_page_insn) Meelis Roos
2018-10-10 17:08 ` David Miller [this message]

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=20181010.100857.951754034539960711.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.com \
    --cc=mroos@linux.ee \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox