From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Subject: Question regarding call trace.
Date: Mon, 27 Feb 2006 14:12:13 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0602271411020.5678@p34> (raw)
I have a trace that looks like the following, my question is, are the
process(es) at the top of the call trace responible for the actual crash
of the machine? Are they the root cause?
Would this point to a bad SCSI board?
Call Trace: [<c0107a24>] [<c0107b0e>] [<f892ad30>]
[<c01073f6>] [<f8926590>]
scsi_eh_0 S 00000012 6376 166 1 167 13 (L-TLB)
Call Trace: [<c0107a24>] [<c0107b0e>] [<c01fffa1>] [<c0108d76>]
[<c01073f6>]
[<c01ffc80>]
scsi_eh_1 S 00000010 6372 167 1 168 166 (L-TLB)
Call Trace: [<c0107a24>] [<c0107b0e>] [<c01fffa1>] [<c0108d76>]
[<c01073f6>]
[<c01ffc80>]
scsi_eh_2 S 00000015 6372 168 1 169 167 (L-TLB)
Call Trace: [<c0107a24>] [<c0107b0e>] [<c01fffa1>] [<c0108d76>]
[<c01073f6>]
[<c01ffc80>]
scsi_eh_3 S 00000012 6372 169 1 165 168 (L-TLB)
Call Trace: [<c0107a24>] [<c0107b0e>] [<c01fffa1>] [<c0108d76>]
[<c01073f6>]
[<c01ffc80>]
kjournald S 00000019 2608 185 1 186 162 (L-TLB)
Call Trace: [<c0117dfa>] [<c017f6fa>] [<c017f570>] [<c01073f6>]
[<c017f590>]
kjournald S 00000019 0 186 1 187 185 (L-TLB)
Call Trace: [<c0117dfa>] [<c017f6fa>] [<c017f570>] [<c01073f6>]
[<c017f590>]
kjournald S 00000016 2608 187 1 188 186 (L-TLB)
Call Trace: [<c0117dfa>] [<c017f6fa>] [<c017f570>] [<c01073f6>]
[<c017f590>]
kjournald S 00000019 2608 188 1 675 187 (L-TLB)
Call Trace: [<c0117dfa>] [<c017f6fa>] [<c017f570>] [<c01073f6>]
[<c017f590>]
sshd S C850FBA0 20 675 1 699 188 (NOTLB)
Call Trace: [<c0108944>] [<c0117417>] [<c022e480>] [<c015676a>]
[<c0156af8>]
syslogd08dc3>]R 0000001A 3660 699 1 704
next reply other threads:[~2006-02-27 19:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-27 19:12 Justin Piszcz [this message]
2006-02-27 19:33 ` Jesper Juhl
2006-02-27 19:52 ` Justin Piszcz
[not found] <5KW4H-13v-11@gated-at.bofh.it>
2006-02-27 23:38 ` Robert Hancock
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=Pine.LNX.4.64.0602271411020.5678@p34 \
--to=jpiszcz@lucidpixels.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®