From: Guenter Roeck <linux@roeck-us.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: nvme boot problems after merge of mm-stable tree into linux-next
Date: Sun, 26 Feb 2023 14:53:29 -0800 [thread overview]
Message-ID: <d4260bee-2bec-40e4-b07f-3a9fa18c3d72@roeck-us.net> (raw)
In-Reply-To: <20230227091423.3797ba8e@canb.auug.org.au>
On 2/26/23 14:14, Stephen Rothwell wrote:
> Hi all,
>
> On Tue, 14 Feb 2023 14:29:29 +0700 Bagas Sanjaya <bagasdotme@gmail.com> wrote:
>>
>> On 2/14/23 13:49, Guenter Roeck wrote:
>>> 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.
>>>
>>
>> OK, thanks!
>
> Did this get resolved?
>
I think so. Either the offending patch was reverted, or it has been fixed.
I still see various boot problems in -next (and most of them are now
seen in mainline as well), but none of them are nvme related.
Guenter
next prev parent reply other threads:[~2023-02-26 22:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 16:27 Guenter Roeck
2023-02-13 17:47 ` Andrew Morton
2023-02-14 2:23 ` Bagas Sanjaya
2023-02-14 4:01 ` Guenter Roeck
2023-02-14 6:20 ` Stephen Rothwell
2023-02-14 6:49 ` Guenter Roeck
2023-02-14 7:29 ` Bagas Sanjaya
2023-02-26 22:14 ` Stephen Rothwell
2023-02-26 22:53 ` Guenter Roeck [this message]
2023-02-26 23:04 ` Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d4260bee-2bec-40e4-b07f-3a9fa18c3d72@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=bagasdotme@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®