jjepsuomi's questions

我最近在我的 PC 上将 Ubuntu 16.04 升级到 18.04（使用 Nvidia GeForce GTX 1080 Ti GPU），自从我的文件系统是从这些巨大的日志文件中建立起来的。每次我关闭我的电脑时，我都会收到无数的 pcieport 消息，直到电脑自行关闭。

昨天我把我的机器开着过夜，当我回到它时，有一个通知说磁盘空间已全部用完，即/dev/sda1100% 使用。我设法通过du-command 找到了这一点，并将问题定位到/var/log/-folder 中的日志文件，其中包含超过350GB.

目前，日志文件正在重新构建，现在它们占用的空间大约为150GB. 导致问题的日志文件是：syslog.1, syslog和kern.log

我的问题是：是什么导致了这个问题以及如何解决它？

我在下面列出了有关我的系统的信息和日志文件中的几行。我将再次删除它们，但无休止地删除它们似乎不是最好的长期解决方案。

Distributor ID: Ubuntu
Description:    Ubuntu 18.04.3 LTS
Release:    18.04
Codename:   bionic

nvidia-smi
Thu Aug 15 09:25:53 2019       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 430.40       Driver Version: 430.40       CUDA Version: 10.1     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 108...  Off  | 00000000:01:00.0  On |                  N/A |
| 24%   58C    P0    67W / 250W |   1373MiB / 11177MiB |      1%      Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|    0      1298      G   /usr/lib/xorg/Xorg                            89MiB |
|    0      1337      G   /usr/bin/gnome-shell                          50MiB |
|    0      2258      G   /usr/lib/xorg/Xorg                           726MiB |
|    0      2465      G   /usr/bin/gnome-shell                         189MiB |
|    0     14914      G   ...e --type=gpu-process --field-trial-hand   154MiB |
|    0     18206      C   /usr/lib/libreoffice/program/soffice.bin     137MiB |
+-----------------------------------------------------------------------------+

lspci -vt
-[0000:00]-+-00.0  Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers
           +-01.0-[01]--+-00.0  NVIDIA Corporation GP102 [GeForce GTX 1080 Ti]
           |            \-00.1  NVIDIA Corporation GP102 HDMI Audio Controller
           +-02.0  Intel Corporation Device 3e92
           +-14.0  Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller
           +-16.0  Intel Corporation 200 Series PCH CSME HECI #1
           +-17.0  Intel Corporation 200 Series PCH SATA controller [AHCI mode]
           +-1b.0-[02]--
           +-1c.0-[03]--
           +-1c.4-[04]----00.0  ASMedia Technology Inc. Device 2142
           +-1c.7-[05]----00.0  Realtek Semiconductor Co., Ltd. RTL8812AE 802.11ac PCIe Wireless Network Adapter
           +-1d.0-[06]--
           +-1f.0  Intel Corporation Z370 Chipset LPC/eSPI Controller
           +-1f.2  Intel Corporation 200 Series/Z370 Chipset Family Power Management Controller
           +-1f.3  Intel Corporation 200 Series PCH HD Audio
           +-1f.4  Intel Corporation 200 Series/Z370 Chipset Family SMBus Controller
           \-1f.6  Intel Corporation Ethernet Connection (2) I219-V

系统日志.1

