Update: If you’re having these issues, then you’ve probably bought this card from AliExpress or eBay and these cards are bad/damaged…
Linux boasts the best hardware driver support among operating systems (let’s just say some Windows drivers I’ve used caused crashes, slowdowns, or were simply unusable).
When it comes to SCSI Host Bus Adapters (HBAs), all modern cards are typically well-supported. So, if you’re building a machine, there’s a very high chance (almost 99%) that you’ll automatically find a suitable kernel module to initialize and activate your hardware, allowing you to use various software tools for disk management.
However, you might occasionally encounter an issue in the kernel system log (or journal) that looks something like this:
[Sun Jun 9 01:20:59 2024] mpt3sas_cm0: log_info(0x30030109): originator(IOP), code(0x03), sub_code(0x0109)
[Sun Jun 9 01:20:59 2024] mpt3sas_cm0: log_info(0x30030109): originator(IOP), code(0x03), sub_code(0x0109)
[Sun Jun 9 01:20:59 2024] mpt3sas_cm0: log_info(0x30030109): originator(IOP), code(0x03), sub_code(0x0109)
[Sun Jun 9 01:20:59 2024] mpt3sas_cm0: log_info(0x30030109): originator(IOP), code(0x03), sub_code(0x0109)
[Sun Jun 9 01:20:59 2024] mpt3sas_cm0: log_info(0x30030109): originator(IOP), code(0x03), sub_code(0x0109)
[Sun Jun 9 01:20:59 2024] mpt3sas_cm0: log_info(0x30030109): originator(IOP), code(0x03), sub_code(0x0109)
[Sun Jun 9 01:20:59 2024] mpt3sas_cm0: log_info(0x30030109): originator(IOP), code(0x03), sub_code(0x0109)
[Sun Jun 9 01:20:59 2024] mpt3sas_cm0: log_info(0x30030109): originator(IOP), code(0x03), sub_code(0x0109)
[Sun Jun 9 01:20:59 2024] mpt3sas_cm0: log_info(0x30030109): originator(IOP), code(0x03), sub_code(0x0109)
[Sun Jun 9 01:20:59 2024] mpt3sas_cm0: log_info(0x30030109): originator(IOP), code(0x03), sub_code(0x0109)
What do these messages mean? Is there a problem?
Unfortunately, querying the linux-scsi mailing list didn’t yield any helpful information. However, by observing various user-level applications, it appears that some tools use one version of the SCSI API, while others use a different version (let’s call them version 1 and version 2).
With version 1, every interaction with the device (opening communication, sending commands, retrieving data, closing communication) generates these messages. For example, using the drivetemp kernel module with the s-tui tool will produce these messages. Conversely, other tools that communicate directly with the HBA won’t generate them.
In summary, these messages are harmless. If there’s a genuine error, you’ll see a clear indication in the system log or journal.
Update: If you’re having these issues, then you’ve probably bought this card from AliExpress or eBay and these cards are bad/damaged…
In summary, these messages are harmless. If there’s a genuine error, you’ll see a clear indication in the system log or journal.
So which one is it?
After writing this post, I talked to few people who had the exact issue. I asked them to take out the card and look for the manufacturer logo. None of them had the logo so all of those cards were fake
Long story short – if you have this issue, you can either ignore these message (the card works just fine) or replace the card
Here’s an additional data point:
I flashed the latest Avago firmware onto a Dell OEM version of a SAS9305-16i and use it in IT mode. Card works fine, but does generate these messages.
I have thes messages only when running commands like storcli or storcli64 to get temperature status of my HBAs. Cards seem to work fine though.
In the logs they are marked as warnings, not errors, critical, or alerts so I agree they could be ignored.
A similar warning appeared on one of my machines, but sometimes it could run normally, and occasionally it would be accompanied by a kernel crash, causing a reboot. Is this also a problem with HBA cards?
“`
[907367.415253] mpt3sas_cm7: log_info(0x30030109): originator(IOP), code(0x03), sub_code(0x0109)
[907367.415980] mpt3sas_cm7: log_info(0x30030109): originator(IOP), code(0x03), sub_code(0x0109)
[907367.454756] mpt3sas_cm0: log_info(0x310f0400): originator(PL), code(0x0f), sub_code(0x0400)
[907367.455030] mpt3sas_cm0: log_info(0x3003011d): originator(IOP), code(0x03), sub_code(0x011d)
[907367.461059] mpt3sas_cm1: log_info(0x310f0400): originator(PL), code(0x0f), sub_code(0x0400)
[907367.461433] mpt3sas_cm1: log_info(0x3003011d): originator(IOP), code(0x03), sub_code(0x011d)
[907367.465505] BUG: unable to handle page fault for address: 00000000000d00c2
[907367.465896] #PF: supervisor read access in kernel mode
[907367.466149] #PF: error_code(0x0000) – not-present page
[907367.466383] PGD 10bb6fef067 P4D 10cca676067 PUD 10376bce067 PMD 0
[907367.466573] Oops: 0000 [#1] PREEMPT SMP NOPTI
[907367.466759] CPU: 77 PID: 0 Comm: swapper/77 Kdump: loaded Tainted: P OE ——– — 5.14.0-284.25.1.el9_2.x86_64 #1
[907367.467143] Hardware name: N/A N/A/BS56M2C20S, BIOS 6.10.55 08/27/2025
[907367.467345] RIP: 0010:_base_interrupt+0xa/0x40 [mpt3sas]
[907367.467569] Code: 7b 68 00 74 96 b8 00 01 00 00 8b 7b 3c 66 89 43 68 e8 8a 46 b9 cf eb 83 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 8b 16 31 c0 ba c0 00 00 00 00 75 0b 80 7e 68 00 b8 01 00 00 00 74 05 c3 cc
[907367.468008] RSP: 0018:ff50a90b1a168f40 EFLAGS: 00010046
[907367.468235] RAX: 0000000000000000 RBX: ff46bfa2f8223e80 RCX: 000000000000080b
[907367.468471] RDX: 00000000000d0002 RSI: ff46bfa2f8222300 RDI: 00000000000005f2
[907367.468709] RBP: ff46bfa218c540c4 R08: 0003393ef37644e7 R09: 0000000000000000
[907367.468952] R10: 0000000000000000 R11: ff50a90b1a168ff8 R12: 0000000000000000
[907367.469211] R13: ff50a90b1a168f84 R14: 00000000000005f2 R15: ff46bfa218c54000
[907367.469478] FS: 0000000000000000(0000) GS:ff46c19c7df40000(0000) knlGS:0000000000000000
[907367.469757] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[907367.470028] CR2: 00000000000d00c2 CR3: 0000010d02c7c004 CR4: 0000000000771ee0
[907367.470309] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[907367.470593] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400
[907367.470878] PKRU: 55555554
[907367.471165] Call Trace:
[907367.471455]
[907367.471744] __handle_irq_event_percpu+0x3a/0x190
[907367.472049] handle_irq_event+0x58/0xb0
[907367.472351] handle_edge_irq+0x93/0x240
[907367.472661] __common_interrupt+0x3e/0xa0
[907367.473178] common_interrupt+0x7b/0xa0
[907367.473554]
[907367.473887]
[907367.474219] asm_common_interrupt+0x22/0x40
[907367.474556] RIP: 0010:cpuidle_enter_state+0xd2/0x400
[907367.474890] Code: 49 89 c5 0f 1f 44 00 00 31 ff e8 29 a8 8e ff 45 84 ff 74 12 9c 58 f6 c4 02 0f 85 12 03 00 00 31 ff e8 22 b6 94 ff fb 45 85 f6 88 15 01 00 00 49 63 d6 4c 2b 2c 24 48 8d 04 52 48 8d 04 82 49
[907367.475609] RSP: 0018:ff50a90b18887e80 EFLAGS: 00000202
[907367.475979] RAX: ff46c19c7df6ab80 RBX: 0000000000000002 RCX: 000000000000001f
[907367.476358] RDX: 0000000000000000 RSI: 000000003cf3cf3d RDI: 0000000000000000
[907367.476745] RBP: ff82a90afed41538 R08: 0003393ef3764063 R09: 0000000000000018
[907367.477136] R10: 0000000000001709 R11: 0000000000000229 R12: ffffffff95aace20
[907367.477529] R13: 0003393ef3764063 R14: 0000000000000002 R15: 0000000000000000
[907367.477927] cpuidle_enter+0x29/0x40
[907367.478348] cpuidle_idle_call+0x12c/0x1c0
[907367.478768] do_idle+0x7b/0xe0
[907367.479164] cpu_startup_entry+0x19/0x20
[907367.479557] start_secondary+0x116/0x140
[907367.479947] secondary_startup_64_no_verify+0xe5/0xeb
[907367.480334]
“`