> Source: [sk130752](https://support.checkpoint.com/results/sk/sk130752)

# sk130752 - Specific CPU core usage is 100% on VSX Gateway Standby VS

| Property | Value |
|----------|-------|
| Solution ID | sk130752 |
| Date Created | 2018-07-04 |
| Last Modified | 2018-09-24 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |
| OS | Gaia |

## Symptoms

- * Specific CPU core usage is 100% on VSX Gateway due to soft lockup of fwk process.
* */var/log/messages* file shows soft lockups for "fwk_0" processes similar to these:  
  Note:  
  If "soft lockup" is detected, originally, the stack trace should output after "Call Trace:" line, but in case of this problem it will not be output.

  ```
  
  kernel: BUG: soft lockup - CPU#4 stuck for 10s! [fwk21_0:5481]
  kernel: CPU 4:
  kernel: Modules linked in: mptctl(U) mptbase(U) vrrp_lkmmod(PU) adm1026(U) hwmon_vid(U) i2c_dev(U) nct7904(U) hwmon(U)
  button(U) 8021q(U) bonding(U) wrpmodmod(PU) fwmod(PU) simmod(PU) bridge(U) llc(U) ipsctlmod(PU) eeprom(U) pca9536(U)
  pca954x(U) i2c_virt(U) dm_multipath(U) lp(U) sr_mod(U) cdrom(U) shpchp(U) i2c_i801(U) igb(U) parport_pc(U) parport(U)
  sg(U) i2c_core(U) pcspkr(U) ixgbe(U) e1000e(U) serio_raw(U) ip_srs_apic(U) dm_snapshot(U) dm_zero(U) dm_mirror(U) dm_mod(U)
  usb_storage(U) cciss(U) ahci(U) libata(U) sd_mod(U) scsi_mod(U) raid1(U) ext3(U) jbd(U) ehci_hcd(U) ohci_hcd(U) uhci_hcd(U)
  kernel: Pid: 5481, comm: fwk21_0 Tainted: P      2.6.18-92cpx86_64 #1
  kernel: RIP: 0023:[<00000000f5c58060>]  [<00000000f5c58060>]
  kernel: RSP: 002b:00000000de805ef4  EFLAGS: 00000287
  kernel: RAX: 00000000000006c0 RBX: 00000000ffffffff RCX: 0000000000000000
  kernel: RDX: 0000000000000000 RSI: 00000000f6e50700 RDI: 00000000000001cc
  kernel: RBP: ffffffff8000a96b R08: 0000000000000000 R09: 0000000000000000
  kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 00000000ffffffff
  kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
  kernel: FS:  0000000000000000(0000) GS:ffff81010fd81640(0063) knlGS:00000000de809b90
  kernel: CS:  0010 DS: 002b ES: 002b CR0: 000000008005003b
  kernel: CR2: 00000000f7dec000 CR3: 00000003d1204000 CR4: 00000000000006e0
  kernel: 
  kernel: Call Trace:
  kernel: 
  ```

* The issue always occur on the Standby VS.
* The VSX gateway may become unresponsive after few days in this state. Even the serial console do not respond. In that case, there is no way to recover except a reboot.

## Cause

A software limitation in the code.

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content