Aug 14 10:14:03 user kernel: [   10.680132] pcieport 0000:00:1c.7: AER: Corrected error received: 0000:00:1c.7
Aug 14 10:14:03 user kernel: [   10.680135] pcieport 0000:00:1c.7: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 14 10:14:03 user kernel: [   10.680135] pcieport 0000:00:1c.7:   device [8086:a297] error status/mask=00000001/00002000
Aug 14 10:14:03 user kernel: [   10.680136] pcieport 0000:00:1c.7:    [ 0] RxErr                 
Aug 14 10:14:03 user kernel: [   10.680187] pcieport 0000:00:1c.7: AER: Corrected error received: 0000:00:1c.7
Aug 14 10:14:03 user kernel: [   10.680190] pcieport 0000:00:1c.7: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 14 10:14:03 user kernel: [   10.680190] pcieport 0000:00:1c.7:   device [8086:a297] error status/mask=00000001/00002000
Aug 14 10:14:03 user kernel: [   10.680191] pcieport 0000:00:1c.7:    [ 0] RxErr                 
Aug 14 10:14:03 user kernel: [   10.680281] pcieport 0000:00:1c.7: AER: Corrected error received: 0000:00:1c.7
Aug 14 10:14:03 user kernel: [   10.680284] pcieport 0000:00:1c.7: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 14 10:14:03 user kernel: [   10.680284] pcieport 0000:00:1c.7:   device [8086:a297] error status/mask=00000001/00002000
Aug 14 10:14:03 user kernel: [   10.680285] pcieport 0000:00:1c.7:    [ 0] RxErr                 
Aug 14 10:14:03 user kernel: [   10.680374] pcieport 0000:00:1c.7: AER: Multiple Corrected error received: 0000:00:1c.7
Aug 14 10:14:03 user kernel: [   10.680378] pcieport 0000:00:1c.7: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 14 10:14:03 user kernel: [   10.680379] pcieport 0000:00:1c.7:   device [8086:a297] error status/mask=00000001/00002000
Aug 14 10:14:03 user kernel: [   10.680380] pcieport 0000:00:1c.7:    [ 0] RxErr                 
Aug 14 10:14:03 user kernel: [   10.680586] pcieport 0000:00:1c.7: AER: Multiple Corrected error received: 0000:00:1c.7
Aug 14 10:14:03 user kernel: [   10.680590] pcieport 0000:00:1c.7: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 14 10:14:03 user kernel: [   10.680591] pcieport 0000:00:1c.7:   device [8086:a297] error status/mask=00000001/00002000
Aug 14 10:14:03 user kernel: [   10.680591] pcieport 0000:00:1c.7:    [ 0] RxErr                 

系统日志

Aug 15 09:04:23 user kernel: [  307.590656] pcieport 0000:00:1c.7:    [ 0] RxErr                 
Aug 15 09:04:23 user kernel: [  307.590836] pcieport 0000:00:1c.7: AER: Multiple Corrected error received: 0000:00:1c.7
Aug 15 09:04:23 user kernel: [  307.590841] pcieport 0000:00:1c.7: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 15 09:04:23 user kernel: [  307.590843] pcieport 0000:00:1c.7:   device [8086:a297] error status/mask=00000001/00002000
Aug 15 09:04:23 user kernel: [  307.590844] pcieport 0000:00:1c.7:    [ 0] RxErr                 
Aug 15 09:04:23 user kernel: [  307.591125] pcieport 0000:00:1c.7: AER: Multiple Corrected error received: 0000:00:1c.7
Aug 15 09:04:23 user kernel: [  307.591134] pcieport 0000:00:1c.7: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 15 09:04:23 user kernel: [  307.591135] pcieport 0000:00:1c.7:   device [8086:a297] error status/mask=00000001/00002000
Aug 15 09:04:23 user kernel: [  307.591136] pcieport 0000:00:1c.7:    [ 0] RxErr                 
Aug 15 09:04:23 user kernel: [  307.591414] pcieport 0000:00:1c.7: AER: Multiple Corrected error received: 0000:00:1c.7
Aug 15 09:04:23 user kernel: [  307.591419] pcieport 0000:00:1c.7: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 15 09:04:23 user kernel: [  307.591420] pcieport 0000:00:1c.7:   device [8086:a297] error status/mask=00000001/00002000
Aug 15 09:04:23 user kernel: [  307.591422] pcieport 0000:00:1c.7:    [ 0] RxErr                 
Aug 15 09:04:23 user kernel: [  307.591607] pcieport 0000:00:1c.7: AER: Multiple Corrected error received: 0000:00:1c.7
Aug 15 09:04:23 user kernel: [  307.591614] pcieport 0000:00:1c.7: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 15 09:04:23 user kernel: [  307.591616] pcieport 0000:00:1c.7:   device [8086:a297] error status/mask=00000001/00002000
Aug 15 09:04:23 user kernel: [  307.591617] pcieport 0000:00:1c.7:    [ 0] RxErr                 
Aug 15 09:04:23 user kernel: [  307.591896] pcieport 0000:00:1c.7: AER: Multiple Corrected error received: 0000:00:1c.7
Aug 15 09:04:23 user kernel: [  307.591901] pcieport 0000:00:1c.7: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)

