From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id BF34915800F for ; Wed, 15 Feb 2023 14:50:37 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 57D6DE0886; Wed, 15 Feb 2023 14:50:33 +0000 (UTC) Received: from ciao.gmane.io (ciao.gmane.io [116.202.254.214]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 0CBBAE07D3 for ; Wed, 15 Feb 2023 14:50:33 +0000 (UTC) Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1pSJ79-0004Pa-LK for gentoo-user@lists.gentoo.org; Wed, 15 Feb 2023 15:50:31 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: Grant Edwards Subject: [gentoo-user] Re: my 5.15.93 kernel keeps rebooting Date: Wed, 15 Feb 2023 14:50:27 -0000 (UTC) Message-ID: References: User-Agent: slrn/1.0.3 (Linux) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply X-Archives-Salt: 594ad47e-9c4a-4fc2-93d2-b132f9b15ec4 X-Archives-Hash: 2f2757787ecaccf6a8878d443c61213d On 2023-02-14, Rich Freeman wrote: > Where are you getting this from, the system log/journal? This doesn't > seem like a clean shutdown, so if it is a kernel PANIC I wouldn't > expect the most critical info to be in the log (since it will stop > syncing to protect the filesystem). The details you need probably > will be displayed on the console briefly. You can also enable a > network console, which will send the dmesg output continuously over > UDP to another device. This won't be interrupted by a PANIC unless > there is some issue with the hardware or networking stack. If you've got a serial port[1], you could also set up serial logging. Though using serial ports have become a bit of a lost art, the serial console code in the kernel is pretty carefully designed to be the last man standing when things start to die. It's possible (though I wouldn't say probable) that a serial console will be able to show you stuff closer to the event horizon than a network console can. Anyway, since still I'm in the serial port business (yes, there are still plenty of people using serial ports in industrial settings) I had to mention it... [1] For this purpose you want a plain old UART on the motherboard type seial port. You'd be surprised how many motherboards still have them. Even though they're never brought out to a DB9 connector on the back panel, there's often an 8-pin header on the edge of the board somewhere, so you'd need one of these: https://www.amazon.com/C2G-27550-Adapter-Bracket-Motherboards/dp/B0002J27R8/ -- Grant