linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Aaron Lu <aaron.lu@intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Colin Ian King <colin.i.king@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Fwd: crash/hang in mm/swapfile.c:718 add_to_avail_list when exercising stress-ng
Date: Wed, 2 Aug 2023 19:54:38 +0700	[thread overview]
Message-ID: <43765f2d-f486-8b00-7fb9-9eaea5045bfe@gmail.com> (raw)

Hi,

I notice a bug report on Bugzilla [1]. Quoting from it:

> How to reproduce:
> 
> Had 24 CPU Alderlake 16GB debian12 system running with default kernel (from makecondig) on 6.5-rc4, exercised with no swap to start with.
> 
> using stress-ng tip commit 0f2ef02e9bc5abb3419c44be056d5fa3c97e0137
> (see https://github.com/ColinIanKing/stress-ng )
> 
> build and run stress-ng for say 60 minutes:
> 
> ./stress-ng --cpu-online 50 --brk 50 --swap 50 --vmstat 1 -t 60m
> 
> Will hang in mm/swapfile.c:718 add_to_avail_list+0x93/0xa0
> 
> See attached file for an image of the console on the hang (I'm trying to get the full stack dump).

See Bugzilla for the full thread and attached console image.

FWIW, I have to forward this bug report to the mailing lists because
Thorsten noted that many developers don't take a look on Bugzilla
(see the BZ thread).

Thanks.

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

-- 
An old man doll... just what I always wanted! - Clara


             reply	other threads:[~2023-08-02 12:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-02 12:54 Bagas Sanjaya [this message]
2023-08-03  6:06 ` Aaron Lu
2023-08-03 13:41   ` Aaron Lu
2023-08-03 14:36     ` Colin King (gmail)
2023-08-03 15:04     ` Kefeng Wang
2023-08-04  1:58       ` Lu, Aaron

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=43765f2d-f486-8b00-7fb9-9eaea5045bfe@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=aaron.lu@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=colin.i.king@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=torvalds@linux-foundation.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