Preview Tool

Cisco Bug: CSCur19344 - Cannot start timer on "CCSIP_SPI_CONTROL" process

Last Modified

Nov 15, 2020

Products (1)

  • Cisco 2600 Series Multiservice Platforms

Known Affected Releases


Description (partial)

Root cause of this issue is when cube is getting an unsolicited notify message and starts processing it, Here somehow the value getting assigned is max value for unsigned long, when gets converted to signed long this will be always out of range. This is why we are seeing the trace back.

Below trace back and errors seen on syslog

%SYS-3-TIMERNEG: Cannot start timer (0xB680048) with negative offset
(-63535). -Process= "CCSIP_SPI_CONTROL", ipl= 0, pid= 357

-Traceback= 1B67504z 1B67898z 43A3E20z 43A2244z 18069B4z 17EEB94z 17E0FCCz 15C6AFCz
15C817Cz 15C89CCz 15B7BD4z 15B8058z 17D9BC4z 17DA050z 6A0994z

HW:Cisco7206VXR (NPE G2)
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.