All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: sparclinux@vger.kernel.org
Subject: Re: n2_crypto gets a BUG() triggered on T5240
Date: Mon, 11 Dec 2017 21:50:40 +0000	[thread overview]
Message-ID: <20171211215040.GA2190@ravnborg.org> (raw)
In-Reply-To: <nycvar.YFH.7.76.1712110214220.28416@n3.vanv.qr>

Hi Jan.

On Mon, Dec 11, 2017 at 02:14:31AM +0100, Jan Engelhardt wrote:
> 
> 
> With the current Debian sid system (2-3 days old) running the 4.14.2,
> loading the n2_crypto module causes a BUG() to get triggered. The
> system is a T5240 and the problem is reliably repeatable in case I
> should try some suggestions, patches, or if I need to provide more
> information. On a T5120, loading n2_crypto does not lead to this
> issue.

One (not so educated) guess would be to try if:
79db795833bf5c3e798bcd7a5aeeee3fb0505927 "sparc64: Don't clibber fixed registers in __multi4."
will fix this.

4.14.2 have the commit that the above commit fixes.

But using a newer kernel should probarly be first as Davem already suggested.

	Sam

  parent reply	other threads:[~2017-12-11 21:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-11  1:14 n2_crypto gets a BUG() triggered on T5240 Jan Engelhardt
2017-12-11 19:20 ` David Miller
2017-12-11 21:50 ` Sam Ravnborg [this message]
2017-12-16  0:57 ` Jan Engelhardt
2017-12-16  1:01   ` [PATCH] crypto: n2 - cure use after free Jan Engelhardt
2017-12-19 15:31     ` David Miller
2017-12-19 15:42       ` Jan Engelhardt
2017-12-19 15:42         ` Jan Engelhardt
2017-12-19 16:38         ` David Miller
2017-12-19 16:38           ` David Miller
2017-12-19 18:09           ` Jan Engelhardt
2017-12-19 18:09             ` Jan Engelhardt
2017-12-19 18:39             ` David Miller
2017-12-19 18:39               ` David Miller
2017-12-22  8:36             ` Herbert Xu
2017-12-22  8:36               ` Herbert Xu

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=20171211215040.GA2190@ravnborg.org \
    --to=sam@ravnborg.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.