linux-kernel - Re: "BUG: soft lockup - CPU#0 stuck for 61s! [kswapd0:184]"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <AANLkTikGC43B=+h5MNF665rFuRYfX4NQh6XyhuwxUT0A@mail.gmail.com>
Date:	Tue, 9 Nov 2010 00:50:40 -0500
From:	Luke Hutchison <luke.hutch@...il.com>
To:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
Cc:	linux-kernel@...r.kernel.org, linux-mm <linux-mm@...ck.org>,
	Mel Gorman <mel@....ul.ie>
Subject: Re: "BUG: soft lockup - CPU#0 stuck for 61s! [kswapd0:184]"

On Tue, Nov 9, 2010 at 12:33 AM, KOSAKI Motohiro
<kosaki.motohiro@...fujitsu.com> wrote:
> AFAIK, This isssue was already fixed by Mel.
>
> http://kerneltrap.org/mailarchive/linux-kernel/2010/10/27/4637977

Yes, based on where the CPU lockups were occurring
(zone_nr_free_pages, zone_watermark_ok), this fix does seem to address
the problem I described.  I assume the other lockup points
(_raw_spin_unlock_irqrestore, find_next_bit, sleeping_prematurely,
test_tsk_thread_flag) are also caused by the NR_FREE_PAGES problem?

Thank you for the link, I'll put it into the Fedora bug report and
hopefully a fix will be pushed out sometime soon.

Luke
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/