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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20101109142733.BC69.A69D9226@jp.fujitsu.com>
Date:	Tue,  9 Nov 2010 14:33:12 +0900 (JST)
From:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To:	Luke Hutchison <luke.hutch@...il.com>
Cc:	kosaki.motohiro@...fujitsu.com, 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]"

> Hi,
> 
> I just wanted to report a bug upstream that is affecting the latest
> versions of at least both Fedora and Ubuntu. CPUs somehow lock up
> under load, producing errors of the form "BUG: soft lockup - CPU#0
> stuck for 61s! [kswapd0:184]"
> 
> The Fedora Bug report is here:
> https://bugzilla.redhat.com/show_bug.cgi?id=649694 -- however you can
> find lots of references to the error message on other distributions
> (including Ubuntu) by googling  "bug soft lockup cpu stuck".
> 
> Lockups seem to happen on server-class hardware under heavy loads when
> the machine is swapping.  This can lead to the entire machine locking
> up in some reported cases (although so far only individual CPUs seem
> to have locked up in my case, not the entire machine).  The point at
> which the CPU hangs varies -- see the dmesg output I attached to the
> Fedora bug report above.
> 
> My machine is a 12-way Xeon X5680 system with ext3, AFS and XFS
> filesystems (XFS is running on hardware RAID).  Please let me know if
> you need other info that would be helpful to diagnosing the problem.

AFAIK, This isssue was already fixed by Mel.

http://kerneltrap.org/mailarchive/linux-kernel/2010/10/27/4637977



--
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/