Following the Bisecting a bug guide, i also report here a potential kernel bug: 218896 – SATA devices on Alder-Lake S not recognized since kernel 6.7 on bugzilla.kernel.org side
It follows my first post here related to my sata device not recognized since kernel 6.7
Iupdated my system with the last stable update without any issue, my kernel was still version 6.6.19. I rebooted and i was able to do whatever as usual.
Then, i installed kernel 6.7.7 with Manjaro tools, as i always do. Just after rebooting, i get the following message in a black screen right after grub menu :
ERROR: resume: hibernation device 'UUID=<uuid the swap file location> not found
mount: /new_root: can’t find UUID=<uuid of my root partition>
ERROR: Failed to mount ‘UUID=<uuid of my …
To sum up, since kernel 6.7, none of my SATA devices are recognized, it’s like they do not exist.
I strongly suspect an issue with Alder Lake S intel CPU, potentially with a combination of B660 chipset, which does not recognized any SATA devices. I have made some tests with 3 different devices, 2 SSD and 1 HDD.
There is a similar issue reported here, on Batocera :
opened 09:36PM - 10 Mar 24 UTC
requires upstream fix
### Batocera build version
39
### Your architecture
X86
### Your Graphic Pro… cessor Unit(s) (GPU)
Nvidia, does not matter
### Issue description
Today I attempted an Upgrade to check if the full broken status of DBus/Steam has been addressed (Spoiler: nope) and ended up with a broken system. After the Upgrade V38->V39 the system would not boot anymore stuck with a black screen.
### Detailed reproduction steps
I use an B660 mainboard together with an 12th gen CPU and a SATA SSD. Just upgrading to V39 was enough to have a lot of "fun" for the whole day.
### Details of any attempts to fix this yourself
My first assumption was that something in the upgrade processes went wrong, or it being some secure boot issue. Neither is true. After getting into the verbose boot start i got these lines repeating on the consoles
```
[timestamp] LABEL=BATOCERA: Can't lookup bootdev
[timestamp] LABEL=BATOCERA: Can't lookup bootdev
[timestamp] LABEL=BATOCERA: Can't lookup bootdev
[timestamp] LABEL=BATOCERA: Can't lookup bootdev
[timestamp] LABEL=BATOCERA: Can't lookup bootdev
[timestamp] LABEL=BATOCERA: Can't lookup bootdev
[timestamp] LABEL=BATOCERA: Can't lookup bootdev
mount: mounting LABEL=BATOCERA on /boot_root failed: No such file or directory
Waiting for the root device
```
Therefore early boot was working but after that the device went missing. I attempted a reinstallation from a stick but oddly the SSD would not show up. Clearing it was of no use. Therefore I wrote the image file directly to the SSD by adapter. Then I got the exact same problem as above. More crosschecking revealed, the system no longer recognizes any internal SATA devices. (NVMe I have not checked). On V38 it works fine, V39 no longer. Booting V39 via USB works fine, but thats no solution.
I ended up downgrading to V38
### Details of any modifications you have made to Batocera.
N/A
### Logs and data
Oddly enough lspci and dmsg came up IDENTICAL on v38 and v39. However on V39 no internal SATA device appears in /dev or anywhere else.
```
00:17.0 SATA controller: Intel Corporation Alder Lake-S PCH SATA Controller [AHCI Mode] (rev 11) (prog-if 01 [AHCI 1.0])
DeviceName: Onboard - SATA
Subsystem: Biostar Microtech Int'l Corp Device 5225
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 123
Memory at 81200000 (32-bit, non-prefetchable) [size=8K]
Memory at 81203000 (32-bit, non-prefetchable) [size=256]
I/O ports at 5050 [size=8]
I/O ports at 5040 [size=4]
I/O ports at 5020 [size=32]
Memory at 81202000 (32-bit, non-prefetchable) [size=2K]
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [70] Power Management version 3
Capabilities: [a8] SATA HBA v1.0
Kernel driver in use: ahci
```
```
[ 0.357479] ahci 0000:00:17.0: version 3.0
[ 0.367794] ahci 0000:00:17.0: AHCI 0001.0301 32 slots 4 ports 6 Gbps 0xf0 impl SATA mode
[ 0.367804] ahci 0000:00:17.0: flags: 64bit ncq sntf led clo only pio slum part ems deso sadm sds
[ 0.401060] scsi host0: ahci
[ 0.401635] scsi host1: ahci
[ 0.402063] scsi host2: ahci
[ 0.402436] scsi host3: ahci
[ 0.402776] scsi host4: ahci
[ 0.403015] scsi host5: ahci
[ 0.403220] scsi host6: ahci
[ 0.403441] scsi host7: ahci
```
and also here, on Ubuntu :
Whereas here it’s not really clear on Ubuntu what kernel version is problematic on the first post, it’s clear that going back to 6.6 solve the issue.
Do you experience also this issue with SATA devices and the same CPU/Chipset ?
Upstream patch ata: ahci: Do not apply Intel PCS quirk on Intel Alder Lake - kernel/git/libata/linux.git - libata development tree solved this issue.
My SATA devices are now detected again, this is an issue with Alder Lake S (there is a mistake in upstream comment, this is not Alder Lake P) intel cpu.
This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.