Re: problem booting 5.10

[Julia Lawall <julia.lawall@inria.fr>]

[-- Attachment #1: Type: text/plain, Size: 1421 bytes --]



On Tue, 8 Dec 2020, Linus Torvalds wrote:

> 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,

rc1 was not ok.  I just started rebasing and the first step was not ok
either.

> 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?

A dmesg after successfully booting in 5.9 is attached.

julia

[-- Attachment #2: Type: application/gzip, Size: 31057 bytes --]