Re: problem booting 5.10

From: Linus Torvalds <torvalds@linux-foundation.org>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Julia Lawall <julia.lawall@inria.fr>,
	"James E.J. Bottomley" <jejb@linux.ibm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	nicolas.palix@univ-grenoble-alpes.fr,
	linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: problem booting 5.10
Date: Tue, 8 Dec 2020 11:19:22 -0800	[thread overview]
Message-ID: <CAHk-=whThuW=OckyeH0rkJ5vbbbpJzMdt3YiMEE7Y5JuU1EkUQ@mail.gmail.com> (raw)
In-Reply-To: <yq1sg8gunxy.fsf@ca-mkp.ca.oracle.com>

On Tue, Dec 8, 2020 at 10:59 AM Martin K. Petersen
<martin.petersen@oracle.com> wrote:
>
> > So I'm adding SCSI people to the cc, just in case they go "Hmm..".
>
> Only change in this department was:
>
> 831e3405c2a3 scsi: core: Don't start concurrent async scan on same host

Yeah, I found that one too, and dismissed it for the same reason you
did - it wasn't in rc1. Plus it looked very simple.

That said, maybe Julia might have misspoken, and rc1 was ok, so I
guess it's possible. The scan_mutex does show up in that "locks held"
list, although I can't see why it would matter. But it does
potentially change timing (so it could expose some existing race), if
nothing else.

But let's make sure Jens is aware of this too, in case it's some ATA
issue. Not that any of those handful of 5.10 changes look remotely
likely _either_.

Jens, see

   https://lore.kernel.org/lkml/alpine.DEB.2.22.394.2012081813310.2680@hadrien/

if you don't already have the lkml thread locally.. There's not enough
of the dmesg to even really guess what Julia's actual hardware is,
apart from it being a Seagate SATA disk. Julia? What controllers and
disks do you have show up when things work?

             Linus