You are not logged in.

#1 2016-02-28 16:22:26

Neuntoter
Member
Registered: 2016-02-28
Posts: 3

Issue with newer mpt2sas and mpt3sas(merged mpt2sas)

works fine from live cd from july 2015 and from installed system there of until I did system update.

Linux archiso 4.3.3-3-ARCH #1 SMP PREEMPT Wed Jan 20 08:12:23 CET 2016 x86_64 GNU/Linux
0b:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2308 PCI-Express Fusion-MPT SAS-2 (rev 05)
        Subsystem: LSI Logic / Symbios Logic Device 3020
        Physical Slot: 192
        Flags: fast devsel
        I/O ports at 5000 [size=256]
        Memory at fd4f0000 (64-bit, non-prefetchable) [size=64K]
        Memory at fd480000 (64-bit, non-prefetchable) [size=256K]
        Capabilities: [50] Power Management version 3
        Capabilities: [68] Express Endpoint, MSI 00
        Capabilities: [d0] Vital Product Data
        Capabilities: [a8] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [c0] MSI-X: Enable- Count=16 Masked-
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [1e0] #19
        Capabilities: [1c0] Power Budgeting <?>
        Capabilities: [190] #16
        Capabilities: [148] Alternative Routing-ID Interpretation (ARI)
        Kernel modules: mpt2sas
Feb 28 16:04:07 archiso kernel: mpt2sas0: MSI-X vectors supported: 16, no of cores: 1, max_msix_vectors: -1
Feb 28 16:04:07 archiso kernel: mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 59
Feb 28 16:04:07 archiso kernel: mpt2sas0: iomem(0x00000000fd4f0000), mapped(0xffffc90000220000), size(65536)
Feb 28 16:04:07 archiso kernel: mpt2sas0: ioport(0x0000000000005000), size(256)
Feb 28 16:04:07 archiso kernel: mpt2sas0: Allocated physical memory: size(14931 kB)
Feb 28 16:04:07 archiso kernel: mpt2sas0: Current Controller Queue Depth(9979), Max Controller Queue Depth(10240)
Feb 28 16:04:07 archiso kernel: mpt2sas0: Scatter Gather Elements per IO(128)
Feb 28 16:04:07 archiso kernel: mpt2sas0: _base_event_notification: timeout
Feb 28 16:04:07 archiso kernel: mpt2sas0: sending message unit reset !!
Feb 28 16:04:07 archiso kernel: mpt2sas0: message unit reset: SUCCESS
Feb 28 16:04:07 archiso kernel: mpt2sas0: failure at drivers/scsi/mpt2sas/mpt2sas_scsih.c:8498/_scsih_probe()!

Please Help.

Offline

#2 2016-02-28 23:00:19

Neuntoter
Member
Registered: 2016-02-28
Posts: 3

Re: Issue with newer mpt2sas and mpt3sas(merged mpt2sas)

I downgraded back to linux-4.1.5-1 and all works again so there is an issue with linux kernel somewhere between 4.1.5-1 and 4.3.3-3
From what I can tell it is directly related to mpt2sas.

Offline

#3 2016-03-03 05:39:12

severach
Member
Registered: 2015-05-23
Posts: 192

Re: Issue with newer mpt2sas and mpt3sas(merged mpt2sas)

Google that error. If you can't join in and help you can at least see there's a lot of interest.

I use a LSI 9211-8i IT and see no such errors.

05:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 02)
        Subsystem: LSI Logic / Symbios Logic Device 3020
        Physical Slot: 1-2
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 0
        Region 0: I/O ports at e000 [size=256]
        Region 1: Memory at f7d00000 (64-bit, non-prefetchable) [size=16K]
        Region 3: Memory at f7c80000 (64-bit, non-prefetchable) [size=256K]
        Expansion ROM at f7800000 [disabled] [size=512K]
        Capabilities: <access denied>
        Kernel driver in use: mpt3sas
        Kernel modules: mpt3sas

[    0.557931] mpt3sas version 09.102.00.00 loaded
[    0.558117] mpt2sas_cm0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (32839912 kB)
[    0.603006] mpt2sas_cm0: MSI-X vectors supported: 1, no of cores: 8, max_msix_vectors: -1
[    0.603071] mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 26
[    0.603073] mpt2sas_cm0: iomem(0x00000000f7d00000), mapped(0xffffc90003178000), size(16384)
[    0.603074] mpt2sas_cm0: ioport(0x000000000000e000), size(256)
[    0.659378] mpt2sas_cm0: sending message unit reset !!
[    0.660937] mpt2sas_cm0: message unit reset: SUCCESS
[    0.698003] mpt2sas_cm0: Allocated physical memory: size(7445 kB)
[    0.698006] mpt2sas_cm0: Current Controller Queue Depth(3307),Max Controller Queue Depth(3432)
[    0.698007] mpt2sas_cm0: Scatter Gather Elements per IO(128)
[    0.744818] mpt2sas_cm0: LSISAS2008: FWVersion(19.00.00.00), ChipRevision(0x02), BiosVersion(07.37.00.00)
[    0.744821] mpt2sas_cm0: Protocol=(
[    0.745112] mpt2sas_cm0: sending port enable !!
[    0.747420] mpt2sas_cm0: host_add: handle(0x0001), sas_addr(0x500605b0026b59e0), phys(8)
[    0.756670] mpt2sas_cm0: port enable: SUCCESS

Offline

#4 2016-03-03 06:08:00

Neuntoter
Member
Registered: 2016-02-28
Posts: 3

Re: Issue with newer mpt2sas and mpt3sas(merged mpt2sas)

Google shows 2 Posts... in the last year with that error. 1 being some scrape of my post. The other not seemingly pertaining to my issue.
It really bugs me when someone assumes that the first stop was to post on a forum with no searching. I searched issues for hours. Besides seeing that the mpt2sas driver was upgraded and no longer worked on the most recent LiveCD and that the latest upgraded system contains a combined mpt3sas and mpt2sas driver which also doesn't work there wasn't much to go on.

I found people having similar issues with 0 a solution given. None of which directly pertained to my situation or device and none listing the error.
I have exhausted what information I can find and short of delving into source code for a driver(which I have 0 experience with), I am not sure what help I can be.

SO if there is all of this interest please do direct me to it... If more information is needed feel free to ask.
The error is easily reproducible for me. I however have no clue what information would be relevant or if it's a known issue.

Offline

#5 2016-09-20 20:12:19

redshift_arch
Member
Registered: 2016-09-20
Posts: 1

Re: Issue with newer mpt2sas and mpt3sas(merged mpt2sas)

Neuntoter, I've opened the following bug today on Launchpad:

https://bugs.launchpad.net/ubuntu/+sour … ug/1625718

I think it's related to the kernel version, not the distribution.

Regards

Offline

#6 2021-04-10 18:08:33

yikesh
Member
Registered: 2021-04-10
Posts: 1

Re: Issue with newer mpt2sas and mpt3sas(merged mpt2sas)

I realize this is an older thread, but there's still a dearth of info out there on this issue. My symptoms were none of my disks attached to LSI SAS controllers showed up.  @Neuntoter I'm not sure if you ever resolved your issue on a newer kernel, but this just happened to me on a server after upgrading the kernel to 5.10.28-1-lts. I tried the stable kernel as well (5.11.12.arch1-1) but had the same issue. The SAS devices:

03:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)
04:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2116 PCI-Express Fusion-MPT SAS-2 [Meteor] (rev 02)

The error I saw in kernel logs was:

Apr 09 22:43:31 hostname kernel: mpt2sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:12011/_scsih_probe()!

However, this thread (https://bugzilla.kernel.org/show_bug.cgi?id=209177) pointed me to a solution that worked for me. As in the case of that bug report, I have a line in logs like:

Apr 09 22:43:31 hostname kernel: mpt2sas_cm1: Current Controller Queue Depth(3368),Max Controller Queue Depth(3439)

You can see that the queue depth is close to the max; it appears that it's hitting the max and causing problems per that bug report thread. Your logs seem to show something similar. Taking the advice from the thread and setting

mpt3sas.max_queue_depth=10000

in /boot/loader/entries/arch-lts.conf appears to have resolved the issue. It also fixes it on the stable kernel if I update the boot options. This does seem like it must be related to changes in the kernels, but I have also been adding disks to my JBOD, so I'm not sure if it gets aggravated with more drives present. Anyway, hopefully this is helpful to someone.

Offline

#7 2021-04-10 22:20:03

2ManyDogs
Forum Fellow
Registered: 2012-01-15
Posts: 4,645

Re: Issue with newer mpt2sas and mpt3sas(merged mpt2sas)

Thanks for the contribution, but as you note this thread is very old. Closing.

Offline

Board footer

Powered by FluxBB