Ubuntu定期结冰

Question

我有个奇怪的问题。在刚刚安装的Ubuntu18.04上，系统似乎运转良好。突然，显然没有任何原因，系统挂断了，10秒或几分钟，我无法执行任何事情。

我试图让顶级实例处于打开状态，而RAM/CPU的使用似乎还不错。我在一台拥有6GB内存和12 6GB交换内存的i5机器上。我刚刚测试了内存和磁盘，它们是没有错误的。

编辑一些附加信息。我将CPU频率调控器设置为性能，因此它总是最大限度地工作。

在执行CPU密集型操作(如数据分析)时，问题会更多地出现。完成后，GUI变得完全没有响应能力，很难或不可能让它恢复工作。

grep . -r /sys/firmware/acpi/interrupts的编辑输出

/sys/firmware/acpi/interrupts/gpe2F:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe23:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe1F:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe13:       0  EN     enabled      unmasked
/sys/firmware/acpi/interrupts/gpe0F:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe03:       0         disabled     unmasked
/sys/firmware/acpi/interrupts/gpe3D:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe31:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe2D:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe21:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe1D:       0  EN     enabled      unmasked
/sys/firmware/acpi/interrupts/ff_pwr_btn:       0  EN     enabled      unmasked
/sys/firmware/acpi/interrupts/gpe11:       0     STS invalid      unmasked
/sys/firmware/acpi/interrupts/gpe0D:       0         disabled     unmasked
/sys/firmware/acpi/interrupts/gpe01:       0  EN     enabled      unmasked
/sys/firmware/acpi/interrupts/gpe3B:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe2B:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/ff_rt_clk:       0         disabled     unmasked
/sys/firmware/acpi/interrupts/ff_pmtimer:       0     STS invalid      unmasked
/sys/firmware/acpi/interrupts/gpe1B:       0     STS invalid      unmasked
/sys/firmware/acpi/interrupts/gpe38:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe0B:       0         disabled     unmasked
/sys/firmware/acpi/interrupts/gpe28:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe18:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe08:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe36:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe26:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/error:       0
/sys/firmware/acpi/interrupts/gpe16:       0  EN     enabled      unmasked
/sys/firmware/acpi/interrupts/sci:       4
/sys/firmware/acpi/interrupts/gpe06:       4  EN     enabled      unmasked
/sys/firmware/acpi/interrupts/gpe34:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe24:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe14:       0  EN     enabled      unmasked
/sys/firmware/acpi/interrupts/gpe04:       0         disabled     unmasked
/sys/firmware/acpi/interrupts/gpe3E:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe32:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe2E:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe22:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe1E:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe12:       0  EN     enabled      unmasked
/sys/firmware/acpi/interrupts/gpe0E:       0         disabled     unmasked
/sys/firmware/acpi/interrupts/gpe02:       0  EN     enabled      unmasked
/sys/firmware/acpi/interrupts/gpe3C:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe30:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe2C:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe20:       0         disabled     unmasked
/sys/firmware/acpi/interrupts/gpe1C:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe10:       0     STS invalid      unmasked
/sys/firmware/acpi/interrupts/gpe39:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe0C:       0         disabled     unmasked
/sys/firmware/acpi/interrupts/gpe00:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe3A:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe_all:       4
/sys/firmware/acpi/interrupts/gpe29:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe2A:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe19:       0     STS invalid      unmasked
/sys/firmware/acpi/interrupts/gpe1A:       0     STS invalid      unmasked
/sys/firmware/acpi/interrupts/gpe09:       0         disabled     unmasked
/sys/firmware/acpi/interrupts/gpe37:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe0A:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe27:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe17:       0     STS invalid      unmasked
/sys/firmware/acpi/interrupts/ff_gbl_lock:       0  EN     enabled      unmasked
/sys/firmware/acpi/interrupts/gpe07:       0         enabled      unmasked
/sys/firmware/acpi/interrupts/sci_not:       0
/sys/firmware/acpi/interrupts/gpe35:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe25:       0         disabled     unmasked
/sys/firmware/acpi/interrupts/gpe15:       0  EN     enabled      unmasked
/sys/firmware/acpi/interrupts/gpe05:       0         disabled     unmasked
/sys/firmware/acpi/interrupts/gpe3F:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe33:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/ff_slp_btn:       0         invalid      unmasked

编辑04/03/2019我运行了一个完整的智能测试，现在看起来不太好，至少在我看来。

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
3 Spin_Up_Time            0x0027   179   176   021    Pre-fail  Always       -       4025
4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       218
5 Reallocated_Sector_Ct   0x0033   154   154   140    Pre-fail  Always       -       364
7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
9 Power_On_Hours          0x0032   034   034   000    Old_age   Always       -       48741
10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       217
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       100
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       117
194 Temperature_Celsius     0x0022   089   080   000    Old_age   Always       -       58
196 Reallocated_Event_Count 0x0032   022   022   000    Old_age   Always       -       178
197 Current_Pending_Sector  0x0032   199   199   000    Old_age   Always       -       234
198 Offline_Uncorrectable   0x0030   199   199   000    Old_age   Offline      -       245
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   188   188   000    Old_age   Offline      -       2436
240 Head_Flying_Hours       0x0032   038   038   000    Old_age   Always       -       45709
241 Total_LBAs_Written      0x0032   200   200   000    Old_age   Always       -       81196791754
242 Total_LBAs_Read         0x0032   200   200   000    Old_age   Always       -       75991010629

Answer 1

这只是个人经验，但如果其他建议没有帮助，因为你的CPU在一个良好的温度。您可能想要考虑找到另一个类似的CPU兼容您的主板，并看看是否把它放在有助于解决问题。我最近有个CPU死掉了，它做的事情和你描述的几乎完全一样。也可能是主板的问题，但我会首先检查CPU。我知道获取和测试其他部件可能也不完全实用，但在我的经验中，这类问题往往是某种硬件问题。

如果这两个问题都不是问题，我将在硬盘驱动器上运行一个带有磁盘实用工具的智能测试，详细信息如下：如何在Ubuntu14.04到18.10的当前版本上检查SSD或HDD的智能状态？

Answer 2

我也会检查CPU温度，并确保您的冷却风扇是正常的。如果冷却风扇正常，您可能需要检查恶意软件/病毒。

此外，有时您可能需要更新BIOS以充分适应较新操作系统中的新功能(取决于系统)。

另一件事，我发现可能导致系统冻结是如果你的互联网连接被删除，特别是在更新等，所以也检查你的互联网连接，并确保它没有下降。

有点“黑暗中的镜头”，但也许有一个建议会有帮助。关于您的系统的更多信息，如MainBoard品牌、模型和版本，可能会有所帮助。

Answer 3

试着调整你的设置围绕着交换。例如，通过运行sudo sysctl vm.swappiness=20，在重新启动之后将再次恢复。即使您的内存尚未完全使用，内核也会开始将部件交换到磁盘，以保留一些内存空间。选择一个相当低的价值将导致更少的自由空间，但也减少交换。最佳值取决于内存大小和正在运行的工作负载。

当您找到一个值时，您可以通过在/etc/sysctl.conf中添加这样的行来永久地设置它：

vm.swappiness=20

有关更多背景信息，请参见：什么是交换，我如何改变它？