Failing Address

  • 0
  • 1
  • Question
  • Updated 1 year ago
  • Answered
Does anyone knows what's causing this error?

05/22/2017 07:12:51.95 <Erro:Kern.Error> Failing  Address: 0x000000006aadb730, Data: 0x0000000000000000
05/22/2017 07:12:51.95 <Erro:Kern.Error> LMC0 ECC:      syndrome: 0x9b
05/22/2017 07:12:51.95 <Erro:Kern.Error> LMC0 ECC:      Failing column: 0x36d6
05/22/2017 07:12:51.95 <Erro:Kern.Error> LMC0 ECC:      Failing row:    0x6aad
05/22/2017 07:12:51.95 <Erro:Kern.Error> LMC0 ECC:      Failing bank:   6
05/22/2017 07:12:51.95 <Erro:Kern.Error> LMC0 ECC:      Failing rank:   0
05/22/2017 07:12:51.95 <Erro:Kern.Error> LMC0 ECC:      Failing dimm:   0
05/22/2017 07:12:51.95 <Erro:Kern.Error> ERROR LMC0 ECC: sec_err:4 ded_err:0
05/22/2017 07:12:51.77 <Erro:Kern.Error> Failing  Address: 0x000000006aadb730, Data: 0x0000000000000000
05/22/2017 07:12:51.77 <Erro:Kern.Error> LMC0 ECC:      syndrome: 0x9b
05/22/2017 07:12:51.77 <Erro:Kern.Error> LMC0 ECC:      Failing column: 0x36d6
05/22/2017 07:12:51.77 <Erro:Kern.Error> LMC0 ECC:      Failing row:    0x6aad
05/22/2017 07:12:51.77 <Erro:Kern.Error> LMC0 ECC:      Failing bank:   6
05/22/2017 07:12:51.77 <Erro:Kern.Error> LMC0 ECC:      Failing rank:   0
05/22/2017 07:12:51.77 <Erro:Kern.Error> LMC0 ECC:      Failing dimm:   0
05/22/2017 07:12:51.77 <Erro:Kern.Error> ERROR LMC0 ECC: sec_err:4 ded_err:0

What should I do?

Switch information:

System Type:      X670G2-72x

Image   : ExtremeXOS version 15.6.4.2 v1564b2-patch1-3 by release-manager
          on Thu Jan 28 11:12:00 EST 2016
BootROM : 1.0.2.1
Diagnostics : 2.1


Thanks

Bruno L.
Photo of Bruno

Bruno

  • 122 Points 100 badge 2x thumb

Posted 1 year ago

  • 0
  • 1
Photo of Aleixo Gomes

Aleixo Gomes, Employee

  • 334 Points 250 badge 2x thumb
hi , 

did you try booting in different partition/
Photo of Taykin Izzet

Taykin Izzet , Employee

  • 2,924 Points 2k badge 2x thumb
Bruno, please also check the log for any "CPU/L2 Memory ECC Counters have incremented" messages. These messages may be related to Memory.

From within EXOS, please also collect the following output:

# debug hal show sys-health-check


It would also be recommended to run extended diagnostics.
Photo of Bruno

Bruno

  • 122 Points 100 badge 2x thumb
Hi, Thanks for the reply.

I have no match in my logs for "CPU/L2 Memory ECC Counters have incremented" or similar.

Folow de output for "debug hal show sys-health-check"

==================================================
 # debug hal show sys-health-check

[System Info]
-------------------------
 System Time: Mon Jun 12 09:28:39 2017

[Conduit Retry Stats]
Retry Value = 15    Action on Error = 0

[Low Memory Alerts]

[CPU ECC Counters]

[BCM Counters]

[Chip TCAM Counters]

==================================================

I have the same error yesterday:

06/11/2017 09:25:27.71 <Erro:Kern.Error> Failing  Address: 0x000000006aadb730, Data: 0x0000000000000000
06/11/2017 09:25:27.71 <Erro:Kern.Error> LMC0 ECC:      syndrome: 0x9b
06/11/2017 09:25:27.71 <Erro:Kern.Error> LMC0 ECC:      Failing column: 0x36d6
06/11/2017 09:25:27.71 <Erro:Kern.Error> LMC0 ECC:      Failing row:    0x6aad
06/11/2017 09:25:27.71 <Erro:Kern.Error> LMC0 ECC:      Failing bank:   6
06/11/2017 09:25:27.71 <Erro:Kern.Error> LMC0 ECC:      Failing rank:   0
06/11/2017 09:25:27.71 <Erro:Kern.Error> LMC0 ECC:      Failing dimm:   0
06/11/2017 09:25:27.71 <Erro:Kern.Error> ERROR LMC0 ECC: sec_err:4 ded_err:0


Should I be worried?


Regards
Photo of Bruno

Bruno

  • 122 Points 100 badge 2x thumb
Hi, Thanks for the reply.

I have no match in my logs for "CPU/L2 Memory ECC Counters have incremented" or similar.

Folow de output for "debug hal show sys-health-check"

==================================================
 # debug hal show sys-health-check

[System Info]
-------------------------
 System Time: Mon Jun 12 09:28:39 2017

[Conduit Retry Stats]
Retry Value = 15    Action on Error = 0

[Low Memory Alerts]

[CPU ECC Counters]

[BCM Counters]

[Chip TCAM Counters]

==================================================

I have the same error yesterday:

06/11/2017 09:25:27.71 <Erro:Kern.Error> Failing  Address: 0x000000006aadb730, Data: 0x0000000000000000
06/11/2017 09:25:27.71 <Erro:Kern.Error> LMC0 ECC:      syndrome: 0x9b
06/11/2017 09:25:27.71 <Erro:Kern.Error> LMC0 ECC:      Failing column: 0x36d6
06/11/2017 09:25:27.71 <Erro:Kern.Error> LMC0 ECC:      Failing row:    0x6aad
06/11/2017 09:25:27.71 <Erro:Kern.Error> LMC0 ECC:      Failing bank:   6
06/11/2017 09:25:27.71 <Erro:Kern.Error> LMC0 ECC:      Failing rank:   0
06/11/2017 09:25:27.71 <Erro:Kern.Error> LMC0 ECC:      Failing dimm:   0
06/11/2017 09:25:27.71 <Erro:Kern.Error> ERROR LMC0 ECC: sec_err:4 ded_err:0


Should I be worried?


Regards
Photo of Brandon Clay

Brandon Clay, Escalation Support Engineer

  • 13,086 Points 10k badge 2x thumb
Hi Bruno,

I'd suggest opening up a case with GTAC. I believe this may require an RMA.