Mailing List Archive: Kern Mem

Kern Mem

Jan 26, 2011, 3:47 AM

Post #1 of 3 (6805 views)

Hi All,

What's going on with my switch ?

Jan 26 11:42:24.538 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA failed: Operation failed
Jan 26 11:42:24.538 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma: L2_ENTRY.ipipe0 failed(NAK)
Jan 26 11:42:23.429 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA failed: Operation failed
Jan 26 11:42:23.428 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma: L2_ENTRY.ipipe0 failed(NAK)
Jan 26 11:42:22.189 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA failed: Operation failed
Jan 26 11:42:22.188 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma: L2_ENTRY.ipipe0 failed(NAK)
Jan 26 11:42:20.848 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA failed: Operation failed
Jan 26 11:42:20.848 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma: L2_ENTRY.ipipe0 failed(NAK)
Jan 26 11:42:19.630 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA failed: Operation failed
Jan 26 11:42:19.630 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma: L2_ENTRY.ipipe0 failed(NAK)
Jan 26 11:42:18.535 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA failed: Operation failed
Jan 26 11:42:18.534 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma: L2_ENTRY.ipipe0 failed(NAK)
Jan 26 11:42:17.210 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA failed: Operation failed
Jan 26 11:42:17.209 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma: L2_ENTRY.ipipe0 failed(NAK)
Jan 26 11:42:16.109 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA failed: Operation failed
Jan 26 11:42:16.109 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma: L2_ENTRY.ipipe0 failed(NAK)
Jan 26 11:42:14.807 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA failed: Operation failed
Jan 26 11:42:14.806 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma: L2_ENTRY.ipipe0 failed(NAK)
Jan 26 11:42:13.609 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA failed: Operation failed

sh mem

Statistics On Unit 0 Processor
===========================
Total(b) Used(b) Free(b) Lowest(b) Largest(b)
268435456 2367012 266068444 266051880 266068444

CPU Statistics Of Unit 0
=======================================

CPU utilization for five seconds: 0%/0%; one minute: 4%; five minutes: 3%
PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
0x4293e000 10 1 10000 0.00% 0.00% 0.00% 0 POEAgt
0x4292a000 2901770 290177 10000 0.00% 0.00% 0.00% 0 diagagt
0x42916000 0 0 0 0.00% 0.00% 0.00% 0 debugagt

Kabayan

_______________________________________________
force10-nsp mailing list
force10-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/force10-nsp

Re: Kern Mem [ In reply to ]

lists at beatmixed

Jan 27, 2011, 9:50 PM

Post #2 of 3 (6756 views)

Permalink

I've seen it on one of our S50 switches recently, too, in combination with:

Jan 19 16:55:17.78 PST: %STKUNIT0-M:CP %KERN-2-INT:
soc_fb_mmu_parity_error:unit = 1,INTSTATUS = 0x00000000 Fail Count =
0

Symptoms included some [but not all] hosts having difficulty reaching
certain servers connected to switch.

I ripped the switch out and replaced it with a spare. No idea what the
actual problem is... although the parity_error would suggest some data
corruption, perhaps relating to onboard memory. But who knows other
than a developer -- there isn't mention that I could of this problem
in the Force10 support database.

-M

On Wed, Jan 26, 2011 at 3:47 AM, Kabayan <kab4yan@yahoo.com> wrote:
> Hi All,
>
> What's going on with my switch ?
>
> Jan 26 11:42:24.538 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA failed: Operation failed
> Jan 26 11:42:24.538 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma: L2_ENTRY.ipipe0 failed(NAK)
> Jan 26 11:42:23.429 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA failed: Operation failed
> Jan 26 11:42:23.428 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma: L2_ENTRY.ipipe0 failed(NAK)
> Jan 26 11:42:22.189 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA failed: Operation failed
> Jan 26 11:42:22.188 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma: L2_ENTRY.ipipe0 failed(NAK)
> Jan 26 11:42:20.848 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA failed: Operation failed
> Jan 26 11:42:20.848 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma: L2_ENTRY.ipipe0 failed(NAK)
> Jan 26 11:42:19.630 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA failed: Operation failed
> Jan 26 11:42:19.630 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma: L2_ENTRY.ipipe0 failed(NAK)
> Jan 26 11:42:18.535 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA failed: Operation failed
> Jan 26 11:42:18.534 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma: L2_ENTRY.ipipe0 failed(NAK)
> Jan 26 11:42:17.210 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA failed: Operation failed
> Jan 26 11:42:17.209 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma: L2_ENTRY.ipipe0 failed(NAK)
> Jan 26 11:42:16.109 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA failed: Operation failed
> Jan 26 11:42:16.109 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma: L2_ENTRY.ipipe0 failed(NAK)
> Jan 26 11:42:14.807 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA failed: Operation failed
> Jan 26 11:42:14.806 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma: L2_ENTRY.ipipe0 failed(NAK)
> Jan 26 11:42:13.609 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA failed: Operation failed
>
> sh mem
>
> Statistics On Unit 0 Processor
> ===========================
> Total(b) Used(b) Free(b) Lowest(b) Largest(b)
> 268435456 2367012 266068444 266051880 266068444
>
>
> CPU Statistics Of Unit 0
> =======================================
>
> CPU utilization for five seconds: 0%/0%; one minute: 4%; five minutes: 3%
> PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
> 0x4293e000 10 1 10000 0.00% 0.00% 0.00% 0 POEAgt
> 0x4292a000 2901770 290177 10000 0.00% 0.00% 0.00% 0 diagagt
> 0x42916000 0 0 0 0.00% 0.00% 0.00% 0 debugagt
>
>
> Kabayan
>
>
>
>
>
>
> _______________________________________________
> force10-nsp mailing list
> force10-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/force10-nsp
>

_______________________________________________
force10-nsp mailing list
force10-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/force10-nsp

Re: Kern Mem [ In reply to ]

fajri.kmmt at gmail

Jan 27, 2011, 10:05 PM

Post #3 of 3 (6708 views)

Permalink

>
> hi all,
>
> for related case, here I share advice from force10 expert :
>
>
> [26/01/2011 21:01:56] Prasanth Sasidharan: what i did was "turn off"
> parity checking of the L2_ENTRY
> [26/01/2011 21:02:01] Prasanth Sasidharan: and the error message
> disappeared
> [26/01/2011 21:02:15] Prasanth Sasidharan: it means that there is harware
> parity error in the system
> [26/01/2011 21:02:43] Prasanth Sasidharan: it is a ASIC related issue
>
> and he recommend for the switch like that is do RMAed..
>
> best regards,
> Fajri
>
> 2011/1/28 Matt Hite <lists@beatmixed.com>
>
> I've seen it on one of our S50 switches recently, too, in combination with:
>>
>> Jan 19 16:55:17.78 PST: %STKUNIT0-M:CP %KERN-2-INT:
>> soc_fb_mmu_parity_error:unit = 1,INTSTATUS = 0x00000000 Fail Count =
>> 0
>>
>> Symptoms included some [but not all] hosts having difficulty reaching
>> certain servers connected to switch.
>>
>> I ripped the switch out and replaced it with a spare. No idea what the
>> actual problem is... although the parity_error would suggest some data
>> corruption, perhaps relating to onboard memory. But who knows other
>> than a developer -- there isn't mention that I could of this problem
>> in the Force10 support database.
>>
>> -M
>>
>> On Wed, Jan 26, 2011 at 3:47 AM, Kabayan <kab4yan@yahoo.com> wrote:
>> > Hi All,
>> >
>> > What's going on with my switch ?
>> >
>> > Jan 26 11:42:24.538 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA
>> failed: Operation failed
>> > Jan 26 11:42:24.538 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma:
>> L2_ENTRY.ipipe0 failed(NAK)
>> > Jan 26 11:42:23.429 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA
>> failed: Operation failed
>> > Jan 26 11:42:23.428 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma:
>> L2_ENTRY.ipipe0 failed(NAK)
>> > Jan 26 11:42:22.189 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA
>> failed: Operation failed
>> > Jan 26 11:42:22.188 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma:
>> L2_ENTRY.ipipe0 failed(NAK)
>> > Jan 26 11:42:20.848 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA
>> failed: Operation failed
>> > Jan 26 11:42:20.848 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma:
>> L2_ENTRY.ipipe0 failed(NAK)
>> > Jan 26 11:42:19.630 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA
>> failed: Operation failed
>> > Jan 26 11:42:19.630 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma:
>> L2_ENTRY.ipipe0 failed(NAK)
>> > Jan 26 11:42:18.535 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA
>> failed: Operation failed
>> > Jan 26 11:42:18.534 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma:
>> L2_ENTRY.ipipe0 failed(NAK)
>> > Jan 26 11:42:17.210 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA
>> failed: Operation failed
>> > Jan 26 11:42:17.209 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma:
>> L2_ENTRY.ipipe0 failed(NAK)
>> > Jan 26 11:42:16.109 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA
>> failed: Operation failed
>> > Jan 26 11:42:16.109 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma:
>> L2_ENTRY.ipipe0 failed(NAK)
>> > Jan 26 11:42:14.807 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA
>> failed: Operation failed
>> > Jan 26 11:42:14.806 UTC: %STKUNIT0-M:CP %KERN-2-INT: _soc_xgs3_mem_dma:
>> L2_ENTRY.ipipe0 failed(NAK)
>> > Jan 26 11:42:13.609 UTC: %STKUNIT0-M:CP %KERN-2-INT: soc_l2x_thread: DMA
>> failed: Operation failed
>> >
>> > sh mem
>> >
>> > Statistics On Unit 0 Processor
>> > ===========================
>> > Total(b) Used(b) Free(b) Lowest(b) Largest(b)
>> > 268435456 2367012 266068444 266051880 266068444
>> >
>> >
>> > CPU Statistics Of Unit 0
>> > =======================================
>> >
>> > CPU utilization for five seconds: 0%/0%; one minute: 4%; five minutes:
>> 3%
>> > PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min
>> TTY Process
>> > 0x4293e000 10 1 10000 0.00% 0.00% 0.00%
>> 0 POEAgt
>> > 0x4292a000 2901770 290177 10000 0.00% 0.00% 0.00%
>> 0 diagagt
>> > 0x42916000 0 0 0 0.00% 0.00% 0.00%
>> 0 debugagt
>> >
>> >
>> > Kabayan
>> >
>> >
>> >
>> >
>> >
>> >
>> > _______________________________________________
>> > force10-nsp mailing list
>> > force10-nsp@puck.nether.net
>> > https://puck.nether.net/mailman/listinfo/force10-nsp
>> >
>>
>> _______________________________________________
>> force10-nsp mailing list
>> force10-nsp@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/force10-nsp
>>
>
>