linux-kernel - Re: How do I analyze a soft lockup?

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]

Date:	Wed, 07 Mar 2007 07:12:20 -0800
From:	Arjan van de Ven <arjan@...radead.org>
To:	Rainer Koenig <Rainer.Koenig@...itsu-siemens.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: How do I analyze a soft lockup?

On Wed, 2007-03-07 at 15:02 +0100, Rainer Koenig wrote:
> Hi there,
> 
> Environment:
> 
> Kernel is 2.6.16.27, arch x86_64 on a Dual Core AMD64 machine with
> 4 GB of RAM. Also involved is an Areca 1100 SATA RAID controller
> with the drives from the Tekram website. 
> 
> Problem: 
> 
> We get customer reports that a system stops with the following kernel
> messages (as they are submitted to us, we're not able yet to reproduce
> the problem in our laboratory :-( )

looks like a stack overflow or a random memory scribble to me.
Alternatively the stacktrace is entirely garbled, also a possibility.
I assume you checked there were no other external modules involved?
Also can the user use a much later version of the kernel (which has
areca merged and can enable lockdep debugging)?

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