From: Arjan van de Ven <arjan@infradead.org>
To: Rainer Koenig <Rainer.Koenig@fujitsu-siemens.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How do I analyze a soft lockup?
Date: Wed, 07 Mar 2007 07:12:20 -0800 [thread overview]
Message-ID: <1173280342.3540.7.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <87k5xt40ew.fsf@ABG3595C.abg.fsc.net>
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)?
prev parent reply other threads:[~2007-03-07 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 14:02 Rainer Koenig
2007-03-07 15:12 ` Arjan van de Ven [this message]
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=1173280342.3540.7.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=Rainer.Koenig@fujitsu-siemens.com \
--cc=linux-kernel@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®