timeslice -1259, current process infected

[Former Member]

Experts,

Below pasted is the stack trace that hit our Sybase Server for timeslice.

Can you help me in analyzing this, has anyone encountered similar time slice errors at your environment? I plan to schedule shared memory dump for this. But this was a rare kind.

The ASE version we run

Adaptive Server Enterprise/15.7/EBF 23820 SMP SP132 /P/RS6000/AIX 6.1

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

00:0017:00000:00013:2016/12/20 15:59:38.69 kernel timeslice -1259, current process infected at 100779184 (pss_init+0x2dc) 00:0017:00000:00013:2016/12/20 15:59:38.70 kernel **** Saved signal context (0x000000016a448630): **** 00:0017:00000:00013:2016/12/20 15:59:39.74 kernel __sc_onstack: 0x0, __sc_uerror: 55 00:0017:00000:00013:2016/12/20 15:59:39.74 kernel uc_sigmask: 0xffffffff1ffef877 0xffffffffffffffff 0xffffffffffffffff 0x7fffffffffffffff 00:0017:00000:00013:2016/12/20 15:59:39.80 kernel Machine Save State: 00:0017:00000:00013:2016/12/20 15:59:39.80 kernel PC (iar): 0000000100779184 (pss_init+0x2dc) 00:0017:00000:00013:2016/12/20 15:59:39.80 kernel Link Register (lr): 00000001007790dc (pss_init+0x234) 00:0017:00000:00013:2016/12/20 15:59:39.80 kernel Stack Pointer (stkp): 000000016a448b20 00:0017:00000:00013:2016/12/20 15:59:39.80 kernel msr : a00000000000d032 ctr : 00000000000000b6 cr : 22442840 00:0017:00000:00013:2016/12/20 15:59:39.80 kernel xer : 20000011 00:0017:00000:00013:2016/12/20 15:59:39.80 kernel r0 : 00000000000092b0 r1 : 000000016a448b20 r2 : 0000000110763870 00:0017:00000:00013:2016/12/20 15:59:39.80 kernel r3 : 00000001d8309000 r4 : 00000001d8305868 r5 : 00000001d8305868 00:0017:00000:00013:2016/12/20 15:59:39.81 kernel r6 : 0000000000000125 r7 : 00000001d831d878 r8 : 0000000000000000 00:0017:00000:00013:2016/12/20 15:59:39.81 kernel r9 : 0000000000000000 r10 : 0000000000000000 r11 : 000000016a449390 00:0017:00000:00013:2016/12/20 15:59:39.81 kernel r12 : 000000016a449af8 r13 : 0000000110d0e800 r14 : 00000001b66b0e10 00:0017:00000:00013:2016/12/20 15:59:39.81 kernel r15 : 00000001b66b0e10 r16 : 00000001d830eb08 r17 : 00000001d830dda0 00:0017:00000:00013:2016/12/20 15:59:39.81 kernel r18 : 00000001d830dda0 r19 : 00000001d830dd90 r20 : 00000001d830dd90 00:0017:00000:00013:2016/12/20 15:59:39.81 kernel r21 : 00000001d830dd80 r22 : 00000001d830dd80 r23 : 0000000000000000 00:0017:00000:00013:2016/12/20 15:59:39.81 kernel r24 : 0000000000000000 r25 : 001500000000002a r26 : 00000001d830eac0 00:0017:00000:00013:2016/12/20 15:59:39.81 kernel r27 : 00000001d8305868 r28 : 00000001d8305878 r29 : 0000000000000000 00:0017:00000:00013:2016/12/20 15:59:39.81 kernel r30 : 00000001d8315868 r31 : 00000001d8305868 00:0017:00000:00013:2016/12/20 15:59:39.81 kernel **** end of signal context **** 00:0017:00000:00013:2016/12/20 15:59:39.81 kernel timeslice error: spid 13 exhausted its 'time slice' of 100 milliseconds and additional 'cpu grace time' of 1000 ticks (100000 milliseconds). It has been marked for termination. 00:0017:00000:00013:2016/12/20 15:59:39.81 kernel This Adaptive Server process has had 1250881 major and 2111609 minor page faults since boot. 00:0017:00000:00013:2016/12/20 16:01:04.76 kernel ************************************ 00:0017:00000:00013:2016/12/20 16:01:04.76 server SQL Text: [no text] 00:0017:00000:00013:2016/12/20 16:01:04.76 kernel curdb = 0 tempdb = 2 pstat = 0x200 p2stat = 0x100000 00:0017:00000:00013:2016/12/20 16:01:04.76 kernel p3stat = 0x800 p4stat = 0x0 p5stat = 0x0 p6stat = 0x0 p7stat = 0x10000 00:0017:00000:00013:2016/12/20 16:01:04.76 kernel lasterror = 0 preverror = 0 transtate = 1 00:0017:00000:00013:2016/12/20 16:01:04.76 kernel curcmd = 0 program = 00:0017:00000:00013:2016/12/20 16:01:04.76 kernel extended error information: hostname: login: 00:0017:00000:00013:2016/12/20 16:01:04.86 kernel pc: 0x0000000100026af4 pcstkwalk+0x654() 00:0017:00000:00013:2016/12/20 16:01:04.86 kernel pc: 0x0000000100025c68 ucstkgentrace+0x178() 00:0017:00000:00013:2016/12/20 16:01:04.86 kernel pc: 0x0000000100025098 ucbacktrace+0xa8() 00:0017:00000:00013:2016/12/20 16:01:04.88 kernel pc: 0x000000010011b190 terminate_process.fdpr.chunk.4+0x240() 00:0017:00000:00013:2016/12/20 16:01:04.96 kernel pc: 0x0000000101be2504 kitermproc+0x178() 00:0017:00000:00013:2016/12/20 16:01:04.96 kernel pc: 0x0000000100779184 pss_init+0x2dc() 00:0017:00000:00013:2016/12/20 16:01:04.96 kernel pc: 0x0000000100778d24 pss_alloc+0x40() 00:0017:00000:00013:2016/12/20 16:01:04.97 kernel pc: 0x0000000100779394 spawn_conn_hdlr+0x100()

00:0017:00000:00013:2016/12/20 16:01:04.97 kernel end of stack trace, spid 13, kpid 3080216, suid 0 00:0020:00000:00012:2016/12/20 16:01:08.37 kernel Listener with protocol tcp, host egaes1ci, port 4901 has been terminated due to timeslice error. You can start a new listener on the same port.

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

[Former Member]

UPDATE : I rebooted the ASE server after forceful shutdown of the server. Once restarted the system has become accessible and fine now. I have raised a support incident with SAP.

Regards,

Ajith Prabhakaran

[Former Member]

Hello Bret,

The ASE dataserver, do not allow to login into the server now.

Regards,

Ajith Prabhakaran

[former_member188958]

Hi Ajith,

Well, the stack is pretty short when the timeslice happened, just spawn_conn_hdlr -> pss_alloc -> pss_init+0x2dc.

"pss" is the data structure used to track a login in ASE - so the stack essentially shows a new login being processed and ASE is in the middle of initializing the structure. I think the only downside to this error is that a login attempt failed once; the user may have retried immediately and gotten in.

I don't find any known bugs that quite match this.
If you log an incident, a support engineer might be able to get a bit further by digging into the
assembly language code for pss_init to see just what was being processed around offset 0x2dc
A memdump and a support incident are reasonable next steps.

-bret