diff options
author | Russell Currey <ruscur@russell.cc> | 2016-08-09 11:55:23 +1000 |
---|---|---|
committer | Stewart Smith <stewart@linux.vnet.ibm.com> | 2016-08-10 16:40:10 +1000 |
commit | 85c46687ff2c0a4560b1041ebead185cc08b7e17 (patch) | |
tree | 88ff8533b4fbbe0bf7028ea53776ef504e77f25f | |
parent | 895f5e8a3a4416a523c21b9873885c7f19e92a09 (diff) | |
download | skiboot-85c46687ff2c0a4560b1041ebead185cc08b7e17.zip skiboot-85c46687ff2c0a4560b1041ebead185cc08b7e17.tar.gz skiboot-85c46687ff2c0a4560b1041ebead185cc08b7e17.tar.bz2 |
hmi: Clean up NPU FIR debug messages
With the skiboot log set to debug, the FIR (and related registers) were
logged all in the same message. It was too much for one line, didn't
clarify if the numbers were in hex, and didn't show leading zeroes.
So, split it into two lines, with leading zeroes and a "0x" prefix.
Signed-off-by: Russell Currey <ruscur@russell.cc>
Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
(cherry picked from commit 4eabfa056562e144c1a011bf4159387337023659)
Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
-rw-r--r-- | core/hmi.c | 7 |
1 files changed, 4 insertions, 3 deletions
@@ -514,9 +514,10 @@ static void find_npu_checkstop_reason(int flat_chip_id, if (!fatal_errors) return; - prlog(PR_DEBUG, - "NPU: FIR %llx FIR mask %llx FIR ACTION0 %llx FIR ACTION1 %llx\n", - npu_fir, npu_fir_mask, npu_fir_action0, npu_fir_action1); + prlog(PR_DEBUG, "NPU: FIR 0x%016llx mask 0x%016llx\n", + npu_fir, npu_fir_mask); + prlog(PR_DEBUG, "NPU: ACTION0 0x%016llx, ACTION1 0x%016llx\n", + npu_fir_action0, npu_fir_action1); /* Set the NPU to fenced since it can't recover. */ npu_set_fence_state(p, true); |