Приложение неожиданно аварийно завершает работу

Это мой компьютер на работе. Это рабочая станция Dell Precision 3630 в корпусе Tower. Когда мы купили его, изначально он поставлялся с одним SSD-накопителем емкостью 256 ГБ + 1 ТБ жесткого диска. У меня был установлен Kubuntu 18.04 с root на ssd и / home на HD.

Проблема, с которой я сталкиваюсь, связана с любым открытым приложением, вероятность того, что оно выйдет из строя каждые 20 минут, составляет около 20%. Я использую в основном код Visual Studio (код VS) на нем, и буквально каждые 20-40 минут редактор перестает отвечать, и мне приходится ждать, пока он не скажет повторно открыть или выйти (я не теряю файлы / несохраненные данные в этой программе ). Я считаю, что код VS порождает несколько процессов, и только один из них дает сбой, так как я все еще могу щелкнуть по строке меню. Кроме того, разные окна не вылетают. Просто ничего внутри разбитого окна не отвечает.

Эта проблема не является исключительной для кода VS, Google Chrome и других рабочих приложений дает сбой и полностью исчезает. Кроме того, время от времени появляется уведомление о том, что соединение Ethernet отключено, а затем снова подключено через 1 секунду. Интернет не теряется.

Я подумал, что проблема может быть в плазме KDE 5 (поскольку я использовал ее впервые), поэтому я установил Gnome, и проблема была той же. Также обратите внимание, что у меня на этом ПК 32 ГБ ОЗУ (с 4 ГБ подкачки), поэтому нехватка памяти никогда не является проблемой.

