[arch-general] System crash troubleshooting help?
Good evening all, I was just watching Linux Sucks (https://www.youtube.com/watch?v=5pOxlazS3zs) on Youtube when my system froze. It was the whole system, I could for example not switch to a TTY. The audio was looping a one second thing. My troubleshooting skills are no pride to me, so I though I could just ask you for help. These are the last entries in the journal (in reverse). Did my system just crash because of a DHCP request? Or should I focus on the kwin error, which is the very last one? I will probably not be available to answer to anything during the next 20 hours. -- Vänligen, Aron Widforss ---- Jan 06 22:31:19 hostname kwin_x11[899]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 4113, resource id: 2097154, major code: 18 (ChangeProperty), minor code: 0 Jan 06 22:31:19 hostname systemd[1]: Started Network Manager Script Dispatcher Service. Jan 06 22:31:19 hostname dbus[635]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Jan 06 22:31:19 hostname kdeinit5[864]: networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "Metered" Jan 06 22:31:19 hostname systemd[1]: Starting Network Manager Script Dispatcher Service... Jan 06 22:31:19 hostname dbus[635]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Jan 06 22:31:19 hostname NetworkManager[637]: <info> (wlp2s0): Activation: successful, device activated. Jan 06 22:31:19 hostname NetworkManager[637]: <info> Policy set 'ssid' (wlp2s0) as default for IPv4 routing and DNS. Jan 06 22:31:19 hostname NetworkManager[637]: <info> NetworkManager state is now CONNECTED_GLOBAL Jan 06 22:31:19 hostname dhclient[1074]: bound to 192.168.1.10 -- renewal in 37620 seconds. Jan 06 22:31:19 hostname NetworkManager[637]: <info> NetworkManager state is now CONNECTED_LOCAL Jan 06 22:31:19 hostname NetworkManager[637]: <info> (wlp2s0): device state change: secondaries -> activated (reason 'none') [90 100 0] Jan 06 22:31:19 hostname NetworkManager[637]: <info> (wlp2s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0] Jan 06 22:31:19 hostname NetworkManager[637]: <info> (wlp2s0): device state change: ip-config -> ip-check (reason 'none') [70 80 0] Jan 06 22:31:19 hostname NetworkManager[637]: <info> (wlp2s0): DHCPv4 state changed unknown -> bound Jan 06 22:31:19 hostname NetworkManager[637]: <info> nameserver '192.168.1.1' Jan 06 22:31:19 hostname NetworkManager[637]: <info> lease time 86400 Jan 06 22:31:19 hostname NetworkManager[637]: <info> server identifier 192.168.1.1 Jan 06 22:31:19 hostname NetworkManager[637]: <info> gateway 192.168.1.1 Jan 06 22:31:19 hostname NetworkManager[637]: <info> plen 24 (255.255.255.0) Jan 06 22:31:19 hostname NetworkManager[637]: <info> address 192.168.1.10 Jan 06 22:31:19 hostname dhclient[1074]: DHCPACK from 192.168.1.1 Jan 06 22:31:19 hostname dhclient[1074]: DHCPOFFER from 192.168.1.1 Jan 06 22:31:19 hostname dhclient[1074]: DHCPREQUEST on wlp2s0 to 255.255.255.255 port 67 Jan 06 22:31:18 hostname dhclient[1074]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 3 Jan 06 22:31:18 hostname NetworkManager[637]: <info> (wlp2s0): DHCPv4 state changed expire -> unknown Jan 06 22:31:18 hostname NetworkManager[637]: <info> (wlp2s0): DHCPv4 state changed unknown -> expire Jan 06 22:31:18 hostname kernel: ll header: 00000000: ff ff ff ff ff ff e0 91 f5 7a fe 9a 08 00 .........z.... Jan 06 22:31:18 hostname kernel: IPv4: martian source 255.255.255.255 from 192.168.1.1, on dev wlp2s0 Jan 06 22:31:18 hostname dhclient[1074]: DHCPNAK from 192.168.1.1 Jan 06 22:31:18 hostname dhclient[1074]: DHCPREQUEST on wlp2s0 to 255.255.255.255 port 67
participants (6)
-
Aron Widforss
-
Christopher Mullins
-
Jonathan Horacio Villatoro Córdoba
-
Mauro Santos
-
Michał Zegan
-
Shridhar Daithankar