mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Yuji Nakao <contact@yujinakao.com>,
	linux-kernel@vger.kernel.org,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: Kernel 5.15 doesn't detect SATA drive on boot
Date: Wed, 17 Nov 2021 08:05:21 +0900	[thread overview]
Message-ID: <8951152e-12d7-0ebe-6f61-7d3de7ef28cb@opensource.wdc.com> (raw)
In-Reply-To: <87h7ccw9qc.fsf@yujinakao.com>

On 2021/11/16 21:44, Yuji Nakao wrote:
> Hello,
> 
> 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, which 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 detection
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
> 
> 


-- 
Damien Le Moal
Western Digital Research

  reply	other threads:[~2021-11-16 23:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-16 12:44 Yuji Nakao
2021-11-16 23:05 ` Damien Le Moal [this message]
2021-11-16 23:26   ` Krzysztof Wilczyński
2021-11-16 23:40     ` Damien Le Moal
2021-11-16 23:54       ` Krzysztof Wilczyński
2021-11-17 16:24         ` Jeremy Soller
2021-11-17  9:07     ` Marc Zyngier
2021-11-17  9:36       ` Krzysztof Wilczyński
2021-11-21 15:41         ` Maxym Synytsky
2021-11-21 19:58           ` Marc Zyngier
2021-11-21 20:48             ` Maxym Synytsky
2021-11-21 21:09               ` Marc Zyngier
2021-11-17 13:52       ` Yuji Nakao
2021-11-17 14:20         ` Marc Zyngier

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=8951152e-12d7-0ebe-6f61-7d3de7ef28cb@opensource.wdc.com \
    --to=damien.lemoal@opensource.wdc.com \
    --cc=contact@yujinakao.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    /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®