内核日志

Aug 14 10:14:03 user kernel: [   11.219257] pcieport 0000:00:1c.7: AER: Corrected error received: 0000:00:1c.7
Aug 14 10:14:03 user kernel: [   11.219259] pcieport 0000:00:1c.7: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 14 10:14:03 user kernel: [   11.219260] pcieport 0000:00:1c.7:   device [8086:a297] error status/mask=00000001/00002000
Aug 14 10:14:03 user kernel: [   11.219260] pcieport 0000:00:1c.7:    [ 0] RxErr                 
Aug 14 10:14:03 user kernel: [   11.219443] pcieport 0000:00:1c.7: AER: Multiple Corrected error received: 0000:00:1c.7
Aug 14 10:14:03 user kernel: [   11.219448] pcieport 0000:00:1c.7: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 14 10:14:03 user kernel: [   11.219448] pcieport 0000:00:1c.7:   device [8086:a297] error status/mask=00000001/00002000
Aug 14 10:14:03 user kernel: [   11.219449] pcieport 0000:00:1c.7:    [ 0] RxErr                 
Aug 14 10:14:03 user kernel: [   11.219714] pcieport 0000:00:1c.7: AER: Corrected error received: 0000:00:1c.7
Aug 14 10:14:03 user kernel: [   11.219717] pcieport 0000:00:1c.7: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 14 10:14:03 user kernel: [   11.219718] pcieport 0000:00:1c.7:   device [8086:a297] error status/mask=00000001/00002000
Aug 14 10:14:03 user kernel: [   11.219718] pcieport 0000:00:1c.7:    [ 0] RxErr                 
Aug 14 10:14:03 user kernel: [   11.219916] pcieport 0000:00:1c.7: AER: Multiple Corrected error received: 0000:00:1c.7
Aug 14 10:14:03 user kernel: [   11.219922] pcieport 0000:00:1c.7: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 14 10:14:03 user kernel: [   11.219923] pcieport 0000:00:1c.7:   device [8086:a297] error status/mask=00000001/00002000
Aug 14 10:14:03 user kernel: [   11.219924] pcieport 0000:00:1c.7:    [ 0] RxErr                 
Aug 14 10:14:03 user kernel: [   11.220101] pcieport 0000:00:1c.7: AER: Corrected error received: 0000:00:1c.7
Aug 14 10:14:03 user kernel: [   11.220104] pcieport 0000:00:1c.7: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 14 10:14:03 user kernel: [   11.220105] pcieport 0000:00:1c.7:   device [8086:a297] error status/mask=00000001/00002000
Aug 14 10:14:03 user kernel: [   11.220105] pcieport 0000:00:1c.7:    [ 0] RxErr                 

我需要在这里发布一个问题，因为经过多次谷歌搜索和尝试，我无法解决这个问题。所以这是我的问题：

我的系统由一台装有 Ubuntu 18.04.3 LTS、GeForce GTX 1080 Ti 和三台显示器的 PC 组成。我正在使用 JABRA Evolve 65 耳机（通过 USB 电缆连接到 PC）进行声音输出，在将 Ubuntu 16.04 升级到 18.04（全新安装）后，我无法修复声音问题（在 16.04 中一切正常）。

