7.6.2-015: Spinnlock-loops?

[Former Member]

Linux X86_64

7.6.2-015

A shutdown of a central instance takes a LOT of time (> 10 minutes) - using "x_cons <SID> show ac 1" I see the following:

Console command finished (2007-07-17 19:07:05).

SERVERDB: P01

T226 7 -1 User 2117 Vbegexcl 0 0 175 105549713(r)

T230 7 -1 User 15448 Vbegexcl 0 0 173 105549713(r)

T231 7 -1 User 0 Spinlock Loop 0 0 105549713(r)

T232 7 -1 User 15555 Vbegexcl 0 0 172 105549713(r)

T233 7 -1 User 15576 Vbegexcl 0 0 172 105549713(r)

T234 7 -1 User 15584 Vbegexcl 0 0 173 105549713(r)

T247 8 -1 User 15447 Vbegexcl 0 0 174 102580666(s)

T251 8 -1 User 15585 Vbegexcl 0 0 172 102580666(s)

T252 8 -1 User 15593 Vbegexcl 0 0 172 102580666(s)

T260 9 -1 User 15452 Vbegexcl 0 0 175 118312956(r)

T261 9 -1 User 15455 Vbegexcl 0 0 172 118312956(r)

T262 9 -1 User 15557 Vbegexcl 0 0 172 118312956(r)

T264 9 -1 User 15586*Spinlock Loop 42 0 118312956(r)

T265 9 -1 User 15594 Vbegexcl 0 0 172 118312956(r)

T266 9 -1 User 0 Running 0 0 118312956(r)

T276 9 -1 User 0*Spinlock Loop 41 0 118312956(r)

T279 10 -1 User 0*Spinlock Loop 0 0 83141700(r)

T280 10 -1 User 15456 Vbegexcl 0 0 174 83141700(r)

T281 10 -1 User 15560 Vbegexcl 0 0 174 83141700(r)

T282 10 -1 User 15579 Vbegexcl 0 0 175 83141700(r)

T283 10 -1 User 15587 Vbegexcl 0 0 175 83141700(r)

T284 10 -1 User 15608 Vbegexcl 0 0 174 83141700(r)

T285 10 -1 User 0*Spinlock Loop 41 0 83141700(r)

T298 11 -1 User 15451 Running 0 7 177 66661984(r)

T299 11 -1 User 15552 Vbegexcl 0 0 175 66661984(r)

T300 11 -1 User 15556 Vbegexcl 0 0 175 66661984(r)

T301 11 -1 User 15581 Vbegexcl 0 0 174 66661984(r)

T302 11 -1 User 15588 Vbegexcl 0 0 174 66661984(r)

T305 11 -1 User 0*Spinlock Loop 41 0 66661984(r)

T315 11 -1 User 0*Spinlock Loop 42 0 66661984(r)

T317 12 -1 User 15449 Running 0 2716 178 165447130(r)

T318 12 -1 User 15554 Vbegexcl 0 0 176 165447130(r)

T319 12 -1 User 15562*Spinlock Loop 43 0 165447130(r)

T323 12 -1 User 15816 Vbegexcl 0 0 176 165447130(r)

T325 12 -1 User 0*Spinlock Loop 44 0 165447130(r)

T326 12 -1 User 0*Spinlock Loop ! 41 0 165447130(r)

T327 12 -1 User 0*Spinlock Loop 42 0 165447130(r)

T330 12 -1 User 0*Spinlock Loop ! 45 0 165447130(r)

T334 12 -1 User 9171 Vbegexcl 0 0 172 165447130(r)

T336 13 -1 User 15553 Vbegexcl 0 0 172 107867342(r)

T338 13 -1 User 15582 Vbegexcl 0 0 177 107867342(r)

T339 13 -1 User 15590 Vbegexcl 0 0 177 107867342(r)

T340 13 -1 User 0*Spinlock Loop 42 0 107867342(r)

T341 13 -1 User 0*Spinlock Loop 42 0 107867342(r)

T342 13 -1 User 0*Spinlock Loop 44 0 107867342(r)

T347 13 -1 User 0*Spinlock Loop 0 0 107867342(r)

T348 13 -1 User 0*Spinlock Loop 43 0 107867342(r)

T356 14 -1 User 0*Spinlock Loop 41 0 144368048(r)

T358 14 -1 User 0*Spinlock Loop 40 0 144368048(r)

T360 14 -1 User 0*Spinlock Loop 41 0 144368048(r)

What is the reason for that? I never saw that task state before...

--

Markus

[markus_doehr2 · Accepted solution]

additional info: This goes on even after all application servers were shut down - the database uses 100 % of CPU time (8 CPU box) and doing those strange things...

--

Markus

[former_member229109 · Accepted solution]

Hello Markus,

-> Please check "Reason and Prerequisites" of the SAP note 1041650, if it's related to your problem.

-> Did you create the OSS ticket, therefore we could logon to your system via OSS & take a look closer on this issue?

Thank you and best regards, Natalia Khlopina

[markus_doehr2 · Accepted solution]

Hi Natalia,

thank you for the hint. All our files are local so this can't be the problem.

Since this was our production system I needed to go on - after some minutes the database was safely shut down (db_offline) and could be restarted again.

What I was seeing also is the fact, that the DB server consumed MUCH MORE memory than before with 7.6.0-036.

I will have a look on this in the upcoming days and will create an OSS call if that problems shows up again.

Greetings,

--

Markus