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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 20076C19F2D for ; Tue, 9 Aug 2022 13:40:40 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243862AbiHINkj (ORCPT ); Tue, 9 Aug 2022 09:40:39 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50342 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S243891AbiHINki (ORCPT ); Tue, 9 Aug 2022 09:40:38 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8902415FE6 for ; Tue, 9 Aug 2022 06:40:37 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 1266B6114D for ; Tue, 9 Aug 2022 13:40:37 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPS id 71AAEC433C1 for ; Tue, 9 Aug 2022 13:40:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1660052436; bh=GsqDUB7pAYPJRokt0b8zNi6tKQREim5dtEzDGelKZi0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=TrTxU/PYNKJxLIH6WMvRHd2Ahdfs++m5tfJfg++CPoyzN5mrMPKxnprXTnciy210v bMjJQzwNYp/cEEGBu99odXzTfSCoOAZPjoAWaQYH2pR0hxNlpc0kPRTkYF+XGJZKtk pylTkhv4c2O5esaiNVkPyE2GrgJCp43ja4hOeYHRM0UPx6pVfI+Oqty9zK54nzuwqt T7tkij2Rnx4Nk5xuRA+Ot2t1PlANqdzLV7pjhQYGaTvh/U2aau9XVTQY2MHmFEiKTZ RV7m6wD579z7oaJCCsrlMIqCvAOFMI7BEPmDEvQd27EyQDMJnZT6HPazDklwYsIh/z LzPRRshWDNztw== Received: by aws-us-west-2-korg-bugzilla-1.web.codeaurora.org (Postfix, from userid 48) id 5EF75C433E9; Tue, 9 Aug 2022 13:40:36 +0000 (UTC) From: bugzilla-daemon@kernel.org To: linux-ext4@vger.kernel.org Subject: [Bug 216322] Freezing of tasks failed after 60.004 seconds (1 tasks refusing to freeze... task:fstrim ext4_trim_fs - Dell XPS 13 9310 Date: Tue, 09 Aug 2022 13:40:36 +0000 X-Bugzilla-Reason: None X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: AssignedTo fs_ext4@kernel-bugs.osdl.org X-Bugzilla-Product: File System X-Bugzilla-Component: ext4 X-Bugzilla-Version: 2.5 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: lenb@kernel.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: fs_ext4@kernel-bugs.osdl.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugzilla.kernel.org/ Auto-Submitted: auto-generated MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org https://bugzilla.kernel.org/show_bug.cgi?id=3D216322 --- Comment #6 from Len Brown (lenb@kernel.org) --- Is there an simple recipe to reproduce this failure? Note that upon this 60-second timeout, the kernel aborts the suspend and un-freezes user-space. Well, what is running in user space is the sleepgraph program with --multi, which saves the record of the failure and immediately provokes the next suspend -- which works. Did the act of unfreezing user-space result in progress, or were we just lucky that the operation completed before the subsequent suspend request? Note that Rafael thought that the kernel timeout was 20 seconds, not 60 seconds, and he's inclined to make it shorter, not longer. (are we sure that this process is actually making progress, and not in some kind of deadlock that would persist no matter now long the timeout?) --=20 You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.=