9300-48UXM-A linux_iosd-image (wr mem unexpected reboot)

[netgn]

We have a few stacks of 9300-48UXM-A  ranging from size 2 to 5 in size planned for implementation.  We were running 17.3.6 code and noticed that anytime someone would issue command "wr mem" the switch would reload with errors below.  We figured this was a bug so we jumped up to Cisco recommended release of 17.12.4 but the issue still persists.  Anyone else seen this issue?  

switch#wr

ASR1000-WATCHDOG: Process = Exec

-Traceback= 1#c1c017c27f1bcabf35877bf8334596d3 :61576C2D8000+3E63990

IOSXE-WATCHDOG: Process = Exec

-Traceback= 1#c1c017c27f1bcabf35877bf8334596d3 :61576C2D8000+3E63990

Chassis 1 reloading, reason - Non participant detected

Apr 8 08:07:47.431: %PMAN-3-RPSWITCH: R0/0: pman: RP switch initiated. Critical process linux_iosd-image has failed (rc 0)

[marce1000]

   - If you get this on an advisory release then escalate and report towards Cisco's  TAC :
     You could consider last release https://software.cisco.com/download/home/286314060/type/282046477/release/IOSXE-17.17.1
     
  M.

[netgn]

There are no release notes or anything for this release I can find. Not
sure how I feel about going this direction considering its way outside
Cisco recommended release. We do not have TAC support unfortunately.

[marce1000]

   @netgn                   >... We do not have TAC support unfortunately.
                 To me that's vital in such circumstances and business managers should acknowledge that
                 when using important equipment for networking.
                 Your previous sentences stresses that point even more ; usually for instance then 'an unknown recent release'
                 could be used on test equipment (if available). But if there is no Cisco support , at this point ; you
                 can only jump into it, if it can not be tested , but that is not advisable indeed

  M.

[netgn]

Thanks, but I was not part of that decision.  There is no disagreement from me.  However the issue still remains and jumping to that version blindly concerns me as this problem happens on 17.3.6 and 17.12.4.  My larger question is and I should have asked earlier on is anyone seeing issues with these types of crashes on 17.9.x?  I did not go 17.9 as they have EOL that version.  

https://www.cisco.com/c/en/us/products/collateral/ios-nx-os-software/ios-xe-17/ios-xe-17-9-x-eol.html

[Leo Laohoo]

Without TAC to confirm, this smells like CSCwe12134. 

Before saving the config to other switches, please check for the following: 

• Switch uptime:  The higher the uptime (>6 months), the higher chances of hitting this bug. 
• Memory utilization:  Use the command "sh platform resources" to check the control-plane memory utilization.  If the memory utilization is >60%, chances of crashing is very, very high