From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id E5387C433EF for ; Wed, 9 Feb 2022 01:30:59 +0000 (UTC) Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.94.2) (envelope-from ) id 1nHboW-0001YY-Bj; Tue, 08 Feb 2022 20:30:32 -0500 Received: from mail-qt1-x834.google.com ([2607:f8b0:4864:20::834]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1nHboS-0001XP-PQ for kernelnewbies@kernelnewbies.org; Tue, 08 Feb 2022 20:30:28 -0500 Received: by mail-qt1-x834.google.com with SMTP id l14so656204qtp.7 for ; Tue, 08 Feb 2022 17:30:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vt-edu.20210112.gappssmtp.com; s=20210112; h=sender:from:to:cc:subject:in-reply-to:references:mime-version :content-transfer-encoding:date:message-id; bh=9Aj5ncwPXYclTFtIPgPEQY27jX/GfVqUaTJ6Iic04xI=; b=wtz4g6fd4DkXR+pjfTWFl04VLs7b0pKM0EOoxV0wTk3LQ/eDLKeqF+7aIHZ6z/pdei 5bHOYBNX6HriORIp9uFHivQh7UyzbtyBssL/4sU0MBa/bRAobqV2yyMNB2rVRv2PPd6s IFa2Obd3L7yG1vx0X0UWOFqwMmYn/YDabxVJ5217RbXjqMUGmxKWmuUr1ws9zZC2NBxd OS0NqKllCakip6tvrElwxp8PQghxT7tz2m2iLIERJyzA8/T/jnDnyWGXRVMhsPKmLR/M 12/YTp8EKTbtQZbdgr3zCBmwq7FVY1+wjjAmbctdkzcmAgZ32xPn2ebsO3lY9F75IqF5 7BiQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:sender:from:to:cc:subject:in-reply-to:references :mime-version:content-transfer-encoding:date:message-id; bh=9Aj5ncwPXYclTFtIPgPEQY27jX/GfVqUaTJ6Iic04xI=; b=0N+Oyx0E8exTWpxHkC8eacGszXlSY0oEa5kqmfSJ7N8s+jHSAO3NfjdUoi5R/decX9 5rLzF7muyvs2QxM75oxPkKXPF9iJp7rur/crinWkp6X00xQKccfM6Ax4rcRKyg01i9IN dxkVZoxISrRJdBKnNOZpZEiE2xCDFUPQ9CNjdyFT9EdfqYmEDU12NscTOUS0/ajuZRke 8DJgvrUewdgbkM9DORp5KAnQfZnE4Wd+gtApb3hhUMZxPgnN0m8C5YJEqcKZ+yT1EkWX rbJSVhLewrEA/eTlGKzo/uEEf6peAMX3H1NYgnUXtBdqreWO1pZVVzxh0kH7wQrYN5BE 4V5w== X-Gm-Message-State: AOAM533rTsu8xN7Zt7BYWUgiTM15taAxNjiKzY61XZReDgBWgBZG63LR 9zXetIS8UXxIQvyUUVCBsjclqg== X-Google-Smtp-Source: ABdhPJzHXNjhvsp8eKm4uikk7ztxVl5RD6pGymrsBdjZ9ipJi7MM3SKciBG3tqrJPapzW8WS/QRBxw== X-Received: by 2002:ac8:7f48:: with SMTP id g8mr4970217qtk.622.1644370225971; Tue, 08 Feb 2022 17:30:25 -0800 (PST) Received: from turing-police ([2601:5c0:c380:d61::359]) by smtp.gmail.com with ESMTPSA id w3sm8571962qta.13.2022.02.08.17.30.24 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 08 Feb 2022 17:30:25 -0800 (PST) From: "Valdis Kl=?utf-8?Q?=c4=93?=tnieks" X-Google-Original-From: "Valdis Kl=?utf-8?Q?=c4=93?=tnieks" X-Mailer: exmh version 2.10.0-pre 07/05/2021 with nmh-1.7+dev To: David Kahurani Subject: Re: Kernel freezes instead of panicking In-reply-to: References: Mime-Version: 1.0 Date: Tue, 08 Feb 2022 20:30:24 -0500 Message-ID: <26925.1644370224@turing-police> Cc: kernelnewbies , Wonhyuk Yang X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kernelnewbies-bounces@kernelnewbies.org On Tue, 08 Feb 2022 08:03:56 +0300, David Kahurani said: > I figured I could use kdump to save the dmesg logs but it doesn't seem to > work with later kernels. kdump is probably overkill for just saving dmesg. If you're booting x86_64 in UEFI mode, using pstore to save the dmesg is probably a lot easier. What I have in .config: [~] zgrep -i pstore /proc/config.gz | grep ^C CONFIG_EFI_VARS_PSTORE=y CONFIG_PSTORE=y CONFIG_PSTORE_DEFAULT_KMSG_BYTES=65536 CONFIG_PSTORE_DEFLATE_COMPRESS=y CONFIG_PSTORE_COMPRESS=y CONFIG_PSTORE_DEFLATE_COMPRESS_DEFAULT=y CONFIG_PSTORE_COMPRESS_DEFAULT="deflate" CONFIG_PSTORE_CONSOLE=y CONFIG_PSTORE_PMSG=y CONFIG_PSTORE_RAM=y On most crashes and hangs, after reboot you'll find the dmesg logs in /sys/fs/pstore Note that you'll probably want to set up something that auto-recovers the data during reboot, as there's only a limited amount of UEFI storage available, so you can end up not getting messages if the space fills up. (The alignment varies because of loglevel info, you might want something like: cut -f2- -d'[' /sys/fs/pstore/* | sort -n | sed -e 's/^/[/' > pstore.`date +%m%d%y-%H%M` rm /sys/fs/pstore/* (You need the rm because if you don't, the next time you'll get 2 interleaved dmesgs from different boots and nothing will make sense :) Alternatively, use the timestamps in the filenames to disambiguate the various crashes.... _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies