All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Mattli <dmm@mattli.us>
To: sparclinux@vger.kernel.org
Subject: Re: Linux Sparc FPU register corruption
Date: Thu, 18 Jun 2015 16:51:23 +0000	[thread overview]
Message-ID: <87ioalarjo.fsf@mattli.us> (raw)
In-Reply-To: <49B61131-8512-493B-BF49-7B2362383CCF@google.com>


I've submitted a bug to Debian against src:linux requesting that they
enable SLUB on the sparc kernel because in my testing a SLUB kernel
never shows an error with Knight's test program and a SLAB kernel shows
it within seconds.

Enabling SLUB also fixes the nettle FTBFS.

I'd appreciate if you can help by making this change to the linux
package, adding information to the bug or by confirming whether the
proposed workaround works for you.

Here's the src:linux bug:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bugx9180

And the nettle FTBFS bug:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bugx9013

Thanks!
David Mattli

  parent reply	other threads:[~2015-06-18 16:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-09  4:11 Linux Sparc FPU register corruption James Y Knight
2015-06-09  7:34 ` David Miller
2015-06-09  7:46 ` David Miller
2015-06-09 12:13 ` James Y Knight
2015-06-09 18:16 ` David Miller
2015-06-09 19:02 ` David Miller
2015-06-09 20:45 ` David Miller
2015-06-09 21:54 ` James Y Knight
2015-06-09 23:37 ` David Miller
2015-06-10  7:50 ` Aurelien Jarno
2015-06-10  9:18 ` David Miller
2015-06-10  9:33 ` Aurelien Jarno
2015-06-10 14:40 ` James Y Knight
2015-06-10 18:02 ` David Miller
2015-06-10 18:07 ` David Miller
2015-06-10 20:22 ` David Miller
2015-06-18 16:51 ` David Mattli [this message]
2015-06-19 10:50 ` David Miller
2015-08-05  1:06 ` David Miller
2015-08-05  5:07 ` Sam Ravnborg

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=87ioalarjo.fsf@mattli.us \
    --to=dmm@mattli.us \
    --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.