** Changed in: linux (Ubuntu Noble)
Status: Won't Fix => In Progress
** Changed in: linux (Ubuntu Noble)
Assignee: Michael Reed (mreed8855) => Matthew Ruffell (mruffell)
** Tags added: sts
** Description changed:
+ BugLink: https://bugs.launchpad.net/bugs/2116103
+
[Impact]
- With the current driver mpi3mr v8.9.1.0.51, the logs are flooded with error
message “mpi3mr_devinfochg_evt_bh :Device info change: handle(0x0001):
persist_id(0x1)”. The above patch adds a check to block driver messages
flooding the OS logs.
+
+ The current mpi3mr driver floods the kernel logs, spamming with entries
+ mentioning each and every device state change.
+
+ [Wed Oct 15 09:35:05 2025] mpi3mr0: Device Info Changed: dev=0x0001 Form=0x2
+ [Wed Oct 15 09:35:05 2025] mpi3mr0: mpi3mr_devinfochg_evt_bh :Device info
change: handle(0x0001): persist_id(0x1)
+ [Wed Oct 15 09:35:05 2025] mpi3mr0: Device Info Changed: dev=0x0001 Form=0x2
+ [Wed Oct 15 09:35:05 2025] mpi3mr0: mpi3mr_devinfochg_evt_bh :Device info
change: handle(0x0001): persist_id(0x1)
+ [Wed Oct 15 09:35:06 2025] mpi3mr0: Device Info Changed: dev=0x0001 Form=0x2
+
+ This quickly exhausts the dmesg log buffer and reduces performance.
+
+ Add a check to only output these messages with a sufficient log level
+ set.
[Fix]
- This patch adds a check to block driver messages flooding the OS logs
- https://git.kernel.org/mkp/scsi/c/b0b7ee3b574a
+
+ This was fixed in 6.15-rc4 by:
+
+ commit b0b7ee3b574a72283399b9232f6190be07f220c0
+ Author: Ranjan Kumar <[email protected]>
+ Date: Tue Apr 15 15:45:46 2025 +0530
+ Subject: scsi: mpi3mr: Add level check to control event logging
+ Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b0b7ee3b574a72283399b9232f6190be07f220c0
+
+ Plucky already has this through upstream stable. This also landed in 6.12.31
+ and 6.6.93, which are not applied to noble yet.
[Test Plan]
+ Use a modern Dell Server, with a PERC H965i Front RAID controller.
+
+ On boot, dmesg will be flooded by:
+
+ [Wed Oct 15 09:35:05 2025] mpi3mr0: Device Info Changed: dev=0x0001 Form=0x2
+ [Wed Oct 15 09:35:05 2025] mpi3mr0: mpi3mr_devinfochg_evt_bh :Device info
change: handle(0x0001): persist_id(0x1)
+ [Wed Oct 15 09:35:05 2025] mpi3mr0: Device Info Changed: dev=0x0001 Form=0x2
+ [Wed Oct 15 09:35:05 2025] mpi3mr0: mpi3mr_devinfochg_evt_bh :Device info
change: handle(0x0001): persist_id(0x1)
+ [Wed Oct 15 09:35:06 2025] mpi3mr0: Device Info Changed: dev=0x0001 Form=0x2
+
+ If you install the below test kernel and reboot, these messages will be
hidden,
+ unless you set the log level to MPI3_DEBUG_EVENT.
+
+ https://launchpad.net/~mruffell/+archive/ubuntu/sf419539-test
+
[Where problems could occur]
- [Other Info]
+ This just adds a check to only output the messages when the correct log level
is
+ set. If a user was for some reason relying on these messages, they would need
to
+ set a higher log level on their module options.
+
+ If a regression were to occur, it could increase or decrease logging from
+ mpi3mr, or impact the functionality of mpi3mr.
--
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/2116103
Title:
[SRU] Dell: Add level check to control event logging
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Noble:
In Progress
Status in linux source package in Oracular:
Won't Fix
Status in linux source package in Plucky:
Fix Released
Bug description:
BugLink: https://bugs.launchpad.net/bugs/2116103
[Impact]
The current mpi3mr driver floods the kernel logs, spamming with entries
mentioning each and every device state change.
[Wed Oct 15 09:35:05 2025] mpi3mr0: Device Info Changed: dev=0x0001 Form=0x2
[Wed Oct 15 09:35:05 2025] mpi3mr0: mpi3mr_devinfochg_evt_bh :Device info
change: handle(0x0001): persist_id(0x1)
[Wed Oct 15 09:35:05 2025] mpi3mr0: Device Info Changed: dev=0x0001 Form=0x2
[Wed Oct 15 09:35:05 2025] mpi3mr0: mpi3mr_devinfochg_evt_bh :Device info
change: handle(0x0001): persist_id(0x1)
[Wed Oct 15 09:35:06 2025] mpi3mr0: Device Info Changed: dev=0x0001 Form=0x2
This quickly exhausts the dmesg log buffer and reduces performance.
Add a check to only output these messages with a sufficient log level
set.
[Fix]
This was fixed in 6.15-rc4 by:
commit b0b7ee3b574a72283399b9232f6190be07f220c0
Author: Ranjan Kumar <[email protected]>
Date: Tue Apr 15 15:45:46 2025 +0530
Subject: scsi: mpi3mr: Add level check to control event logging
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b0b7ee3b574a72283399b9232f6190be07f220c0
Plucky already has this through upstream stable. This also landed in 6.12.31
and 6.6.93, which are not applied to noble yet.
[Test Plan]
Use a modern Dell Server, with a PERC H965i Front RAID controller.
On boot, dmesg will be flooded by:
[Wed Oct 15 09:35:05 2025] mpi3mr0: Device Info Changed: dev=0x0001 Form=0x2
[Wed Oct 15 09:35:05 2025] mpi3mr0: mpi3mr_devinfochg_evt_bh :Device info
change: handle(0x0001): persist_id(0x1)
[Wed Oct 15 09:35:05 2025] mpi3mr0: Device Info Changed: dev=0x0001 Form=0x2
[Wed Oct 15 09:35:05 2025] mpi3mr0: mpi3mr_devinfochg_evt_bh :Device info
change: handle(0x0001): persist_id(0x1)
[Wed Oct 15 09:35:06 2025] mpi3mr0: Device Info Changed: dev=0x0001 Form=0x2
If you install the below test kernel and reboot, these messages will be
hidden,
unless you set the log level to MPI3_DEBUG_EVENT.
https://launchpad.net/~mruffell/+archive/ubuntu/sf419539-test
[Where problems could occur]
This just adds a check to only output the messages when the correct log level
is
set. If a user was for some reason relying on these messages, they would need
to
set a higher log level on their module options.
If a regression were to occur, it could increase or decrease logging from
mpi3mr, or impact the functionality of mpi3mr.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2116103/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
