Зависаем

Imperio · #1

И снова здравствуйте

Пытался создать другую тему по другому поводу. Но во время сбора информации inxi -Fxz отвалилась сеть. После перезагрузки попробовал еще раз, система виснет. При запуске hw-probe тоже зависает.
Я конечно в логи не очень умею, но вроде ничего критичного не нашел.
Ноут все тот же, будь он неладен, MSI PE70 6QE-063XRU

imperio@imperio-msi-mint:~$ tail -100 /var/log/boot.log
Starting Tell Plymouth To Write Out Runtime Data...
Starting Set console font and keymap...
Starting Create Volatile Files and Directories...
Starting LSB: AppArmor initialization...
[ OK ] Started Clean up any mess left by 0dns-up.
Starting Nameserver information manager...
Mounting Arbitrary Executable File Formats File System...
[ OK ] Started Create Volatile Files and Directories.
Starting Update UTMP about System Boot/Shutdown...
[ OK ] Reached target System Time Synchronized.
[ OK ] Started Tell Plymouth To Write Out Runtime Data.
[ OK ] Mounted Arbitrary Executable File Formats File System.
[ OK ] Started Nameserver information manager.
[ OK ] Started Enable support for additional executable binary formats.
[ OK ] Started Update UTMP about System Boot/Shutdown.
[ OK ] Reached target Network (Pre).
[ OK ] Started Set console font and keymap.
[ OK ] Created slice system-getty.slice.
[ OK ] Started LSB: AppArmor initialization.
[ OK ] Reached target System Initialization.
[ OK ] Listening on ACPID Listen Socket.
[ OK ] Started ACPI Events Check.
[ OK ] Listening on D-Bus System Message Bus Socket.
[ OK ] Started Daily apt download activities.
[ OK ] Listening on CUPS Scheduler.
[ OK ] Listening on UUID daemon activation socket.
[ OK ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
Starting Console System Startup Logging...
[ OK ] Started Daily apt upgrade and clean activities.
[ OK ] Started CUPS Scheduler.
[ OK ] Reached target Paths.
[ OK ] Reached target Sockets.
[ OK ] Reached target Basic System.
Starting Initialize hardware monitoring sensors...
Starting Detect the available GPUs and deal with any system changes...
Starting Permit User Sessions...
[ OK ] Started mintsystem.service.
Starting System Logging Service...
Starting IIO Sensor Proxy service...
[ OK ] Started Self Monitoring and Reporting Technology (SMART) Daemon.
Starting Thermal Daemon Service...
[ OK ] Started Cgroup management daemon.
Starting LSB: Speech Dispatcher...
[ OK ] Started ACPI event daemon.
Starting Avahi mDNS/DNS-SD Stack...
Starting Bluetooth service...
Starting Login Service...
Starting LSB: Set the CPU Frequency Scaling governor to "ondemand"...
Starting Restore /etc/resolv.conf if the system crashed before the ppp link was shut down...
Starting LSB: Load kernel modules needed to enable cpufreq scaling...
[ OK ] Started CUPS Scheduler.
Starting LSB: Record successful boot for GRUB...
Starting LSB: automatic crash report generation...
[ OK ] Started Regular background program processing daemon.
Starting LSB: daemon to balance interrupts for SMP systems...
[ OK ] Started Run anacron jobs.
Starting Accounts Service...
Starting Save/Restore Sound Card State...
Starting Modem Manager...
[ OK ] Started D-Bus System Message Bus.
[ OK ] Started Bluetooth service.
[ OK ] Started Thermal Daemon Service.
[ OK ] Started Avahi mDNS/DNS-SD Stack.
[ OK ] Started Make remote CUPS printers available locally.
[ OK ] Reached target Bluetooth.
Starting Network Manager...
[ OK ] Started Daily Cleanup of Temporary Directories.
[ OK ] Reached target Timers.
Starting Raise network interfaces...
[ OK ] Started System Logging Service.
[ OK ] Started Console System Startup Logging.
[ OK ] Started Detect the available GPUs and deal with any system changes.
[ OK ] Started Permit User Sessions.
[ OK ] Started IIO Sensor Proxy service.
[ OK ] Started Restore /etc/resolv.conf if the system crashed before the ppp link was shut down.
[ OK ] Started Initialize hardware monitoring sensors.
[ OK ] Started Save/Restore Sound Card State.
[ OK ] Started LSB: Speech Dispatcher.
[ OK ] Started LSB: Set the CPU Frequency Scaling governor to "ondemand".
[ OK ] Started LSB: automatic crash report generation.
[ OK ] Started LSB: daemon to balance interrupts for SMP systems.
[ OK ] Started LSB: Record successful boot for GRUB.
[ OK ] Started Login Service.
Starting Hostname Service...
Starting Authenticate and Authorize Users to Run Privileged Tasks...
Starting Light Display Manager...
[ OK ] Started Network Manager.
Starting Network Manager Wait Online...
[ OK ] Started LSB: Load kernel modules needed to enable cpufreq scaling.
Starting LSB: set CPUFreq kernel parameters...
Starting Network Manager Script Dispatcher Service...
[ OK ] Started Raise network interfaces.
[ OK ] Reached target Network.
Starting OpenVPN service...
[ OK ] Started LSB: set CPUFreq kernel parameters.
[ OK ] Started OpenVPN service.
[ OK ] Started Authenticate and Authorize Users to Run Privileged Tasks.
[ OK ] Started Network Manager Script Dispatcher Service.
[ OK ] Started Accounts Service.
[ OK ] Started Hostname Service.

imperio@imperio-msi-mint:~$ tail -f /var/log/dmesg
(Nothing has been logged yet.)

imperio@imperio-msi-mint:~$ tail -f /var/log/dpkg.log
2018-02-15 22:29:53 startup packages configure
2018-02-15 22:29:54 startup archives install
2018-02-15 22:29:54 install hw-probe:all <нет> 1.3-2
2018-02-15 22:29:54 status half-installed hw-probe:all 1.3-2
2018-02-15 22:29:54 status unpacked hw-probe:all 1.3-2
2018-02-15 22:29:54 status unpacked hw-probe:all 1.3-2
2018-02-15 22:29:54 configure hw-probe:all 1.3-2 1.3-2
2018-02-15 22:29:54 status unpacked hw-probe:all 1.3-2
2018-02-15 22:29:54 status half-configured hw-probe:all 1.3-2
2018-02-15 22:29:54 status installed hw-probe:all 1.3-2

imperio@imperio-msi-mint:~$ tail -f /var/log/faillog
^C

imperio@imperio-msi-mint:~$ tail -100 /var/log/kern.log
Feb 15 22:31:06 imperio-msi-mint NetworkManager[1077]: <info> [1518723066.2647] Loaded device plugin: NMBridgeFactory (internal)
Feb 15 22:31:06 imperio-msi-mint NetworkManager[1077]: <info> [1518723066.2647] Loaded device plugin: NMBondFactory (internal)
Feb 15 22:31:06 imperio-msi-mint NetworkManager[1077]: <info> [1518723066.2674] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wifi.so)
Feb 15 22:31:06 imperio-msi-mint NetworkManager[1077]: <info> [1518723066.2698] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-adsl.so)
Feb 15 22:31:06 imperio-msi-mint NetworkManager[1077]: <info> [1518723066.2752] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wwan.so)
Feb 15 22:31:06 imperio-msi-mint NetworkManager[1077]: <info> [1518723066.2793] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
Feb 15 22:31:06 imperio-msi-mint NetworkManager[1077]: <info> [1518723066.2803] (wlp2s0): using nl80211 for WiFi device control
Feb 15 22:31:06 imperio-msi-mint NetworkManager[1077]: <info> [1518723066.2813] device (wlp2s0): driver supports Access Point (AP) mode
Feb 15 22:31:06 imperio-msi-mint NetworkManager[1077]: <info> [1518723066.2821] manager: (wlp2s0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/0)
Feb 15 22:31:06 imperio-msi-mint NetworkManager[1077]: <info> [1518723066.2831] device (wlp2s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Feb 15 22:31:06 imperio-msi-mint kernel: [ 4.719851] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Feb 15 22:31:06 imperio-msi-mint NetworkManager[1077]: <info> [1518723066.3870] manager: (enp3s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/1)
Feb 15 22:31:06 imperio-msi-mint kernel: [ 4.822226] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Feb 15 22:31:06 imperio-msi-mint NetworkManager[1077]: <info> [1518723066.3889] keyfile: add connection in-memory (726d740d-081b-3817-811e-76d6bde72e22,"Проводное соединение 1")
Feb 15 22:31:06 imperio-msi-mint NetworkManager[1077]: <info> [1518723066.3893] settings: (enp3s0): created default wired connection 'Проводное соединение 1'
Feb 15 22:31:06 imperio-msi-mint NetworkManager[1077]: <info> [1518723066.3899] device (enp3s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Feb 15 22:31:06 imperio-msi-mint NetworkManager[1077]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
Feb 15 22:31:06 imperio-msi-mint NetworkManager[1077]: <info> [1518723066.3914] device (lo): link connected
Feb 15 22:31:06 imperio-msi-mint kernel: [ 4.826779] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
Feb 15 22:31:06 imperio-msi-mint kernel: [ 4.827188] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
Feb 15 22:31:06 imperio-msi-mint NetworkManager[1077]: <info> [1518723066.3919] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/2)
Feb 15 22:31:06 imperio-msi-mint NetworkManager[1077]: <info> [1518723066.3960] urfkill disappeared from the bus
Feb 15 22:31:06 imperio-msi-mint NetworkManager[1077]: <info> [1518723066.3980] bluez: use BlueZ version 5
Feb 15 22:31:06 imperio-msi-mint NetworkManager[1077]: <info> [1518723066.3993] ofono is now available
Feb 15 22:31:06 imperio-msi-mint NetworkManager[1077]: <warn> [1518723066.3997] failed to enumerate oFono devices: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files
Feb 15 22:31:06 imperio-msi-mint NetworkManager[1077]: <info> [1518723066.4000] ModemManager available in the bus
Feb 15 22:31:06 imperio-msi-mint NetworkManager[1077]: <info> [1518723066.4143] supplicant: wpa_supplicant running
Feb 15 22:31:06 imperio-msi-mint NetworkManager[1077]: <info> [1518723066.4144] device (wlp2s0): supplicant interface state: init -> starting
Feb 15 22:31:06 imperio-msi-mint NetworkManager[1077]: <info> [1518723066.4707] device (wlp2s0): supplicant interface state: starting -> ready
Feb 15 22:31:06 imperio-msi-mint NetworkManager[1077]: <info> [1518723066.4708] device (wlp2s0): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Feb 15 22:31:06 imperio-msi-mint kernel: [ 4.907449] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Feb 15 22:31:10 imperio-msi-mint NetworkManager[1077]: <info> [1518723070.0932] device (wlp2s0): supplicant interface state: ready -> inactive
Feb 15 22:31:10 imperio-msi-mint NetworkManager[1077]: <info> [1518723070.0944] policy: auto-activating connection 'Keenetic-4G-MTS'
Feb 15 22:31:10 imperio-msi-mint NetworkManager[1077]: <info> [1518723070.0953] device (wlp2s0): Activation: starting connection 'Keenetic-4G-MTS' (8ce9271c-91ae-4bc9-a2e3-16a83567a9e6)
Feb 15 22:31:10 imperio-msi-mint NetworkManager[1077]: <info> [1518723070.0955] device (wlp2s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Feb 15 22:31:10 imperio-msi-mint NetworkManager[1077]: <info> [1518723070.0956] manager: NetworkManager state is now CONNECTING
Feb 15 22:31:10 imperio-msi-mint NetworkManager[1077]: <info> [1518723070.0961] device (wlp2s0): state change: prepare -> config (reason 'none') [40 50 0]
Feb 15 22:31:10 imperio-msi-mint NetworkManager[1077]: <info> [1518723070.0962] device (wlp2s0): Activation: (wifi) access point 'Keenetic-4G-MTS' has security, but secrets are required.
Feb 15 22:31:10 imperio-msi-mint NetworkManager[1077]: <info> [1518723070.0962] device (wlp2s0): state change: config -> need-auth (reason 'none') [50 60 0]
Feb 15 22:31:10 imperio-msi-mint NetworkManager[1077]: <info> [1518723070.1019] device (wlp2s0): state change: need-auth -> prepare (reason 'none') [60 40 0]
Feb 15 22:31:10 imperio-msi-mint NetworkManager[1077]: <info> [1518723070.1023] device (wlp2s0): state change: prepare -> config (reason 'none') [40 50 0]
Feb 15 22:31:10 imperio-msi-mint NetworkManager[1077]: <info> [1518723070.1025] device (wlp2s0): Activation: (wifi) connection 'Keenetic-4G-MTS' has security, and secrets exist. No new secrets needed.
Feb 15 22:31:10 imperio-msi-mint NetworkManager[1077]: <info> [1518723070.1026] Config: added 'ssid' value 'Keenetic-4G-MTS'
Feb 15 22:31:10 imperio-msi-mint NetworkManager[1077]: <info> [1518723070.1026] Config: added 'scan_ssid' value '1'
Feb 15 22:31:10 imperio-msi-mint NetworkManager[1077]: <info> [1518723070.1026] Config: added 'key_mgmt' value 'WPA-PSK'
Feb 15 22:31:10 imperio-msi-mint NetworkManager[1077]: <info> [1518723070.1026] Config: added 'auth_alg' value 'OPEN'
Feb 15 22:31:10 imperio-msi-mint NetworkManager[1077]: <info> [1518723070.1026] Config: added 'psk' value '<omitted>'
Feb 15 22:31:10 imperio-msi-mint NetworkManager[1077]: <info> [1518723070.1032] sup-iface[0x2328a00,wlp2s0]: config: set interface ap_scan to 1
Feb 15 22:31:10 imperio-msi-mint kernel: [ 9.432318] wlp2s0: authenticate with 04:bf:6d:04:5c:cc
Feb 15 22:31:11 imperio-msi-mint NetworkManager[1077]: <info> [1518723071.0015] device (wlp2s0): supplicant interface state: inactive -> authenticating
Feb 15 22:31:11 imperio-msi-mint kernel: [ 9.437652] wlp2s0: send auth to 04:bf:6d:04:5c:cc (try 1/3)
Feb 15 22:31:11 imperio-msi-mint kernel: [ 9.446771] wlp2s0: authenticated
Feb 15 22:31:11 imperio-msi-mint kernel: [ 9.448088] wlp2s0: associate with 04:bf:6d:04:5c:cc (try 1/3)
Feb 15 22:31:11 imperio-msi-mint NetworkManager[1077]: <info> [1518723071.0159] device (wlp2s0): supplicant interface state: authenticating -> associating
Feb 15 22:31:11 imperio-msi-mint kernel: [ 9.453420] wlp2s0: RX AssocResp from 04:bf:6d:04:5c:cc (capab=0xc11 status=0 aid=4)
Feb 15 22:31:11 imperio-msi-mint kernel: [ 9.457841] wlp2s0: associated
Feb 15 22:31:11 imperio-msi-mint kernel: [ 9.457857] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
Feb 15 22:31:11 imperio-msi-mint NetworkManager[1077]: <info> [1518723071.0268] device (wlp2s0): supplicant interface state: associating -> associated
Feb 15 22:31:11 imperio-msi-mint NetworkManager[1077]: <info> [1518723071.2205] device (wlp2s0): supplicant interface state: associated -> 4-way handshake
Feb 15 22:31:11 imperio-msi-mint NetworkManager[1077]: <info> [1518723071.2370] device (wlp2s0): supplicant interface state: 4-way handshake -> completed
Feb 15 22:31:11 imperio-msi-mint NetworkManager[1077]: <info> [1518723071.2370] device (wlp2s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'Keenetic-4G-MTS'.
Feb 15 22:31:11 imperio-msi-mint NetworkManager[1077]: <info> [1518723071.2371] device (wlp2s0): state change: config -> ip-config (reason 'none') [50 70 0]
Feb 15 22:31:11 imperio-msi-mint NetworkManager[1077]: <info> [1518723071.2382] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
Feb 15 22:31:11 imperio-msi-mint NetworkManager[1077]: <info> [1518723071.2445] dhcp4 (wlp2s0): dhclient started with pid 1409
Feb 15 22:31:11 imperio-msi-mint kernel: [ 9.948099] nouveau 0000:01:00.0: DRM: evicting buffers...
Feb 15 22:31:11 imperio-msi-mint kernel: [ 9.948100] nouveau 0000:01:00.0: DRM: waiting for kernel channels to go idle...
Feb 15 22:31:11 imperio-msi-mint kernel: [ 9.948113] nouveau 0000:01:00.0: DRM: suspending fence...
Feb 15 22:31:11 imperio-msi-mint kernel: [ 9.950821] nouveau 0000:01:00.0: DRM: suspending object tree...
Feb 15 22:31:11 imperio-msi-mint NetworkManager[1077]: <info> [1518723071.5516] address 192.168.1.45
Feb 15 22:31:11 imperio-msi-mint NetworkManager[1077]: <info> [1518723071.5516] plen 24 (255.255.255.0)
Feb 15 22:31:11 imperio-msi-mint NetworkManager[1077]: <info> [1518723071.5517] gateway 192.168.1.1
Feb 15 22:31:11 imperio-msi-mint NetworkManager[1077]: <info> [1518723071.5517] server identifier 192.168.1.1
Feb 15 22:31:11 imperio-msi-mint NetworkManager[1077]: <info> [1518723071.5517] lease time 25200
Feb 15 22:31:11 imperio-msi-mint NetworkManager[1077]: <info> [1518723071.5517] nameserver '192.168.1.1'
Feb 15 22:31:11 imperio-msi-mint NetworkManager[1077]: <info> [1518723071.5517] dhcp4 (wlp2s0): state changed unknown -> bound
Feb 15 22:31:11 imperio-msi-mint NetworkManager[1077]: <info> [1518723071.5537] device (wlp2s0): state change: ip-config -> ip-check (reason 'none') [70 80 0]
Feb 15 22:31:11 imperio-msi-mint NetworkManager[1077]: <info> [1518723071.5540] device (wlp2s0): state change: ip-check -> secondaries (reason 'none') [80 90 0]
Feb 15 22:31:11 imperio-msi-mint NetworkManager[1077]: <info> [1518723071.5546] device (wlp2s0): state change: secondaries -> activated (reason 'none') [90 100 0]
Feb 15 22:31:11 imperio-msi-mint NetworkManager[1077]: <info> [1518723071.5547] manager: NetworkManager state is now CONNECTED_LOCAL
Feb 15 22:31:11 imperio-msi-mint NetworkManager[1077]: <info> [1518723071.5615] manager: NetworkManager state is now CONNECTED_GLOBAL
Feb 15 22:31:11 imperio-msi-mint NetworkManager[1077]: <info> [1518723071.5616] policy: set 'Keenetic-4G-MTS' (wlp2s0) as default for IPv4 routing and DNS
Feb 15 22:31:11 imperio-msi-mint NetworkManager[1077]: <info> [1518723071.5617] dns-plugin[0x23158d0]: starting dnsmasq...
Feb 15 22:31:11 imperio-msi-mint NetworkManager[1077]: <info> [1518723071.5639] dns-mgr: Writing DNS information to /sbin/resolvconf
Feb 15 22:31:11 imperio-msi-mint NetworkManager[1077]: <info> [1518723071.6098] device (wlp2s0): Activation: successful, device activated.
Feb 15 22:31:11 imperio-msi-mint NetworkManager[1077]: <info> [1518723071.6104] manager: startup complete
Feb 15 22:31:11 imperio-msi-mint NetworkManager[1077]: <info> [1518723071.6124] dnsmasq[0x23158d0]: dnsmasq appeared as :1.24
Feb 15 22:31:11 imperio-msi-mint kernel: [ 10.074374] vboxdrv: loading out-of-tree module taints kernel.
Feb 15 22:31:11 imperio-msi-mint kernel: [ 10.074501] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
Feb 15 22:31:11 imperio-msi-mint kernel: [ 10.077794] vboxdrv: Found 8 processor cores
Feb 15 22:31:11 imperio-msi-mint kernel: [ 10.096481] vboxdrv: TSC mode is Invariant, tentative frequency 2592008771 Hz
Feb 15 22:31:11 imperio-msi-mint kernel: [ 10.096482] vboxdrv: Successfully loaded version 5.0.40_Ubuntu (interface 0x00240000)
Feb 15 22:31:11 imperio-msi-mint kernel: [ 10.100552] VBoxNetFlt: Successfully started.
Feb 15 22:31:11 imperio-msi-mint kernel: [ 10.104161] VBoxNetAdp: Successfully started.
Feb 15 22:31:11 imperio-msi-mint kernel: [ 10.107720] VBoxPciLinuxInit
Feb 15 22:31:11 imperio-msi-mint kernel: [ 10.109557] vboxpci: IOMMU not found (not registered)
Feb 15 22:31:13 imperio-msi-mint kernel: [ 11.970181] Bluetooth: RFCOMM TTY layer initialized
Feb 15 22:31:13 imperio-msi-mint kernel: [ 11.970185] Bluetooth: RFCOMM socket layer initialized
Feb 15 22:31:13 imperio-msi-mint kernel: [ 11.970189] Bluetooth: RFCOMM ver 1.11
Feb 15 22:31:16 imperio-msi-mint NetworkManager[1077]: <info> [1518723076.5648] manager: WiFi hardware radio set enabled
Feb 15 22:31:16 imperio-msi-mint NetworkManager[1077]: <info> [1518723076.5649] manager: WWAN hardware radio set enabled

imperio@imperio-msi-mint:~$ tail -f /var/log/lastlog
^C

imperio@imperio-msi-mint:~$ tail -100 /var/log/syslog
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:change_onexec: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:change_hatv: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:change_hat: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:policy: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:.: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:set_load: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:versions: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:.: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:v7: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:v6: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:v5: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:.features: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:.: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: message repeated 17 times: [ ureadahead:.: Относительный путь пропущен]
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:.replace: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: message repeated 5 times: [ ureadahead:.replace: Относительный путь пропущен]
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:.: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:size: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:start: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:BAT1: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:type: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:ADP1: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:type: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:online: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:cron.daily: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:cron.weekly: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:crontabs: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:cron.monthly: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:size: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:start: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:coresize: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: message repeated 109 times: [ ureadahead:coresize: Относительный путь пропущен]
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:.: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: message repeated 2 times: [ ureadahead:.: Относительный путь пропущен]
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:asus-wireless-on: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:asus-keyboard-backlight-down: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:asus-wireless-off: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:asus-keyboard-backlight-up: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:powerbtn: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:lenovo-undock: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:thinkpad-cmos: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:tosh-wireless: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:ibm-wireless: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:size: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:start: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:.: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:NetworkManager_new.1422: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:.: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: message repeated 18 times: [ ureadahead:.: Относительный путь пропущен]
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:NetworkManager: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: message repeated 2 times: [ ureadahead:NetworkManager: Относительный путь пропущен]
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:multi-user.target.wants: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:multi-user.target.wants: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:coresize: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: message repeated 457 times: [ ureadahead:coresize: Относительный путь пропущен]
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:.xsession-errors: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:.: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:objects: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:tmp: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:config: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:summaries/flathub.sig: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:summaries/flathub: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:flathub.trustedkeys.gpg: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:objects: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:tmp: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:config: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:self/fd: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:self/fd: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:.: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:tmp: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:tmp: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:.: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: message repeated 17 times: [ ureadahead:.: Относительный путь пропущен]
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:tracing_on: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:events/fs/open_exec/enable: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: ureadahead:events/fs/do_sys_open/enable: Относительный путь пропущен
Feb 15 22:31:57 imperio-msi-mint ureadahead[385]: Counted 8 CPUs
Feb 15 22:31:57 imperio-msi-mint systemd[1]: Stopped Read required files in advance.
Feb 15 22:33:07 imperio-msi-mint systemd[1]: Stopping User Manager for UID 108...
Feb 15 22:33:07 imperio-msi-mint systemd[1307]: Reached target Shutdown.
Feb 15 22:33:07 imperio-msi-mint systemd[1307]: Starting Exit the Session...
Feb 15 22:33:07 imperio-msi-mint systemd[1307]: Stopped target Default.
Feb 15 22:33:07 imperio-msi-mint systemd[1307]: Stopped target Basic System.
Feb 15 22:33:07 imperio-msi-mint systemd[1307]: Stopped target Paths.
Feb 15 22:33:07 imperio-msi-mint systemd[1307]: Stopped target Sockets.
Feb 15 22:33:07 imperio-msi-mint systemd[1307]: Stopped target Timers.
Feb 15 22:33:07 imperio-msi-mint systemd[1307]: Received SIGRTMIN+24 from PID 3520 (kill).
Feb 15 22:33:07 imperio-msi-mint systemd[1]: Stopped User Manager for UID 108.
Feb 15 22:33:07 imperio-msi-mint systemd[1]: Removed slice User Slice of lightdm.
Feb 15 22:40:23 imperio-msi-mint ntpd[1520]: 80.93.50.95 local addr 192.168.1.45 -> <null>
Feb 15 22:41:18 imperio-msi-mint ntpd[1520]: 91.189.91.157 local addr 192.168.1.45 -> <null>
Feb 15 22:43:12 imperio-msi-mint ntpd[1520]: 185.68.101.2 local addr 192.168.1.45 -> <null>
Feb 15 22:45:32 imperio-msi-mint ntpd[1520]: 94.247.111.10 local addr 192.168.1.45 -> <null>
Feb 15 22:46:45 imperio-msi-mint systemd[1]: Starting Cleanup of Temporary Directories...
Feb 15 22:46:45 imperio-msi-mint systemd-tmpfiles[4446]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
Feb 15 22:46:45 imperio-msi-mint systemd[1]: Started Cleanup of Temporary Directories.
Feb 15 22:51:43 imperio-msi-mint ntpd[1520]: 91.207.142.242 local addr 192.168.1.45 -> <null>
Feb 15 22:52:16 imperio-msi-mint ntpd[1520]: 195.122.241.236 local addr 192.168.1.45 -> <null>
Feb 15 23:01:07 imperio-msi-mint smartd[992]: Device: /dev/sdb [SAT], SMART Prefailure Attribute: 194 Temperature_Celsius changed from 82 to 92
Feb 15 23:04:42 imperio-msi-mint mate-screensaver-dialog: pam_ecryptfs: seteuid error

Что можно сделать в этой ситуации?

А другую тему хотел создать по поводу того, что при запуске виртуальной машины в virtualbox ОСь тоже вешалась.

Imperio · #2

Решил уже сносить минт и ставить винду, но не успел инициировать загрузку в флэшки. Увидел ошибку при загрузке stuck 22s gpu-manager

Беглый поиск и я смог загрузиться и даже теперь inxi работает. Но при запуске виртуалки все так же виснет.

imperio@imperio-msi-mint:~$ inxi -Fxz
System: Host: imperio-msi-mint Kernel: 4.13.0-32-generic x86_64 (64 bit gcc: 5.4.0)
Desktop: MATE 1.18.0 (Gtk 3.18.9-1ubuntu3.3)
Distro: Linux Mint 18.3 Sylvia
Machine: System: Micro-Star product: PE70 6QE v: REV:1.0
Mobo: Micro-Star model: MS-1795 v: REV:0.A
Bios: American Megatrends v: E1795IMS.11B date: 12/06/2017
CPU: Quad core Intel Core i7-6700HQ (-HT-MCP-) cache: 6144 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 20736
clock speeds: max: 3500 MHz 1: 2600 MHz 2: 2600 MHz 3: 2600 MHz
4: 2600 MHz 5: 2600 MHz 6: 2600 MHz 7: 2600 MHz 8: 2600 MHz
Graphics: Card-1: Intel Skylake Integrated Graphics bus-ID: 00:02.0
Card-2: NVIDIA GM107M [GeForce GTX 960M] bus-ID: 01:00.0
Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa)
Resolution: 1920x1080@60.00hz, 1920x1080@60.00hz
GLX Renderer: Mesa DRI Intel HD Graphics 530 (Skylake GT2)
GLX Version: 3.0 Mesa 17.2.8 Direct Rendering: Yes
Audio: Card Intel Sunrise Point-H HD Audio
driver: snd_hda_intel bus-ID: 00:1f.3
Sound: Advanced Linux Sound Architecture v: k4.13.0-32-generic
Network: Card-1: Intel Wireless 3165 driver: iwlwifi bus-ID: 02:00.0
IF: wlp2s0 state: up mac: <filter>
Card-2: Qualcomm Atheros AR8161 Gigabit Ethernet
driver: alx port: d000 bus-ID: 03:00.0
IF: enp3s0 state: down mac: <filter>
Drives: HDD Total Size: 1496.4GB (4.1% used)
ID-1: /dev/sda model: HGST_HTS721010A9 size: 1000.2GB
ID-2: /dev/sdb model: SPCC_Solid_State size: 480.1GB
ID-3: USB /dev/sdc model: Silicon size: 16.1GB
Partition: ID-1: / size: 30G used: 7.2G (26%) fs: ext4 dev: /dev/sdb1
ID-2: /home size: 407G used: 43G (11%) fs: ext4 dev: /dev/sdb6
ID-3: swap-1 size: 4.09GB used: 0.00GB (0%) fs: swap dev: /dev/sdb5
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 50.0C mobo: 27.8C
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 239 Uptime: 0 min Memory: 722.8/15924.5MB
Init: systemd runlevel: 5 Gcc sys: 5.4.0
Client: Shell (bash 4.3.481) inxi: 2.2.35

https://linux-hardware.org/?probe=2c30f85d6a

imperio@imperio-msi-mint:~$ tail -50 /var/log/gpu-manager.log
Is fglrx kernel module available? no
Is nvidia kernel module available? no
Vendor/Device Id: 8086:191b
BusID "PCI:0@0:2:0"
Is boot vga? yes
Vendor/Device Id: 10de:139b
BusID "PCI:1@0:0:0"
Is boot vga? no
Error: can't access /sys/bus/pci/devices/0000:01:00.0/driver
The device is not bound to any driver. Skipping...
Skipping "/dev/dri/card0", driven by "i915"
Skipping "/dev/dri/card0", driven by "i915"
Skipping "/dev/dri/card0", driven by "i915"
Found "/dev/dri/card0", driven by "i915"
output 0:
card0-HDMI-A-2
output 1:
card0-eDP-1
Number of connected outputs for /dev/dri/card0: 2
Does it require offloading? yes
last cards number = 1
Has amd? no
Has intel? yes
Has nvidia? no
How many cards? 1
Has the system changed? No
main_arch_path x86_64-linux-gnu, other_arch_path i386-linux-gnu
Current alternative: /usr/lib/x86_64-linux-gnu/mesa/ld.so.conf
Current core alternative: (null)
Current egl alternative: /usr/lib/x86_64-linux-gnu/mesa-egl/ld.so.conf
Is nvidia enabled? no
Is nvidia egl enabled? no
Is fglrx enabled? no
Is mesa enabled? yes
Is mesa egl enabled? yes
Is pxpress enabled? no
Is prime enabled? no
Is prime egl enabled? no
Is nvidia available? no
Is nvidia egl available? no
Is fglrx available? no
Is fglrx-core available? no
Is mesa available? yes
Is mesa egl available? yes
Is pxpress available? no
Is prime available? no
Is prime egl available? no
Single card detected
Nothing to do
No change - nothing to do

#3

Imperio, ну ты драйвер на карту ставил? Микрокод в диспетчере драйверов ставил? В биосе включил виртуализацию?

Imperio · #4

На видеокарту ставил, уж не помню что было, но стало только хуже, откатывал потом обратно на nouveau. Интел микрокод установлен. Виртуализация в биосе включена.

Imperio · #5

В общем не будет работать текущая версия виртуалбокса с моим ядром https://bugs.launchpad.net/ubuntu/+sour ... ug/1736116
Насколько понял, теперь нужно или виртуалбокс переустановить с родного репозитория или ядро даунгрейдить.

Imperio · #6

Продолжение тут VirualBox и ядро 4.14

#7

Imperio писал(а): ↑
16 фев 2018, 09:31
Насколько понял, теперь нужно или виртуалбокс переустановить с родного репозитория или ядро даунгрейдить.

Так а почему ты не пишешь, что ставил бокс не из родной репы? Да и зачем его было ставить фик знает откуда? Он и из родных хорошо обновляется.

#8

vir0id, Мне кажется наоборот там должно быть, что вибокс 5.0 из убунтовых реп вешает ось после перехода 16.04 на 4.13
5.1+ судя работает норм, судя по отзывам в багрепорте. Осталось дождаться пока его притащат в xenial-updates, а пока юзать оракловый реп

Imperio · #9

vir0id писал(а): ↑
16 фев 2018, 10:11
Так а почему ты не пишешь, что ставил бокс не из родной репы?

А я не понимаю что откуда ставится. Зашел в менеджер программ да установил. А вот сейчас как раз пытаюсь установить фиг знает откуда.

Imperio · #10

Завелся VirtualBox

Linux imperio-msi-mint 4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25 10:13:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
VirtualBox 5.2.6 r120293 (Qt5.6.1)

#11

Chocobo, ну да, просто сперва

Imperio писал(а): ↑
16 фев 2018, 09:31
Насколько понял, теперь нужно или виртуалбокс переустановить с родного репозитория или ядро даунгрейдить.

потом

Imperio писал(а): ↑
16 фев 2018, 11:10
А я не понимаю что откуда ставится. Зашел в менеджер программ да установил.

ибо

Chocobo писал(а): ↑
16 фев 2018, 10:32
Мне кажется наоборот там должно быть, что вибокс 5.0 из убунтовых реп вешает ось после перехода 16.04 на 4.13

Imperio, что у тебя там за система? Убунту или Минт?

#12

vir0id писал(а): ↑
16 фев 2018, 13:20
из убунтовых реп

В репах минта виртуалбокс не живет. он тащится из xenial)

Код: Выделить всё

▶ apt policy virtualbox              
virtualbox:
  Установлен: (отсутствует)
  Кандидат:   5.0.40-dfsg-0ubuntu1.16.04.2
  Таблица версий:
     5.0.40-dfsg-0ubuntu1.16.04.2 500
        500 http://mirror.logol.ru/ubuntu xenial-updates/multiverse amd64 Packages
     5.0.18-dfsg-2build1 500
        500 http://mirror.logol.ru/ubuntu xenial/multiverse amd64 Packages

#13

Chocobo, извинюсь, затупил

Imperio · #14

vir0id писал(а): ↑
16 фев 2018, 13:20
Imperio, что у тебя там за система? Убунту или Минт?

Mint 18.3 Mate

#15

Imperio, покажи

Код: Выделить всё

cat /proc/cpuinfo

забыл что ты пробу дал

#16

vir0id, У тебя кстати на 4.13 работает?
Исходный-то посыл именно в том, что не хочет вроде у многих

#17

Chocobo, ага.

#18

vir0id, значит не 100% хит в багу в этой связке

#19

Imperio, так что? Тему можно закрывать?

Imperio писал(а): ↑
16 фев 2018, 08:17
Беглый поиск и я смог загрузиться и даже теперь inxi работает. Но при запуске виртуалки все так же виснет.

Imperio писал(а): ↑
16 фев 2018, 11:47
Завелся VirtualBox

Imperio · #20

vir0id писал(а): ↑
16 фев 2018, 13:55
Тему можно закрывать?

Все-равно вешается периодически на разных командах, которые обращаются к железу. Из последнего повис на команде lspci | egrep 'VGA|3D|Display', в ответ ничего не получил и первее всех отваливается сеть видимо, т.к. пропадает инет.

Кто сейчас на конференции