[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <0a43155c-b56d-4f85-bb46-dce2a4e5af59@kernel.org>
Date: Tue, 10 Sep 2024 14:19:08 +0200
From: Jesper Dangaard Brouer <hawk@...nel.org>
To: Linus Torvalds <torvalds@...uxfoundation.org>,
LKML <linux-kernel@...r.kernel.org>
Cc: Netdev <netdev@...r.kernel.org>, Jens Axboe <axboe@...nel.dk>,
linux-ide@...r.kernel.org, dlemoal@...nel.org, cassel@...nel.org,
handan.babu@...cle.com, djwong@...nel.org,
Linux-XFS <linux-xfs@...r.kernel.org>, hdegoede@...hat.com,
"David S. Miller" <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>,
kernel-team <kernel-team@...udflare.com>
Subject: Regression v6.11 booting cannot mount harddisks (xfs)
Hi Linus,
My testlab kernel devel server isn't booting correctly on v6.11 branches
(e.g. net-next at 6.11.0-rc5)
I just confirmed this also happens on your tree tag: v6.11-rc7.
The symptom/issue is that harddisk dev names (e.g /dev/sda, /dev/sdb,
/dev/sdc) gets reordered. I switched /etc/fstab to use UUID's instead
(which boots on v6.10) but on 6.11 it still cannot mount harddisks and
doesn't fully boot.
E.g. errors:
systemd[1]: Expecting device
dev-disk-by\x2duuid-0c2b348d\x2de013\x2d482b\x2da91c\x2d029640ec427a.device
- /dev/disk/by-uuid/0c2b348d-e013-482b-a91c-029640ec42
7a...
[DEPEND] Dependency failed for var-lib.mount - /var/lib.
[...]
[ TIME ] Timed out waiting for device
dev-d…499e46-b40d-4067-afd4-5f6ad09fcff2.
[DEPEND] Dependency failed for boot.mount - /boot.
That corresponds to fstab's:
- UUID=8b499e46-b40d-4067-afd4-5f6ad09fcff2 /boot xfs defaults 0 0
- UUID=0c2b348d-e013-482b-a91c-029640ec427a /var/lib/ xfs defaults 0 0
It looks like disk controller initialization happens in *parallel* on
these newer kernels as dmesg shows init printk's overlapping:
[ 5.683393] scsi 5:0:0:0: Direct-Access ATA SAMSUNG
MZ7KM120 003Q PQ: 0 ANSI: 5
[ 5.683641] scsi 7:0:0:0: Direct-Access ATA SAMSUNG
MZ7KM120 003Q PQ: 0 ANSI: 5
[ 5.683797] scsi 8:0:0:0: Direct-Access ATA Samsung SSD
840 BB0Q PQ: 0 ANSI: 5
[...]
[ 7.057376] sd 5:0:0:0: [sda] 234441648 512-byte logical blocks:
(120 GB/112 GiB)
[ 7.062279] sd 7:0:0:0: [sdb] 234441648 512-byte logical blocks:
(120 GB/112 GiB)
[ 7.070628] sd 5:0:0:0: [sda] Write Protect is off
[ 7.070701] sd 8:0:0:0: [sdc] 488397168 512-byte logical blocks:
(250 GB/233 GiB)
Perhaps this could be a hint to what changed?
Any hints what commit I should try to test revert?
Or good starting point for bisecting?
--Jesper
Extra system info that might be relevant:
00:11.4 SATA controller: Intel Corporation C610/X99 series chipset sSATA
Controller [AHCI mode] (rev 05) (prog-if 01 [AHCI 1.0])
Kernel driver in use: ahci
00:1f.2 SATA controller: Intel Corporation C610/X99 series chipset
6-Port SATA Controller [AHCI mode] (rev 05) (prog-if 01 [AHCI 1.0])
Subsystem: Super Micro Computer Inc Device 0834
Kernel driver in use: ahci
$ lsb_release -a
LSB Version: :core-5.0-amd64:core-5.0-noarch
Distributor ID: Fedora
Description: Fedora release 40 (Forty)
Release: 40
Codename: Forty
Powered by blists - more mailing lists