@Koba, As just reported on kernel-t...@lists.ubuntu.com, the "for waiting the udev"[sic!] matter was completely unrelated.
With the patch set, the UBSAN messages are completely gone, and with the workaround reported to the list, the system boots normally. Having learned a bit more about UBSAN, it would seem that the system would still have booted despite the messages, so I shall try to see if I can alter the heading of this report. ** Summary changed: - [mpt3sas, UBSAN] ]linux 6.5-rc won't boot + [mpt3sas, UBSAN] ]linux 6.5-rc give error messages at boot ** Description changed: Ubuntu release: sune@jekaterina:~/src/deb$ lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 - sune@jekaterina:~/src/deb$ + sune@jekaterina:~/src/deb$ Package: linux-image- unsigned-6.5.0-060500rc1-generic_6.5.0-060500rc1.202307232333_amd64.deb from https://kernel.ubuntu.com/~kernel-ppa/mainline (rc2 and rc3 also affected) Expectation: System boots normally Actual results: See below On the request of Koba Ko on the kernel-t...@lists.ubuntu.com mailing list, I hereby submit the following: Do note that two "types" are mentioned, and that I am willing the assist in testing, as, obviously, I have a system with a controller covered by the mpt3sas driver. This is output from attempted boot of 6.5-rc3 from kernel-ppa, but it is similar to rcs 1 and 2: UBSAN: array-index-out-of-bounds in /home/kerne1/COD/linux/drivers/scsi/npt3sas/mpt3sas_scsih.c:4667:12 index 1 is out of range for type ’MPI12_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index—out-of-bounds in /home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih-c:4023:12 index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index—out-of-bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6810:36 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of-bounds in /home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6598:38 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of-bounds in /home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6602:36 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of—bounds in /home/kernel/COD/linux-drivers/scsi/mpt3sas/mpt3sas_scsih.c:6619:7 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of—bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:6666:21 index 1 is out of range for type ’MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of—bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7649:32 index 1 is out of range for type ’MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index-out-of—bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7651:23 index 1 is out of range for type ’MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7655:12 index 1 is out of range for type ’MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' - Timed out for waiting the udey queue being empty. + [EDIT] the next error, repeating for ~1½ hours before finishing boot, + was unrelated to mpt2sas and UBSAN. + + That error was "Timed out for waiting the udey queue being empty." + + Bug subject altered to reflect this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2028830 Title: [mpt3sas, UBSAN] ]linux 6.5-rc give error messages at boot Status in linux package in Ubuntu: In Progress Bug description: Ubuntu release: sune@jekaterina:~/src/deb$ lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 sune@jekaterina:~/src/deb$ Package: linux-image- unsigned-6.5.0-060500rc1-generic_6.5.0-060500rc1.202307232333_amd64.deb from https://kernel.ubuntu.com/~kernel-ppa/mainline (rc2 and rc3 also affected) Expectation: System boots normally Actual results: See below On the request of Koba Ko on the kernel-t...@lists.ubuntu.com mailing list, I hereby submit the following: Do note that two "types" are mentioned, and that I am willing the assist in testing, as, obviously, I have a system with a controller covered by the mpt3sas driver. This is output from attempted boot of 6.5-rc3 from kernel-ppa, but it is similar to rcs 1 and 2: UBSAN: array-index-out-of-bounds in /home/kerne1/COD/linux/drivers/scsi/npt3sas/mpt3sas_scsih.c:4667:12 index 1 is out of range for type ’MPI12_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index—out-of-bounds in /home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih-c:4023:12 index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index—out-of-bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6810:36 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of-bounds in /home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6598:38 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of-bounds in /home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6602:36 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of—bounds in /home/kernel/COD/linux-drivers/scsi/mpt3sas/mpt3sas_scsih.c:6619:7 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of—bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:6666:21 index 1 is out of range for type ’MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of—bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7649:32 index 1 is out of range for type ’MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index-out-of—bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7651:23 index 1 is out of range for type ’MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7655:12 index 1 is out of range for type ’MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [EDIT] the next error, repeating for ~1½ hours before finishing boot, was unrelated to mpt2sas and UBSAN. That error was "Timed out for waiting the udey queue being empty." Bug subject altered to reflect this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028830/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
