From: Kumar Gala <galak@kernel.crashing.org>
To: "Morrison, Tom" <tmorrison@empirix.com>
Cc: Geary Sean-R60898 <sean.geary@freescale.com>,
linuxppc-dev@ozlabs.org, "Young,
Andrew" <andrew.young@windriver.com>,
"Brown, Jeff" <jbrown@empirix.com>
Subject: Re: How to debug a hung multi-core system....
Date: Thu, 21 May 2009 09:45:13 -0500 [thread overview]
Message-ID: <27AB6AE2-F8BA-4F05-9597-BCE0F98C1126@kernel.crashing.org> (raw)
In-Reply-To: <BD261180E6D35F4D9D32F3E44FD3D90110F53A79@EMPBEDEX.empirix.com>
> [Morrison, Tom]
> >BKM>tat
>
> Entry EPN RPN TID TMASK WIMGE TSIZ U0:3 X0:1
> PID TS PROT SHEN UR UW UX SR SW SX TIDZ VAL
>
> LT0 C0000000 00000000 00 0FF 04 9 0 0
> 0 0 P P E E D E E D D V
> LT1 D0000000 01000000 00 0FF 04 9 0 0
> 0 0 P P E E D E E D D V
> LT2 E0000000 02000000 00 0FF 04 9 0 0
> 0 0 P P E E D E E D D V
> LT4 F924E000 7C054500 BA 000 0B E 0 3
> 0 0 P S E E D E E D D V
> LT6 80000000 1F000000 F2 0FF 1D 9 B 3
> 0 0 U S D E D E E E D V
> LT7 64000000 1F000000 B3 07F 02 8 B 0
> 0 1 U S D E D D E E D V
> LT8 E5BF1000 995EA900 96 000 0C D 8 0
> 0 1 U S D E E E E D D V
> LT11 6B000000 F5700000 BC 03F 04 7 D 0
> 0 1 P S E E E E E E D V
> LT12 712DB000 F1B59100 2A 000 19 C F 1
> 0 1 P S E E E E D E D V
> LT13 00000000 F0000000 7F 0FF 07 B 0 0
> 0 1 P S D D E E E E D V
> LT14 A3000000 FDD00000 C5 03F 16 7 E 3
> 0 1 P S E E E D D E D V
> LT15 F7F00000 B0B80000 82 00F 1F 5 F 0
> 0 1 P P E E D D D D D V
Do you know what the Entry field means? Are you guys putting your own
mappings into the TLB? LT4..LT15 (with VAL = V) seem very odd to me.
- k
next prev parent reply other threads:[~2009-05-21 14:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 23:17 How to debug a hung multi-core system Morrison, Tom
2009-05-21 13:12 ` Kumar Gala
2009-05-21 13:52 ` Morrison, Tom
2009-05-21 14:45 ` Kumar Gala [this message]
2009-05-21 14:57 ` Morrison, Tom
2009-05-21 15:23 ` Morrison, Tom
2009-05-28 18:46 ` Kernel bug in 2.6.23...was: " Morrison, Tom
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=27AB6AE2-F8BA-4F05-9597-BCE0F98C1126@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=andrew.young@windriver.com \
--cc=jbrown@empirix.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=sean.geary@freescale.com \
--cc=tmorrison@empirix.com \
/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