As mentioned before, I have had a number of times the computer would crash, but not the disaster I went thru a few days ago. This is the symptom: No input from keyboard or mouse affects anything and there is no cursor on screen. Usually two lights on the keyboard will flash. I think numlock and capslock, but not sure it's always those. Is there some file I can look at to try and determine what caused the crash, and if I find it, can it be fixed? Thanx for your expertise--doug
On Sat, 27 Feb 2021 01:56:56 -0500 Doug McGarrett wrote:
Sounds like a kernel panic <https://en.wikipedia.org/wiki/Kernel_panic> The pattern of flashing lights will give the clue as to what went wrong. -- Bob Williams System: Linux 5.3.18-lp152.50-default Desktop: KDE Frameworks: 5.71.0, Qt: 5.12.7 and Plasma: 5.18.5 https://useplaintext.email/
On 27/02/2021 20.29, Doug McGarrett wrote:
As we told you before, on leap you would find it on /var/log/messages (it is a file) and journalctl (it is a command). On Tumbleeweed it is only on journalctl. It is always the same log, for everything, it doesn't change. Take a note of that, please. Run the command "journalctl" on a terminal. But you need the log of the previous session. Instructions in "man journalctl". -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 2/27/21 4:09 PM, Carlos E. R. wrote:
Yes, I had looked at journalctl. It went all the way back to last November! At any rate, for the dates in question, I didn't find a smoking gun, only a bunch of problems. (inodes were regenerated, for one.) I think it would take an expert, or maybe artificial intelligence to decipher this, from about a half million lines--well, maybe a thousand or so, restricting the date. Perhaps an expert would find the smoking gun. I don't know what to do from here. If I have to reinstall the system, it will easily take a week to get it back to where I want it. --doug --doug
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2021-02-27 at 17:58 -0500, Doug McGarrett wrote:
...
Takes practice :-) Ok, now that you found how to look at the log, just find the start of the current boot, which I assume is the boot just after the crash. Well, the dozen lines just before that line are the ones of interest. It is easy. Go to the very end of the journal (press the end key). Then press "?" to search backwards (without the quotes). Type "-- Reboot --" (without the quotes). You might see something like this: ... Aug 09 17:23:15 Telcontar openvpn[31753]: heroes/client.down tun0 1500 1553 192.168.252.185 192.168.252.1 init Aug 09 17:23:15 Telcontar openvpn-client-down[7605]: client-down set empty file /etc/dnsmasq.opensuseservers.conf and reload the dnsmasq service Aug 09 17:23:15 Telcontar openvpn[31753]: SIGTERM[hard,] received, process exiting - -- Reboot -- Feb 14 12:09:44 Telcontar kernel: Linux version 5.3.18-lp152.63-preempt (geeko@buildhost) (gcc version 7.5.0 (SUSE Linux)) #1 SMP PREEMPT Mon Feb 1 17:31:55 UTC 2021 (98caa86) Feb 14 12:09:44 Telcontar kernel: Command line: BOOT_IMAGE=/vmlinuz-5.3.18-lp152.63-preempt root=UUID=ac173013-18ad-4c4e-921e-fd2ecfb56495 resume=/dev/disk/by-label/nvme-swap splash=verbose verbose Feb 14 12:09:44 Telcontar kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' ... As you can see, my journal log is corrupted. On another machine, precissely when it crashed: ... Feb 25 19:46:58 Isengard named[3302]: timed out resolving '255.178.in-addr.arpa/DS/IN': 1.1.1.1#53 Feb 25 20:00:04 Isengard systemd[1]: Started Timeline of Snapper Snapshots. Feb 25 20:00:04 Isengard dbus-daemon[1086]: [system] Activating service name='org.opensuse.Snapper' requested by ':1.3022' (ui> Feb 25 20:00:04 Isengard dbus-daemon[1086]: [system] Successfully activated service 'org.opensuse.Snapper' Feb 25 20:04:22 Isengard smartd[1169]: Device: /dev/disk/by-id/wwn-0x5000c500c4beb480 [SAT], SMART Usage Attribute: 190 Airflo> Feb 25 20:04:22 Isengard smartd[1169]: Device: /dev/disk/by-id/wwn-0x5000c500c4beb480 [SAT], SMART Usage Attribute: 194 Temper> - -- Reboot -- Feb 25 20:27:05 Isengard kernel: microcode: microcode updated early to revision 0x411, date = 2019-04-23 Feb 25 20:27:05 Isengard kernel: Linux version 5.3.18-lp152.63-default (geeko@buildhost) (gcc version 7.5.0 (SUSE Linux)) #1 S> Feb 25 20:27:05 Isengard kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.3.18-lp152.63-default root=UUID=0d457df1-b43d-4587-a> Feb 25 20:27:05 Isengard kernel: x86/fpu: x87 FPU will use FXSAVE Feb 25 20:27:05 Isengard kernel: BIOS-provided physical RAM map: Feb 25 20:27:05 Isengard kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000003efff] usable Feb 25 20:27:05 Isengard kernel: BIOS-e820: [mem 0x000000000003f000-0x000000000003ffff] ACPI NVS Feb 25 20:27:05 Isengard kernel: BIOS-e820: [mem 0x0000000000040000-0x000000000009dfff] usable ... The line "Command line: BOOT_IMAGE=/boot/vmlinuz..." is typical of booting, it is a telltale. The fact that I can not see messages just before "Reboot" about the machine powering down tells me that it is a crash so bad that the machine could not log it. You could search for the word "Panic", you may find it. Hopefully, a message from the kernel telling you to report a bug.
I don't know what to do from here. If I have to reinstall the system, it will easily take a week to get it back to where I want it.
With a "panic" there is little you can gain by reinstalling. - -- Cheers, Carlos E. R. (from openSUSE 15.2 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYDracxwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVul0An2dnyZitkBhbt8gZNa2N GQn7/pYGAJ9S+gWaaCPQVieWFCJEexTXSDr1hA== =cx6y -----END PGP SIGNATURE-----
On Sat, 27 Feb 2021 01:56:56 -0500 Doug McGarrett wrote:
Sounds like a kernel panic <https://en.wikipedia.org/wiki/Kernel_panic> The pattern of flashing lights will give the clue as to what went wrong. -- Bob Williams System: Linux 5.3.18-lp152.50-default Desktop: KDE Frameworks: 5.71.0, Qt: 5.12.7 and Plasma: 5.18.5 https://useplaintext.email/
On 27/02/2021 20.29, Doug McGarrett wrote:
As we told you before, on leap you would find it on /var/log/messages (it is a file) and journalctl (it is a command). On Tumbleeweed it is only on journalctl. It is always the same log, for everything, it doesn't change. Take a note of that, please. Run the command "journalctl" on a terminal. But you need the log of the previous session. Instructions in "man journalctl". -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 2/27/21 4:09 PM, Carlos E. R. wrote:
Yes, I had looked at journalctl. It went all the way back to last November! At any rate, for the dates in question, I didn't find a smoking gun, only a bunch of problems. (inodes were regenerated, for one.) I think it would take an expert, or maybe artificial intelligence to decipher this, from about a half million lines--well, maybe a thousand or so, restricting the date. Perhaps an expert would find the smoking gun. I don't know what to do from here. If I have to reinstall the system, it will easily take a week to get it back to where I want it. --doug --doug
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2021-02-27 at 17:58 -0500, Doug McGarrett wrote:
...
Takes practice :-) Ok, now that you found how to look at the log, just find the start of the current boot, which I assume is the boot just after the crash. Well, the dozen lines just before that line are the ones of interest. It is easy. Go to the very end of the journal (press the end key). Then press "?" to search backwards (without the quotes). Type "-- Reboot --" (without the quotes). You might see something like this: ... Aug 09 17:23:15 Telcontar openvpn[31753]: heroes/client.down tun0 1500 1553 192.168.252.185 192.168.252.1 init Aug 09 17:23:15 Telcontar openvpn-client-down[7605]: client-down set empty file /etc/dnsmasq.opensuseservers.conf and reload the dnsmasq service Aug 09 17:23:15 Telcontar openvpn[31753]: SIGTERM[hard,] received, process exiting - -- Reboot -- Feb 14 12:09:44 Telcontar kernel: Linux version 5.3.18-lp152.63-preempt (geeko@buildhost) (gcc version 7.5.0 (SUSE Linux)) #1 SMP PREEMPT Mon Feb 1 17:31:55 UTC 2021 (98caa86) Feb 14 12:09:44 Telcontar kernel: Command line: BOOT_IMAGE=/vmlinuz-5.3.18-lp152.63-preempt root=UUID=ac173013-18ad-4c4e-921e-fd2ecfb56495 resume=/dev/disk/by-label/nvme-swap splash=verbose verbose Feb 14 12:09:44 Telcontar kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' ... As you can see, my journal log is corrupted. On another machine, precissely when it crashed: ... Feb 25 19:46:58 Isengard named[3302]: timed out resolving '255.178.in-addr.arpa/DS/IN': 1.1.1.1#53 Feb 25 20:00:04 Isengard systemd[1]: Started Timeline of Snapper Snapshots. Feb 25 20:00:04 Isengard dbus-daemon[1086]: [system] Activating service name='org.opensuse.Snapper' requested by ':1.3022' (ui> Feb 25 20:00:04 Isengard dbus-daemon[1086]: [system] Successfully activated service 'org.opensuse.Snapper' Feb 25 20:04:22 Isengard smartd[1169]: Device: /dev/disk/by-id/wwn-0x5000c500c4beb480 [SAT], SMART Usage Attribute: 190 Airflo> Feb 25 20:04:22 Isengard smartd[1169]: Device: /dev/disk/by-id/wwn-0x5000c500c4beb480 [SAT], SMART Usage Attribute: 194 Temper> - -- Reboot -- Feb 25 20:27:05 Isengard kernel: microcode: microcode updated early to revision 0x411, date = 2019-04-23 Feb 25 20:27:05 Isengard kernel: Linux version 5.3.18-lp152.63-default (geeko@buildhost) (gcc version 7.5.0 (SUSE Linux)) #1 S> Feb 25 20:27:05 Isengard kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.3.18-lp152.63-default root=UUID=0d457df1-b43d-4587-a> Feb 25 20:27:05 Isengard kernel: x86/fpu: x87 FPU will use FXSAVE Feb 25 20:27:05 Isengard kernel: BIOS-provided physical RAM map: Feb 25 20:27:05 Isengard kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000003efff] usable Feb 25 20:27:05 Isengard kernel: BIOS-e820: [mem 0x000000000003f000-0x000000000003ffff] ACPI NVS Feb 25 20:27:05 Isengard kernel: BIOS-e820: [mem 0x0000000000040000-0x000000000009dfff] usable ... The line "Command line: BOOT_IMAGE=/boot/vmlinuz..." is typical of booting, it is a telltale. The fact that I can not see messages just before "Reboot" about the machine powering down tells me that it is a crash so bad that the machine could not log it. You could search for the word "Panic", you may find it. Hopefully, a message from the kernel telling you to report a bug.
I don't know what to do from here. If I have to reinstall the system, it will easily take a week to get it back to where I want it.
With a "panic" there is little you can gain by reinstalling. - -- Cheers, Carlos E. R. (from openSUSE 15.2 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYDracxwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVul0An2dnyZitkBhbt8gZNa2N GQn7/pYGAJ9S+gWaaCPQVieWFCJEexTXSDr1hA== =cx6y -----END PGP SIGNATURE-----
participants (4)
-
Bob Williams -
Carlos E. R. -
DennisG -
Doug McGarrett