linux-kernel - v5.4.289 failed to boot with error megasas_build_io_fusion 3219 sge

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <7dc143fa-4a48-440b-b624-ac57a361ac74@oracle.com>
Date: Wed, 29 Jan 2025 13:57:59 +0530
From: Harshvardhan Jha <harshvardhan.j.jha@...cle.com>
To: Konrad Wilk <konrad.wilk@...cle.com>,
        Boris Ostrovsky <boris.ostrovsky@...cle.com>,
        "jgross@...e.com" <jgross@...e.com>
Cc: "sstabellini@...nel.org" <sstabellini@...nel.org>,
        "xen-devel@...ts.xenproject.org" <xen-devel@...ts.xenproject.org>,
        "iommu@...ts.linux-foundation.org" <iommu@...ts.linux-foundation.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Harshit Mogalapalli <harshit.m.mogalapalli@...cle.com>
Subject: v5.4.289 failed to boot with error megasas_build_io_fusion 3219
 sge_count (-12) is out of range

Hello there,

The stable tag v5.4.289 seems to fail to boot with following trace:

[ OK ] Created slice system-serial\x2dgetty.slice. [ OK ] Listening on
udev Control Socket. [ OK ] Reached target Local Encrypted Volumes. [ OK
] Listening on /dev/initctl Compatibility Named Pipe. [ OK ] Listening
on Delayed Shutdown Socket. [ OK ] Created slice
system-selinux\x2dpol...grate\x2dlocal\x2dchanges.slice. [ OK ] Stopped
target Initrd File Systems. [ OK ] Listening on LVM2 metadata daemon
socket. Mounting Debug File System... [ OK ] Listening on networkd
rtnetlink socket. [ OK ] Listening on Device-mapper event daemon FIFOs.
Starting Monitoring of LVM2 mirrors... dmeventd or progress polling... [
OK ] Created slice User and Session Slice. Starting Read and set NIS
domainname from /etc/sysconfig/network... Starting Load legacy module
configuration... [ OK ] Set up automount Arbitrary Executab...ats File
System Automount Point. [ OK ] Created slice
system-rdma\x2dload\x2dmodules.slice. [ OK ] Started Forward Password
Requests to Wall Directory Watch. [ OK ] Reached target Paths. Starting
Remount Root and Kernel File Systems... [ OK ] Created slice
system-getty.slice. Starting Create list of required st... nodes for the
current kernel... Starting Set Up Additional Binary Formats... [ OK ]
Stopped target Initrd Root File System. [ OK ] Reached target Slices. [
OK ] Created slice system-systemd\x2dfsck.slice. [ OK ] Mounted POSIX
Message Queue File System. [ OK ] Mounted Debug File System. [ OK ]
Started Read and set NIS domainname from /etc/sysconfig/network.
Mounting Arbitrary Executable File Formats File System... [ OK ] Started
Journal Service. [ OK ] Started Create list of required sta...ce nodes
for the current kernel. Starting Create Static Device Nodes in /dev... [
OK ] Started LVM2 metadata daemon. [ OK ] Started Remount Root and
Kernel File Systems. Starting Load/Save Random Seed... Starting udev
Coldplug all Devices... Starting Flush Journal to Persistent Storage...
[FAILED] Failed to start Load Kernel Modules. See 'systemctl status
systemd-modules-load.service' for details. Starting Apply Kernel
Variables... [ OK ] Started Load/Save Random Seed. [ OK ] Mounted
Arbitrary Executable File Formats File System. [ OK ] Started Set Up
Additional Binary Formats. [ OK ] Started Create Static Device Nodes in
/dev. Starting udev Kernel Device Manager... [ OK ] Started Apply Kernel
Variables. [ OK ] Started Load legacy module configuration. [ OK ]
Started udev Coldplug all Devices. Starting udev Wait for Complete
Device Initialization... [ 24.427217] megaraid_sas 0000:65:00.0:
megasas_build_io_fusion 3273 sge_count (-12) is out of range. Range is:
0-256

[   24.427217] megaraid_sas 0000:65:00.0: megasas_build_io_fusion 3273
sge_count (-12) is out of range. Range is:  0-256 kept showing
infinitely. It kept popping until I reset the system.

Reverting the following patch seems to fix the issue:

commit 07c9cccc4c3fecba175a7e5aafba6370758f5ce2
Author: Juergen Gross <jgross@...e.com>
Date:   Fri Sep 13 12:05:02 2024 +0200

    xen/swiotlb: add alignment check for dma buffers

    [ Upstream commit 9f40ec84a7976d95c34e7cc070939deb103652b0 ]

    When checking a memory buffer to be consecutive in machine memory,
    the alignment needs to be checked, too. Failing to do so might result
    in DMA memory not being aligned according to its requested size,
    leading to error messages like:

      4xxx 0000:2b:00.0: enabling device (0140 -> 0142)
      4xxx 0000:2b:00.0: Ring address not aligned
      4xxx 0000:2b:00.0: Failed to initialise service qat_crypto
      4xxx 0000:2b:00.0: Resetting device qat_dev0
      4xxx: probe of 0000:2b:00.0 failed with error -14

    Fixes: 9435cce87950 ("xen/swiotlb: Add support for 64KB page
granularity")
    Signed-off-by: Juergen Gross <jgross@...e.com>
    Reviewed-by: Stefano Stabellini <sstabellini@...nel.org>
    Signed-off-by: Juergen Gross <jgross@...e.com>
    Signed-off-by: Sasha Levin <sashal@...nel.org>

I tried changing swiotlb grub command line arguments but that didn't
seem to help much unfortunately and the error was seen again.

Thanks & Regards,
Harshvardhan