#1107142 linux-image-6.12.27-amd64: mpt3sas LSI SAS2008 [1000:0072] probe failure - BAR 1 reservation error

Package:
src:linux
Source:
src:linux
Submitter:
goose
Date:
2025-07-02 19:13:01 UTC
Severity:
normal
Tags:
#1107142#5
Date:
2025-06-02 07:10:19 UTC
From:
To:
After upgrading from Debian Bookworm to Trixie, and subsequently to kernel linux-image-6.12.27-amd64 (version 6.12.27-1), my LSI SAS2008 HBA is no longer being initialized correctly, preventing access to the attached SAS drives. This appears to be a regression, as the LSI SAS2008 HBA and attached SAS drives work perfectly under kernel 6.1.0-37-amd64. The SAS drives connected to the LSI HBA are not detected by the system (do not appear in lsblk). The mpt3sas driver loads but fails to initialize the card. lspci -nnk for device 04:00.0 shows Kernel modules: mpt3sas but does not show a "Kernel driver in use" line when the failure occurs.

What I believe are the key error messages in dmesg are:

mpt3sas version 48.100.00.00 loaded
mpt3sas 0000:04:00.0: can't disable ASPM; OS doesn't have ASPM control
mpt3sas 0000:04:00.0: BAR 1: can't reserve [mem 0xWWWWWWWW-0xYYYYYYYY 64bit]  <-- Please replace with the exact memory addresses from your latest dmesg on 6.12.27
mpt2sas_cm0: pci_request_selected_regions: failed
mpt2sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:12319/_scsih_probe()!

Adding the kernel boot parameter pci=nocrs did not resolve the BAR 1 reservation error or the probe failure for mpt3sas on kernel 6.12.27-amd64. I am currently booting in to kernel 6.1.0-37-amd64 as a workaround.

Hardware Details:
SAS HBA: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)
    PCI ID: [1000:0072]
    Subsystem: Broadcom / LSI 9211-8i [1000:3020]
    PCI Address: 04:00.0
Motherboard: Supermicro X9DRi-LN4+
#1107142#10
Date:
2025-06-04 14:01:35 UTC
From:
To:
Hello,

It's hard to spot the problem in the massive changes between 6.1 and
6.12. Can you please try with intermediate kernel packages from
snapshot.debian.org, ideally identifying the oldest kernel that breaks
your system?

Best regards
Uwe
#1107142#17
Date:
2025-06-04 15:06:05 UTC
From:
To:
Hello,

Can you try booting 6.12.27-amd64 passing the kernel boot option pci=realloc=off?

Hope this helps.

Best,
A.
#1107142#22
Date:
2025-06-21 17:13:48 UTC
From:
To:
Sorry for the late reply, I've been out of the country and just returned home.

Upon returning home, I found a newer kernel available, 6.12.32-amd64. I installed that and rebooted with kernel boot options:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

The bug was still present on kernel 6.12.32-amd64, none of my SAS drives attached via my LSI card were coming up. I edited the boot options to:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=realloc=off"

And that appears to have fixed it. My SAS drives are now showing up and I can interact with them as normal.

Thanks for the tip, lord2y!
#1107142#29
Date:
2025-06-27 10:29:53 UTC
From:
To:
Hello,

[expanding the audience to include upstream and mark the bug as
forwarded accordingly]

Can you please additionally add

	dyndbg="file drivers/pci/* +p"

to the cmdline and provide the complete output of `dmesg` with and
without passing pci=realloc=off?

Thanks
Uwe
#1107142#38
Date:
2025-07-02 07:58:38 UTC
From:
To:
Certainly. Here is dmesg output without 'pci=realloc=off':

As expected, my SAS drives did not appear.

And here it is with 'pci=realloc=off':

In which my SAS drives do show up.

Please let me know if I can provide any further useful information.
#1107142#43
Date:
2025-07-02 08:03:09 UTC
From:
To:
Apologies for anyone getting this as a duplicate, apparently I formatted my previous email with HTML, which the mailing list servers do not like. Please forgive my inexperience.

Instead of a giant text dump, here is the attached 'dmesg' outputs as requested. Please let me know if I can provide any further information.