%LTL-4-LTL_PARITY_CHECK

[rysky8870]

I want to know about this log

Why it is being rebooted

Device : catalyst 6807

IOS : s2t54-advipservicesk9-mz.SPA.152-1.SY1a.bin

Module : 

Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
2 20 DCEF2T 4 port 40GE / 16 port 10GE C6800-16P10G SAL1929K8YM
3 5 Supervisor Engine 2T 10GE w/ CTS (Acti VS-SUP2T-10G SAL1930KUZ5
5 24 CEF720 24 port 1000mb SFP WS-X6824-SFP SAL1930L1G8
7 48 DCEF 48P 10/100/1000MB Ethernet C6800-48P-TX SAL1927JC3V

Mod MAC addresses Hw Fw Sw Status
--- ---------------------------------- ------ ------------ ------------ -------
2 5087.89f6.104a to 5087.89f6.105d 1.0 15.1(58r)SYL 15.2(1)SY1a Ok
3 d072.dcbb.b42a to d072.dcbb.b431 2.1 12.2(50r)SYS 15.2(1)SY1a Ok
5 84b8.02a6.f79c to 84b8.02a6.f7b3 2.4 12.2(18r)S1 15.2(1)SY1a Ok
7 64f6.9df2.0124 to 64f6.9df2.0153 1.0 12.2(18r)S1 15.2(1)SY1a Ok

Mod Sub-Module Model Serial Hw Status
---- --------------------------- ------------------ ----------- ------- -------
2 Distributed Forwarding Card C6800-DFC SAL1929K8YM 1.0 Ok
3 Policy Feature Card 4 VS-F6K-PFC4 SAL1930KUR7 3.0 Ok
3 CPU Daughterboard VS-F6K-MSFC5 SAL1930KNDW 3.0 Ok
5 Distributed Forwarding Card WS-F6K-DFC4-A SAL1930L1G8 2.4 Ok
7 Distributed Forwarding Card WS-F6K-DFC4-A SAL1927JC3V 1.0 Ok

log message (show stack)

Jun 8 05:22:39.651 UTC: %LTL-4-LTL_PARITY_CHECK: LTL parity check request for 0x52A4 from slot 3.
Jun 8 05:23:11.111 UTC: %LTL-4-LTL_PARITY_CHECK: LTL parity check request for 0x52A4 from slot 3.
Jun 8 05:23:41.451 UTC: %LTL-4-LTL_PARITY_CHECK: LTL parity check request for 0x52A4 from slot 3.
Jun 8 05:23:54.535 UTC: %OSPF-4-FLOOD_WAR: Process 103 flushes LSA ID 103.21.1.201 type-2 adv-rtr 172.16.2.1 in area 0.0.0.0
Jun 8 05:24:11.899 UTC: %LTL-4-LTL_PARITY_CHECK: LTL parity check request for 0x52A4 from slot 3.
Jun 8 05:24:11.899 UTC: %LTL-2-LTL_PARITY_CHECK_TOO_MANY_ERROR: LTL parity check request for slot 3.
Jun 8 05:24:14.131: %HA_EM-6-LOG: Mandatory.go_ltlmemconsty.tcl: GOLD EEM TCL policy for TestLtlFpoeMemoryConsistency
Jun 8 05:24:14.143 UTC: %DATACORRUPTION-1-DATAINCONSISTENCY: copy error, -PC= 0x7C72A64z
-Traceback= 6305480z A60CDA4z 622B9ECz 7C72A64z 7C72B74z 7C2C56Cz 7C403ACz 7C43EECz 7C20978z 7C3E240z 7C5E5E8z 7C403ACz 7C43EECz 7C20978z 7C2765Cz 7C647B8z
Jun 8 05:24:14.143 UTC: %DATACORRUPTION-1-DATAINCONSISTENCY: copy error, -PC= 0x7C72A64z
-Traceback= 6305480z A60CDA4z 622B9ECz 7C72A64z 7C72B74z 7C2E920z 7C403ACz 7C43EECz 7C20978z 7C3E240z 7C5E5E8z 7C403ACz 7C43EECz 7C20978z 7C2765Cz 7C647B8z
CMD: 'en' 05:24:14 UTC Wed Jun 8 2016
CMD: 'diagnostic action mod 3 test TestLtlFpoeMemoryConsistency default' 05:24:14 UTC Wed Jun 8 2016  <-- what?
Jun 8 05:24:14.383 UTC: %CONST_DIAG-2-HM_SUP_CRSH: Supervisor crashed due to unrecoverable errors, Reason: Failed TestLtlFpoeMemoryConsistency

%Software-forced reload

05:24:19 UTC Wed Jun 8 2016: Unexpected exception to CPU: vector 1500, PC = 0x5492874 , LR = 0x549280C

[Mark Malone]

Hi i would upgrade the software you have most likely hit a bug

TestLtlFpoeMemoryConsistency

This test verifies that the LTL an

d FPOE memories are working properly.

The test runs every 15 seconds.

Self-correction is applied if an error is detected. If

self-correction fails, corrective action is triggered to

reset the module. The module is powered-down on th

e third consecutive module

reset. If self-correction

passes, no action is taken. If too many self-correctio

ns occur within a short period of time (more than

three self-corrections in less than

300 seconds), the module is reset.

Intitial Release:

15.0(1)SY.

Corrective action:

Failure of this test causes the module to reset and power down after two

resets.

Hardware support:

All modules including supervisor engines

es