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 838CDC25B08 for ; Thu, 18 Aug 2022 01:08:36 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242490AbiHRBIe (ORCPT ); Wed, 17 Aug 2022 21:08:34 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45180 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239618AbiHRBIa (ORCPT ); Wed, 17 Aug 2022 21:08:30 -0400 Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 653422D1DE for ; Wed, 17 Aug 2022 18:08:26 -0700 (PDT) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id C44C55C01C1; Wed, 17 Aug 2022 21:08:23 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Wed, 17 Aug 2022 21:08:23 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= cc:cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm1; t=1660784903; x=1660871303; bh=WmFWT9Wj5/ JuOHgFegqTlFpnEJ5IUU83+EJpdPWqW/w=; b=quI3kB4wEkefeGCSr3rxiFLRSc 7d9OZXkTpm76sK12vCLfvYrs5TPmdrk7irIsiWwo4FaG792oOVk84uuq6t0kwuSQ 31yEgjmFmyTtQALQIrTi1b3BuuAjXtsPaHMYTpYJ/h/yKeafoS0m1tBh4GBJdVbS uT60bxT4Qyrc1bFWf88XUqQMMso+j2WvuwWbwgvHNp6uXtZQLta/SW3wE4x5dywO 2cJWJzBL5dnQrlWjwtbkjb2ai/MGtNBLvCOgsh4hzVvjRNZacch/6FLDQV/lYr3V WB6AinZH/IWybX8jCUGPA8QaSSljlr4V+Gy5P5Lq6ic55s57QqVH5pYn0wqQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1660784903; x=1660871303; bh=WmFWT9Wj5/JuOHgFegqTlFpnEJ5I UU83+EJpdPWqW/w=; b=M1lPXFJWvPbDg+qY1TznBhN9xRwXMPZK81r/mGUqeQ6M f/B4rJjYEs+Ie7hJZpVuXiV2WjeZUbTQDcfSp4L2CzkqZSlAPbpH+87cbUlJIS5q 58HzD5uVE/DDqUEV3tc21K9F9M2GYbSR0YVxEMPIbsmBsR8YArWJzL+PuRtn1eT6 QGBAX0w1JDyz7XNSxuy4qP5VESlNy8bnKPS1+3OwwU9+Z4OHrcKshG5YeCT4FNgw pPfrTcjn8Kh6WyZ43zETqmfM4qbEy48hxbLM58q4kKjVd8WK8Ed4QwHeuxEjvsq4 F7QuJ0xeGqJGcsVXeNDCULRPmiuBxt32PHu5m3z/nQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrvdehjedggeefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvfevuffkfhggtggujgesthdtredttddtvdenucfhrhhomheptehnughr vghsucfhrhgvuhhnugcuoegrnhgurhgvshesrghnrghrrgiivghlrdguvgeqnecuggftrf grthhtvghrnhephfegjedtudegveffteefjeeljedvgeetueelffdtffejgeffgeeggeff teegheeunecuffhomhgrihhnpegtihhrrhhushdqtghirdgtohhmnecuvehluhhsthgvrh fuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprghnughrvghssegrnhgrrhgr iigvlhdruggv X-ME-Proxy: Feedback-ID: id4a34324:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 17 Aug 2022 21:08:23 -0400 (EDT) Date: Wed, 17 Aug 2022 18:08:22 -0700 From: Andres Freund To: Linus Torvalds Cc: Guenter Roeck , linux-kernel@vger.kernel.org, Greg KH Subject: Re: upstream kernel crashes Message-ID: <20220818010822.hhqn353ddn3n2de6@awork3.anarazel.de> References: <20220814212610.GA3690074@roeck-us.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On 2022-08-17 10:12:18 -0700, Linus Torvalds wrote: > On Sun, Aug 14, 2022 at 2:26 PM Guenter Roeck wrote: > > > > syscaller reports lots of crashes with the mainline kernel. The latest > > I have seen, based on the current ToT, is attached. Backtraces are not > > always the same, but this one is typical. > > Ok, I just pushed out the pull of the virtio fixes, so hopefully this > is all behind us. FWIW, my much smaller automation turned green, building 274a2eebf80c https://cirrus-ci.com/task/6357530606567424?logs=build_image#L3814 previously it failed to come back up after a reboot at that point. And the first run of postgres' tests using that newly built image also passed, so I'm reasonably confident that the issue is fixed, rather than made less common. Not that that is as likely to find problems as syscaller. Greetings, Andres Freund