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 kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4637CC61DA4 for ; Tue, 14 Feb 2023 06:49:44 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id AD0416B0073; Tue, 14 Feb 2023 01:49:43 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id A7FED280002; Tue, 14 Feb 2023 01:49:43 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 94757280001; Tue, 14 Feb 2023 01:49:43 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0017.hostedemail.com [216.40.44.17]) by kanga.kvack.org (Postfix) with ESMTP id 80BD66B0073 for ; Tue, 14 Feb 2023 01:49:43 -0500 (EST) Received: from smtpin03.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay03.hostedemail.com (Postfix) with ESMTP id 17935A0D1D for ; Tue, 14 Feb 2023 06:49:43 +0000 (UTC) X-FDA: 80464971846.03.430E566 Received: from mail-oa1-f51.google.com (mail-oa1-f51.google.com [209.85.160.51]) by imf09.hostedemail.com (Postfix) with ESMTP id 115CC140005 for ; Tue, 14 Feb 2023 06:49:40 +0000 (UTC) Authentication-Results: imf09.hostedemail.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=gNLByVF7; spf=pass (imf09.hostedemail.com: domain of groeck7@gmail.com designates 209.85.160.51 as permitted sender) smtp.mailfrom=groeck7@gmail.com; dmarc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1676357381; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=rijdzKSfbK5ozVCDgevjXVzr4zgQ6Ett6421gYQjBjU=; b=TlbWQ6gHjJBNYn+q/pPIH/kYNguwen5xT94sbMehSDBno6sScew+TOZZ+eZ2/xO6NcORCu TzM2xJpToRlXK4qN/kfjxzZH1czprjD+W4E0odkjEhlcrqN1Kb2msR0NugYMTMi2QCxyxg ZQ23ImceVCQEJxhDJyzSGS7m1luueV4= ARC-Authentication-Results: i=1; imf09.hostedemail.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=gNLByVF7; spf=pass (imf09.hostedemail.com: domain of groeck7@gmail.com designates 209.85.160.51 as permitted sender) smtp.mailfrom=groeck7@gmail.com; dmarc=none ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1676357381; a=rsa-sha256; cv=none; b=5hy87jWnm4K6kNEe2FNRVuZ6153G3AAfbKqeygK9CU63oeh3bFZeKJqwchiQUHblywwN6Y qsJatz00LnFNegyLbV3wUj/SNvU7Cz5AdgZQfUC5f6l9H9nlF6fzZ5vUk7RKEXTgedF82O HBZ/w3kaT9QG6WJdIKYSsh+t5drtLjc= Received: by mail-oa1-f51.google.com with SMTP id 586e51a60fabf-15ff0a1f735so17965717fac.5 for ; Mon, 13 Feb 2023 22:49:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:subject:from:references:cc:to :content-language:user-agent:mime-version:date:message-id:sender :from:to:cc:subject:date:message-id:reply-to; bh=rijdzKSfbK5ozVCDgevjXVzr4zgQ6Ett6421gYQjBjU=; b=gNLByVF7GA+0ujtTikXm5+Fcca8YkgCFBVUuv8X/YA7bpI1ZRU6IPPKtbZJlYRUWpw /MePF0CQTl8AnRVKMAdAAao6pyWwBtMNn1nwGCo4cxOf5cpfTZi46H59nzeSfT+WLW46 zqMic8R1xlGD6D2g80oUKonOHxY4i1asrnDtUFnWcqOZLou/bp5+/Gf3PDepKM8FEWen Ic5D/hkpZ4PmSBcu7zvV2riF5tEK1jtyx3z/USuHuM+TZsb1I9rOoq5iDAPOPaRTcqQX juqmd/Gx6Nc5i6Tsg1I/YdijZticj1qluGeu/XedoBajQVKGwYw4h6wOIXAQekqu2B3C H/iA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:subject:from:references:cc:to :content-language:user-agent:mime-version:date:message-id:sender :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=rijdzKSfbK5ozVCDgevjXVzr4zgQ6Ett6421gYQjBjU=; b=BJI9E/UXQkT9Tnmn/KmF2zPSK4xZb+qj/HvOfq30VrcDGRc5LP0fwLLG7aF+PDIzHZ ptYhSjzLPFqDRmIMWvFJBUlyTxMmmWfLzU3NzKOe7RZhvFDJWs1ZkrbOqKF/Z8ciNqCK sD9DIXxWCxvIZJw2hEFPh2EaTs8BBhoLOhC6QEEPy3JtVPkAxjhGub9b27R9O6G9l80z SHxdLaYOcP7fxUA70rl1b/p6vaZJqHiOl2v0pthupYi1Ro+Ywt32Blpp1+92iZixFant B60XPedTHA/nWZHj5jrwD0nXNZBV1iS9ch2xbbV3I/owvJtYfD3QVoEyxoEBU9ASy1Wo qLew== X-Gm-Message-State: AO0yUKUFCSrEpmzSZe/GVviE7XxCf5CloXQEOGOicrZZ/zEbsXO5FwOb nUwv+z9JwKZjn6a3Sguulak= X-Google-Smtp-Source: AK7set+D6se+3HXzrTkHjLfiAh+EJonOXL1A3hahbqcy+RaRH5Onp3cZWFOegYMqLSY70kp6fnxs3A== X-Received: by 2002:a05:6870:e750:b0:16e:9dd:f059 with SMTP id t16-20020a056870e75000b0016e09ddf059mr441585oak.14.1676357380183; Mon, 13 Feb 2023 22:49:40 -0800 (PST) Received: from ?IPV6:2600:1700:e321:62f0:329c:23ff:fee3:9d7c? ([2600:1700:e321:62f0:329c:23ff:fee3:9d7c]) by smtp.gmail.com with ESMTPSA id ds41-20020a0568705b2900b0016db8833b2dsm4153574oab.52.2023.02.13.22.49.38 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 13 Feb 2023 22:49:39 -0800 (PST) Message-ID: <07c870d3-5d98-ca51-5de8-034abc631673@roeck-us.net> Date: Mon, 13 Feb 2023 22:49:37 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Content-Language: en-US To: Stephen Rothwell Cc: Bagas Sanjaya , Andrew Morton , linux-kernel@vger.kernel.org, linux-next@vger.kernel.org, linux-mm@kvack.org References: <20230213094754.397f86af6b2dea4aafd92344@linux-foundation.org> <58fb32f8-ce1e-913b-3b85-c41b0630d4c6@roeck-us.net> <20230214172040.60657882@canb.auug.org.au> From: Guenter Roeck Subject: Re: nvme boot problems after merge of mm-stable tree into linux-next In-Reply-To: <20230214172040.60657882@canb.auug.org.au> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Stat-Signature: ay4j81ie7pr48uxgssechga1megck3c8 X-Rspam-User: X-Rspamd-Queue-Id: 115CC140005 X-Rspamd-Server: rspam06 X-HE-Tag: 1676357380-346024 X-HE-Meta: U2FsdGVkX1/YwCBgbYdMWe8BhtE+a8E9OiQR6jayzidbkXYq4Xq+5j73cjkM19ZQN7ThseLvKAHeXT7EhkfQ1STilBTy9HLyWisLojjsQ2O9P35jMcnjSbTpQycn1+z7PLfbH7+F2wpwz7QUPmHhPK8w3AYx1Mq7cxMegOXdyg76qMkH0EisBMWmJ0g7TR9rch2mgOOaxps2Nqdg931X7mw6IAy4T1jxqzUciVqXCqOP8yOtJwzG6FSjvuSDSFjojMpLZ5IIeMCKLfFgh60XHHeWzAR7c/z/VtyzQLcYepbx2lbeF7L3tS+libqnGZUmM5yTs3q40sE0x5AY88/zDwbUwW21fUmPIY5Ln3jB5FjOASpgvIROCtlcJJiAIyg8pESkE67DeDYRkbnNHcnxtNctaG+XUk+hHEOSr/nRiMfpeftAXO6Rm62QLwQwoHtfoxX0N6jvJbZgsiFn06dbXZzK7cCyrukjTpnqoE7XK35x8oi1Ck152Q3oDC7bQp4tNMnS4prSn6cpLr55xLCgz1e7IWwKyJJEzOJAqaRK75gXodyZj7yKyL13TTGgY5u6fwHLCMl4RuzJwpE4OKr8pgbTajK1yFIkCzZYV5F1sA9X8VAF+Qb39YNMXU+OkXY/UCfVLIro/9bEMJGdEfgoAjoeVUBJkp2ukrmFQl+FluPkdnflAKexr67PBpAz0WFm6fVtvijmNJZQFVlJLlmhIhevrgpZwQq4I5teSrKQSle7D0UpmIWqnvjcoHN9GZRfGVUNLuBgp11S3/soHNGpyblb8wh6IWkJCMK89xmFqDP5uIDsbpxBdBDV++vd0T1wMqkw5b+2omFE++0VAFT8DOJhh4+eE1keUcM7IjMQ4tBPvRlJyjpAtyOZkHTlgledrNXpPH5LJWKSG+y5+mn0hrs2BLJL6GoFOcPjctGL3Zrsm9i8xqPpWufibrjETm8Jwq9OalkYn6iNoIgQhoj mwyD7MNe D1K4tMSuWsSovfW17dENEiIRJvUdjdDiU+jTDdx77JVDWFsf0QcBHVXpgamU76uo0ZgYpho+/12FNonosewhLxeXGU7fYw34oX8kPBGkhuf1vN49EqvVY20vDY1/2AnBgvwsdEyxeVHVB4l4C1dpN9Owy2DGCG/c2/hZa7mwTxn4e3Bwf77ej8AUJbIw7HeI6OeZOPhoMswEdqCKx9LAGZbBHk5ztbp+kPVQ+Xqk1D367UXwurK+tEIxUH5FGow2JOKsgAUzZwZYxVkF+1yXMYJds/+QOxAeZLgWGG1ohbw05HqBM0Py9tMHbbmnYu5uOErlLa5wLMLxS4D8Yx0gEcgpB2qMKnsD2/rHKko35sje2I0wkH/EgrstYbkzP3FDozjrVnod44UTz0hzfr1WqWPNfdF5NYFdGmlSyyX3rr64Wo51ZIW+L8+nzdfWUFXRD/VycvSZ3QUJI7JSJJtB7C54NwFyzcaKR1V6g1HzfH+vUTWIuKtzzRyM8AuXc4015KlN9faDXTtjXUCM= X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On 2/13/23 22:20, Stephen Rothwell wrote: > Hi Guenter, > > On Mon, 13 Feb 2023 20:01:33 -0800 Guenter Roeck wrote: >> >> Overall, that suggests that there may have been a change somewhere >> else in the kernel which is incompatible with a change in one of >> the mm branches. It is interesting that the problem in next-20230210 >> was seen after the merge of mm-stable, and that it is now seen after >> the merge of mm-everything. > > That could be because I moved some merge resolution fix patches from > the merge of mm-everything to the merge of mm-stable (they were all for > conflicts involving commits that are now in mm-stable). So one of my > merge resolutions could be bad. Or there could be some interaction of > something in mm-everything (that is not in mm-stable or > mm-nonmm-stable) that is interacting with some other change in the rest > of -next. > In next-20230210, the crash happened after the merge of mm-stable. In next-20230213, the crash happens after the merge of mm-everything. That means both the merge of mm-stable and mm-nonmm-stable are now fine. So I would suspect that something in the merge of mm-everything interacts with the rest of -next. Guenter