Я сделал следующее, и все они потерпели неудачу (в основном аппаратно):

  • Я установил более новое ядро ​​(5.7), и проблема все еще оставалась той же.
  • Я удалил ssd и hd, установил новый ssd емкостью 1 ТБ и с нуля установил Kubuntu 20.04 (root и / home в одном разделе). Та же проблема.
  • Я провел тест памяти с помощью memtest86 ( https://www.memtest86.com/ ). Никаких проблем за 2 часа работы (Также проверено еще раз в диагностических инструментах)
  • Имеется встроенный самотест (BIST) с блоком питания. Я это тестировал. Без вопросов.
  • Я запустил диагностические инструменты, входящие в BIOS. Он тестирует CPU / GPU / память / сетевую карту / HD / шину PCIe / кабели / вентиляторы с помощью различных стресс-тестов. Без вопросов.

Сообщается, что ПК поддерживает Linux (мы купили его с предустановленной Ubuntu 18.04). У меня также есть последняя версия прошивки BIOS для этого ПК (сбросьте ее тоже) и последняя версия прошивки для нового SSD (Samsung 860 EVO емкостью 1 ТБ).

Я не уверен, что вызывает эту проблему, и перепробовал почти все, не намекая на причину. Любые предложения о том, как решить эту проблему. Ниже приведена ссылка на журналы из / var / log / syslog за 1 час, где код VS сбой один раз и подключение к локальной сети перезапустилось дважды (имя / IP-адрес изменено по соображениям конфиденциальности)

журналы

Характеристики:

  • ЦП: Intel Core i7-8700 @ 3,20 ГГц, 6 ядер, 12 логических
  • ОЗУ: 2x16 ГБ (2666 МГц)
  • Графический процессор: AMD Radeon Pro WX 2100

Редактировать: VS Code потерпел крах 5 минут назад. Вот результат journalctl за последние 5 минут.

-- Logs begin at Fri 2020-07-17 20:41:33 EDT, end at Sun 2020-07-26 17:23:31 EDT. --
Jul 26 17:18:55 PC1-Linux1 systemd[1]: Starting Message of the Day...
Jul 26 17:18:55 PC1-Linux1 systemd[1]: motd-news.service: Succeeded.
Jul 26 17:18:55 PC1-Linux1 systemd[1]: Finished Message of the Day.
Jul 26 17:22:38 PC1-Linux1 kernel: traps: code[1671] general protection fault ip:55dacd92bda9 sp:7ffdef785fe0 error:0 in code[55dacc0bb000+51c7000]
Jul 26 17:23:28 PC1-Linux1 sudo[3151]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory
Jul 26 17:23:31 PC1-Linux1 sudo[3151]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory
Jul 26 17:23:31 PC1-Linux1 sudo[3151]: user1 : TTY=pts/2 ; PWD=/home/user1 ; USER=root ; COMMAND=/usr/bin/journalctl --since=-5 minutes
Jul 26 17:23:31 PC1-Linux1 sudo[3151]: pam_unix(sudo:session): session opened for user root by (uid=0)

Edit2: LAN-соединение тоже разорвалось. Добавление вывода journalctl за последние 5 минут

Jul 26 17:36:49 PC1-Linux1 sudo[3469]: pam_unix(sudo:session): session closed for user root
Jul 26 17:40:12 PC1-Linux1 NetworkManager[704]: <error> [1595799612.7782] dhcp4 (eno1): error -113 dispatching events
Jul 26 17:40:12 PC1-Linux1 NetworkManager[704]: <info>  [1595799612.7782] dhcp4 (eno1): state changed bound -> fail
Jul 26 17:40:12 PC1-Linux1 NetworkManager[704]: <info>  [1595799612.7783] device (eno1): DHCPv4: trying to acquire a new lease within 90 seconds
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6503] device (eno1): DHCPv4: grace period expired
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6504] device (eno1): state change: activated -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <warn>  [1595799702.6548] device (eno1): Activation: failed for connection 'Wired connection 1'
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6559] manager: NetworkManager state is now CONNECTED_LOCAL
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6562] device (eno1): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jul 26 17:41:42 PC1-Linux1 avahi-daemon[698]: Withdrawing address record for MAC_REMOVED on eno1.
Jul 26 17:41:42 PC1-Linux1 avahi-daemon[698]: Leaving mDNS multicast group on interface eno1.IPv6 with address MAC_REMOVED.
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6568] dhcp4 (eno1): canceled DHCP transaction
Jul 26 17:41:42 PC1-Linux1 avahi-daemon[698]: Interface eno1.IPv6 no longer relevant for mDNS.
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6568] dhcp4 (eno1): state changed fail -> done
Jul 26 17:41:42 PC1-Linux1 avahi-daemon[698]: Withdrawing address record for REMOVED_IP51 on eno1.
Jul 26 17:41:42 PC1-Linux1 avahi-daemon[698]: Leaving mDNS multicast group on interface eno1.IPv4 with address REMOVED_IP51.
Jul 26 17:41:42 PC1-Linux1 avahi-daemon[698]: Interface eno1.IPv4 no longer relevant for mDNS.
Jul 26 17:41:42 PC1-Linux1 dbus-daemon[702]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.10' (uid=0 pid=704 comm="/usr/sbin/NetworkManager --no-daemon " label="unc>
Jul 26 17:41:42 PC1-Linux1 systemd[1]: Starting Network Manager Script Dispatcher Service...
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6629] policy: auto-activating connection 'Wired connection 1' (80d4d697-a540-3f51-9017-549c2ae2ce5b)
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6639] device (eno1): Activation: starting connection 'Wired connection 1' (80d4d697-a540-3f51-9017-549c2ae2ce5b)
Jul 26 17:41:42 PC1-Linux1 avahi-daemon[698]: Joining mDNS multicast group on interface eno1.IPv6 with address MAC_REMOVED.
Jul 26 17:41:42 PC1-Linux1 whoopsie[1011]: [17:41:42] Cannot reach: https://daisy.ubuntu.com
Jul 26 17:41:42 PC1-Linux1 whoopsie[1011]: [17:41:42] offline
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6640] device (eno1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jul 26 17:41:42 PC1-Linux1 avahi-daemon[698]: New relevant interface eno1.IPv6 for mDNS.
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6642] manager: NetworkManager state is now CONNECTING
Jul 26 17:41:42 PC1-Linux1 avahi-daemon[698]: Registering new address record for MAC_REMOVED on eno1.*.
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6644] device (eno1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jul 26 17:41:42 PC1-Linux1 dbus-daemon[702]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6649] device (eno1): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6651] dhcp4 (eno1): activation: beginning transaction (timeout in 45 seconds)
Jul 26 17:41:42 PC1-Linux1 systemd[1]: Started Network Manager Script Dispatcher Service.
Jul 26 17:41:42 PC1-Linux1 nm-dispatcher[3535]: run-parts: failed to stat component /etc/network/if-post-down.d/avahi-daemon: No such file or directory
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6713] dhcp4 (eno1): option dhcp_lease_time      => '3600'
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6713] dhcp4 (eno1): option domain_name          => 'REMOVED_DOMAIN'
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6713] dhcp4 (eno1): option domain_name_servers  => 'REMOVED_IP2 REMOVED_IP1'
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6713] dhcp4 (eno1): option expiry               => '1595803302'
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6713] dhcp4 (eno1): option host_name            => 'user1_e4b97af22165'
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6713] dhcp4 (eno1): option ip_address           => 'REMOVED_IP51'
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6713] dhcp4 (eno1): option requested_broadcast_address => '1'
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6713] dhcp4 (eno1): option requested_domain_name => '1'
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6713] dhcp4 (eno1): option requested_domain_name_servers => '1'
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6713] dhcp4 (eno1): option requested_domain_search => '1'
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6713] dhcp4 (eno1): option requested_host_name  => '1'
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6713] dhcp4 (eno1): option requested_interface_mtu => '1'
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6713] dhcp4 (eno1): option requested_ms_classless_static_routes => '1'
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6713] dhcp4 (eno1): option requested_nis_domain => '1'
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6713] dhcp4 (eno1): option requested_nis_servers => '1'
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6713] dhcp4 (eno1): option requested_ntp_servers => '1'
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6713] dhcp4 (eno1): option requested_rfc3442_classless_static_routes => '1'
Jul 26 17:41:42 PC1-Linux1 avahi-daemon[698]: Joining mDNS multicast group on interface eno1.IPv4 with address REMOVED_IP51.
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6713] dhcp4 (eno1): option requested_root_path  => '1'
Jul 26 17:41:42 PC1-Linux1 avahi-daemon[698]: New relevant interface eno1.IPv4 for mDNS.
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6713] dhcp4 (eno1): option requested_routers    => '1'
Jul 26 17:41:42 PC1-Linux1 avahi-daemon[698]: Registering new address record for REMOVED_IP51 on eno1.IPv4.
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6713] dhcp4 (eno1): option requested_static_routes => '1'
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6713] dhcp4 (eno1): option requested_subnet_mask => '1'
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6713] dhcp4 (eno1): option requested_time_offset => '1'
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6713] dhcp4 (eno1): option requested_wpad       => '1'
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6714] dhcp4 (eno1): option routers              => 'REMOVED_IP'
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6714] dhcp4 (eno1): option subnet_mask          => 'REMOVED_IP'
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6714] dhcp4 (eno1): state changed unknown -> bound
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6723] device (eno1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jul 26 17:41:42 PC1-Linux1 whoopsie[1011]: [17:41:42] Cannot reach: https://daisy.ubuntu.com
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6736] device (eno1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6738] device (eno1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6740] manager: NetworkManager state is now CONNECTED_LOCAL
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6746] manager: NetworkManager state is now CONNECTED_SITE
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6746] policy: set 'Wired connection 1' (eno1) as default for IPv4 routing and DNS
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6750] device (eno1): Activation: successful, device activated.
Jul 26 17:41:42 PC1-Linux1 NetworkManager[704]: <info>  [1595799702.6752] manager: NetworkManager state is now CONNECTED_GLOBAL
Jul 26 17:41:42 PC1-Linux1 whoopsie[1011]: [17:41:42] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/4
Jul 26 17:41:42 PC1-Linux1 whoopsie[1011]: [17:41:42] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/4
Jul 26 17:41:42 PC1-Linux1 whoopsie[1011]: [17:41:42] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/4
Jul 26 17:41:42 PC1-Linux1 whoopsie[1011]: [17:41:42] online
Jul 26 17:41:42 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:42 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:42 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:42 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:42 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:43 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:43 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:43 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:43 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:43 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:43 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:43 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:43 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:43 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:43 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:43 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:43 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:43 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:43 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:43 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:44 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:44 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:44 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:44 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:44 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:44 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:44 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:45 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:45 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:45 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:45 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:45 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:45 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:45 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:45 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:45 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:45 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:45 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:45 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jul 26 17:41:45 PC1-Linux1 systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.

