AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:
CFG:
PT:0
S:andy.sharp@lsi.com
RQ:
SSV:mhbs.lsil.com
NSV:
SSH:
R:<Maxim.Kozlovsky@lsi.com>
MAID:2
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/LSI/INBOX	0	861DA0537719934884B3D30A2666FECC010E3D2043@cosmail02.lsi.com
X-Sylpheed-End-Special-Headers: 1
Date: Mon, 22 Mar 2010 14:55:32 -0700
From: Andrew Sharp <andy.sharp@lsi.com>
To: "Kozlovsky, Maxim" <Maxim.Kozlovsky@lsi.com>
Subject: Re: kernel stacktrace
Message-ID: <20100322145532.6950acfa@ripper.onstor.net>
In-Reply-To: <861DA0537719934884B3D30A2666FECC010E3D2043@cosmail02.lsi.com>
References: <861DA0537719934884B3D30A2666FECC010E3D2043@cosmail02.lsi.com>
Organization: LSI
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Mon, 22 Mar 2010 15:49:16 -0600 "Kozlovsky, Maxim"
<Maxim.Kozlovsky@lsi.com> wrote:

> Hello,
> 
> Why I am getting so uninformative stack trace from kernel crash?
> 
> Call Trace:
> [<ffffffffc0bba578>] $LVL86+0x8/0x10 [scsi_mod]
> [<ffffffffc0bba568>] $LVL85+0x0/0x8 [scsi_mod]
> 
> Is there something I can do to make it better?
> 
> Max
> 

Normally you shouldn't get such a short stack trace, hence I would say
your stack is hosed.