IronPort-SDR: w/l2LBCJKZg+TSD2apsIaIDxpYmNziuTVxCtO1b+i1jRiRgSiDXMW4eMP62XOpAWMFPk/6/tEx
 npflyWSHnRBhftHjq5G6MlLdHfrNEFEuT7Cs6lJyB4bzTfOWdL6BRw116Z84euTpskV3aH3n/W
 UHNr9DvfEJOilJx/YxX5zA7o4tyqwRSkLJa4puNiTcWOT5A2XNu4ZVsQOilfdmd5hnqwPJapvo
 RmP+SRoz7/N5Kb1py3KMQW3n84xZAd8hSAX4/QQrh8QU8dzswKTwcWQVtPHRkuhlEJNZFXV+zW
 jW6fhsp45Q/cb0WGVhZ2enbT
IronPort-SDR: Dx0Akj4zyzOkHsDpEy8BYt1htgbb6Vpp/PXBa71V4ADStr68+5WrgVOzve6YC/hmyTPrpA9i5o
 JQMzQDVnFrI46eWOvTHeo3ZDEsa5cFSUEGvMVVeodVZVicocFwH1jU4zMREXFqPqJ2ySjASaEN
 r7mv1bUUXLXh1IBJX7iNapX/1Pos60OAEl+Q1V4SBha7P6L49zE6Qj9bkxMp6u9U55Ui7s4pq8
 s0dFWuTNM9IJ42bldfzBY8vwUGXmp8Ajp/iMWztPP0yL2LtuwCo3CROK3pOEJo+0STnb33BAWA
 Xuo=
WDCIronportException: Internal
Message-ID: <26826c5d-2fa6-9719-be2a-5a22d1e9abc0@opensource.wdc.com>
Date:   Wed, 17 Nov 2021 08:40:58 +0900
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0)
 Gecko/20100101 Thunderbird/91.3.1
Subject: Re: Kernel 5.15 doesn't detect SATA drive on boot
Content-Language: en-US
To:     =?UTF-8?Q?Krzysztof_Wilczy=c5=84ski?= <kw@linux.com>
Cc:     Yuji Nakao <contact@yujinakao.com>, linux-kernel@vger.kernel.org,
        "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
        ". Bjorn Helgaas" <bhelgaas@google.com>,
        Marc Zyngier <maz@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
        Sasha Levin <sashal@kernel.org>
References: <87h7ccw9qc.fsf@yujinakao.com>
 <8951152e-12d7-0ebe-6f61-7d3de7ef28cb@opensource.wdc.com>
 <YZQ+GhRR+CPbQ5dX@rocinante>
From:   Damien Le Moal <damien.lemoal@opensource.wdc.com>
Organization: Western Digital
In-Reply-To: <YZQ+GhRR+CPbQ5dX@rocinante>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On 2021/11/17 8:26, Krzysztof Wilczy=C5=84ski wrote:
> [+CC Arnd, Bjorn, Marc and Sasha for visibility]
>=20
> Hello Damien and Yuji,
>=20
> [...]
>>> I'm using Arch Linux on MacBook Air 2010. I updated `linux` package[1=
]
>>> from v5.14.16 to v5.15.2 the other day, and the boot process stalled
>>> with the following message.
>>>
>>> ```shell
>>> :: running early hook [udev]
>>> Starting version 249.6-3-arch
>>> :: running hook [udev]
>>> :: Triggering uevents...
>>> Waiting 10 seconds for device /dev/sda3 ...
>>> ERROR: device '/dev/sda3' not found. Skipping fsck.
>>> :: mounting '/dev/sda' on real root
>>> mount: /new_root: no filesystem type specified.
>>> You are now being dropped into an emergency shell.
>>> sh: can't access tty; job control turned off
>>> [rootfs ]#
>>> ```
>>>
>>> In the emergency shell there's no `sda` devices when I type `$ ls
>>> /dev/`. By downgrading the kernel, boot process works properly.
>>>
>>> See also Arch Linux bug tracker[2]. There are similar reports on
>>> Apple devices.
>>>
>>> `dmesg` output in the emergency shell is attached. I guess this issue=
 is
>>> related to libata, so CCed to Damien Le Moal.
>>
>> I think that this problem is due to recent PCI subsystem changes which=
 broke Mac
>> support. The problem show up as the interrupts not being delivered, wh=
ich in
>> turn result in the kernel assuming that the drive is not working (see =
the
>> timeout error messages in your dmesg output). Hence your boot drive de=
tection
>> fails and no rootfs to mount.
>>
>> Adding linux-pci list.
>>
>>
>>
>>>
>>> Regards.
>>>
>>> [1] https://archlinux.org/packages/core/x86_64/linux/
>>> [2] https://bugs.archlinux.org/task/72734
>=20

Krzysztof,

> The error in the dmesg output (see [2] where the log file is attached)
> looks similar to the problem reported a week or so ago, as per:
>=20
>   https://lore.kernel.org/linux-pci/ee3884db-da17-39e3-4010-bcc8f878e2f=
6@xenosoft.de/

Thanks. I searched this thread but could not find it in the archive.
Early morning, need more coffee :)

>=20
> The problematic commits where reverted by Bjorn and the Pull Request th=
at
> did it was accepted, as per:
>=20
>   https://lore.kernel.org/linux-pci/20211111195040.GA1345641@bhelgaas/
>=20
> Thus, this would made its way into 5.16-rc1, I suppose.  We might have =
to
> back-port this to the stable and long-term kernels.

Yes, I think the fix needs to go in 5.15, which is latest stable and LTS.

>=20
> Yuji, could you, if you have some time to spare, try the 5.16-rc1 to se=
e if
> this have gotten better on your system?
>=20
> 	Krzysztof
>=20


--=20
Damien Le Moal
Western Digital Research