mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Anatoly Pugachev <matorola@gmail.com>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Cc: Sparc kernel list <sparclinux@vger.kernel.org>
Subject: Re: [sparc64] running stress-ng and a sparc64 hardware / kernel woes
Date: Sun, 3 Jan 2021 14:10:48 +0100	[thread overview]
Message-ID: <ff57237d-1e5b-9171-d320-eef57bc8d7c5@physik.fu-berlin.de> (raw)
In-Reply-To: <CADxRZqwARwrMeJZTWLeUtGyjStuz=ze2dwNqov0EyfHkRBM1fw@mail.gmail.com>

Hi Anatoly!

On 1/3/21 1:56 PM, Anatoly Pugachev wrote:
> Running a simple stress-ng as a non-privileged (non root) user :
> 
> stress-ng --opcode 1 --timeout 60 --metrics-brief
> 
> will almost always bring the linux kernel to an unusable state,
> starting from "Unable to handle kernel NULL pointer dereference",
> "Bogus kernel PC [0000000000000000] in fault handler", "Kernel
> unaligned access at TPC", "Unable to handle kernel paging request at
> virtual address" and "rcu: INFO: rcu_sched detected stalls on
> CPUs/tasks"...

This looks very similar to the kernel crashes on SPARC that we saw on
the buildds for the GCC testsuite in the past (and other packages).

I wonder whether we can use stress-ng to provoke the kernel crash on
POWER when hosting big-endian VMs with high load on little-endian hosts [1].

Adrian

> [1] https://bugzilla.kernel.org/show_bug.cgi?id=206669

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz@debian.org
`. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913


  reply	other threads:[~2021-01-03 13:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-03 12:56 Anatoly Pugachev
2021-01-03 13:10 ` John Paul Adrian Glaubitz [this message]
2021-01-03 13:39 ` Anatoly Pugachev

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=ff57237d-1e5b-9171-d320-eef57bc8d7c5@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matorola@gmail.com \
    --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

all inboxes | Powered by JetHome®