当我听，比如说一个 Youtube 视频时，我能听到声音，但它正在分解很多，就像它会有很多干扰或什么的。有时声音还可以，比如 2-3 秒，然后它又开始大量破裂。听起来有人会暂停声音，然后很快将其重新打开。也就是说，如果您观看 Youtube 视频并按住空格，这几乎与我的声音问题相同。

我曾尝试在脉冲 daemon.conf 中将默认采样率从 44.1kHz 更改为 48kHz，但这对我没有帮助。

有什么想法我能做什么？谢谢你。

我的计算机设置中有三台显示器，两台插有 HDMI 电缆，一台插有 DisplayPort 电缆。我的问题如下：

当我启动计算机时，所有显示器都启动并正常工作。如果我锁定屏幕一会儿（比如几分钟）然后打开锁定所有屏幕都可以正常工作。但是，如果我锁定屏幕并离开较长时间（例如 15-30 分钟）然后打开屏幕锁定，则插入 HDMI 电缆的一台显示器无法启动。即使我尝试调整显示设置也没有任何反应。我目前的解决方法是重新启动计算机，然后所有显示器都正常启动。

这个问题的原因可能是什么以及如何解决这个问题？我怀疑这可能与系统在几分钟后关闭屏幕有关。问题是，当我再次尝试激活屏幕时，其中一个屏幕不再启动（HDMI-0）。

如果你需要它，这里是xrandr -q-command 的输出：

Screen 0: minimum 8 x 8, current 6200 x 1920, maximum 32767 x 32767
HDMI-0 connected primary 2560x1440+1080+480 (normal left inverted right x axis y axis) 608mm x 345mm
   3840x2160     30.00 +  29.97    25.00    23.98  
   2560x1440     59.95* 
   1920x1080     60.00    59.94    50.00    29.97    23.97  
   1680x1050     59.95  
   1600x900      60.00  
   1440x900      59.89  
   1280x1024     75.02    60.02  
   1280x800      59.81  
   1280x720      60.00    59.94    50.00  
   1152x864      75.00  
   1024x768      75.03    70.07    60.00  
   800x600       75.00    72.19    60.32    56.25  
   720x576       50.00  
   720x480       59.94  
   640x480       75.00    72.81    59.94  
HDMI-1 connected 1080x1920+0+0 left (normal left inverted right x axis y axis) 527mm x 296mm
   1920x1080     60.00*+  59.94    50.00    60.05    60.00    50.04  
   1600x900      60.00  
   1280x1024     75.02    60.02  
   1280x720      60.00    59.94    50.00  
   1152x864      75.00  
   1024x768      75.03    60.00  
   800x600       75.00    60.32  
   720x576       50.00  
   720x480       59.94  
   640x480       75.00    59.94    59.93  
DP-0 connected 2560x1440+3640+480 (normal left inverted right x axis y axis) 607mm x 345mm
   3840x2160     60.00 +  30.00  
   2560x1440     59.95* 
   1920x1080     60.00    59.94  
   1680x1050     59.95  
   1600x900      60.00  
   1440x900      59.89  
   1280x1024     75.02    60.02  
   1280x800      59.81  
   1280x720      60.00  
   1152x864      75.00  
   1024x768      75.03    70.07    60.00  
   800x600       75.00    72.19    60.32    56.25  
   640x480       75.00    72.81    59.94  
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)

问题显示器是带有“HDMI-0”标签的显示器。

我在一个市政府工作，整个机构都在使用 Windows。我们机构的人们使用计算机主要是为了浏览互联网和使用 MS Excel 或 Word。我正在考虑建议我们更改为 GNU/Linux 操作系统，例如 Ubuntu。（主要是因为我认为使用 Microsoft 系统的年度许可费用在市政府的预算中占了很大一部分。）

大型组织可以从 Windows 切换到 Ubuntu 吗？（是否可行，会省钱吗？我该如何证明这一点？）

PS 我所在机构的人们提出的一个担忧是，我们需要安全的操作系统，而 Ubuntu 不够安全。他们认为因为 Ubuntu 是开源的，所以它不够安全？