Вывод free -h

              total        used        free      shared  buff/cache   available
Mem:           31Gi       1.3Gi        28Gi        52Mi       1.5Gi        29Gi
Swap:         2.0Gi          0B       2.0Gi

Вывод sudo lshw -C memory

 *-firmware                
       description: BIOS
       vendor: Dell Inc.
       physical id: 0
       version: 2.5.0
       date: 02/05/2020
       size: 64KiB
       capacity: 32MiB
       capabilities: pci pnp upgrade shadowing cdboot bootselect edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb biosbootspecification netboot uefi
  *-memory
       description: System Memory
       physical id: 9
       slot: System board or motherboard
       size: 32GiB
     *-bank:0
          description: DIMM DDR4 Synchronous 2666 MHz (0.4 ns)
          product: HMA82GU6JJR8N-VK
          vendor: Hynix Semiconductor (Hyundai Electronics)
          physical id: 0
          serial: 72DB71AA
          slot: DIMM1
          size: 16GiB
          width: 64 bits
          clock: 2666MHz (0.4ns)
     *-bank:1
          description: DIMM DDR4 Synchronous 2666 MHz (0.4 ns)
          product: HMA82GU6JJR8N-VK
          vendor: Hynix Semiconductor (Hyundai Electronics)
          physical id: 1
          serial: 72DB71A7
          slot: DIMM2
          size: 16GiB
          width: 64 bits
          clock: 2666MHz (0.4ns)
     *-bank:2
          description: [empty]
          physical id: 2
          slot: DIMM3
     *-bank:3
          description: [empty]
          physical id: 3
          slot: DIMM4
  *-cache:0
       description: L1 cache
       physical id: 14
       slot: L1 Cache
       size: 384KiB
       capacity: 384KiB
       capabilities: synchronous internal write-back unified
       configuration: level=1
  *-cache:1
       description: L2 cache
       physical id: 15
       slot: L2 Cache
       size: 1536KiB
       capacity: 1536KiB
       capabilities: synchronous internal write-back unified
       configuration: level=2
  *-cache:2
       description: L3 cache
       physical id: 16
       slot: L3 Cache
       size: 12MiB
       capacity: 12MiB
       capabilities: synchronous internal write-back unified
       configuration: level=3
  *-memory UNCLAIMED
       description: RAM memory
       product: Cannon Lake PCH Shared SRAM
       vendor: Intel Corporation
       physical id: 14.2
       bus info: pci@0000:00:14.2
       version: 10
       width: 64 bits
       clock: 33MHz (30.3ns)
       capabilities: pm cap_list
       configuration: latency=0
       resources: iomemory:400-3ff iomemory:400-3ff memory:4000114000-4000115fff memory:4000119000-4000119fff

В memtest нет ошибок.Скриншоты: screenshot1 screenshot2 screenshot3

0
задан 27 July 2020 в 23:39

1 ответ

Я связался с Dell, и они прислали мне материнскую плату с процессором на замену. Я думал, что им потребуется много времени, чтобы отправить мне то, что мне нужно, но они были очень быстрыми (то есть на следующий день они отправили их). Я думаю, если вы покупаете у бизнес-подразделения, вы получаете лучший сервис.

Я установил замены, и проблема устранена. Я предполагаю, что проблема в материнской плате или процессоре. У меня все еще есть другие проблемы с перезапуском сетевой карты, но я считаю, что эта проблема не связана и связана с нашей корпоративной сетью.

Также отдельное спасибо @heynnema за помощь в выполнении шагов отладки. Это помогло мне сузить проблему.

0
ответ дан 9 November 2020 в 23:18

Другие вопросы по тегам:

Похожие вопросы: