Date: Tue, 14 Jul 2020 02:39:19 +0200 From: Willem Jan Withagen <wjw@digiware.nl> To: Yuri Pankov <yuripv@yuripv.dev>, freebsd current <freebsd-current@freebsd.org> Subject: Re: Current panics on connecting disks to a LSI-3108 controller Message-ID: <80510d48-adfe-3f9c-a7cd-81a7e88d9d71@digiware.nl> In-Reply-To: <266ce56a-0d95-b61a-4757-4ccdc2533ae2@yuripv.dev> References: <1406943a-6028-26ae-012f-e83903f2b299@digiware.nl> <266ce56a-0d95-b61a-4757-4ccdc2533ae2@yuripv.dev>
next in thread | previous in thread | raw e-mail | index | archive | help
On 14-7-2020 00:47, Yuri Pankov wrote: > Willem Jan Withagen wrote: >> Hi, >> >> I have this Supermicro SUPERSERVER®2028TP >> Which hold four nodes each with a X10DRT-PT motherboard >> and a LSI-3108 SAS controller connecting to 6 disks. >> >> Trying to run the most recent current snapshot on it. >> # uname -a >> FreeBSD quadbox-d.digiware.nl 13.0-CURRENT FreeBSD 13.0-CURRENT #0 >> r363032: Thu Jul 9 04:13:17 UTC 2020 >> root@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC >> amd64 >> >> I have installed the OS on a SATA flash DOM. >> Booting works fine as long as there are no disks connected to >> LSI-3108 controller. >> Booting with SAS disks connected results in a panic. >> Attaching a SAS disk to the LSI-3108 controller give a panic as well. >> >> >> >> AVAGO MegaRAID SAS FreeBSD mrsas driver version: 07.709.04.00-fbsd >> mfi0: <Invader> port 0x6000-0x60ff mem >> 0xc7300000-0xc730ffff,0xc7200000-0xc72fffff irq 26 at device >> 0.0 numa-domain 0 on pci3 >> mfi0: Using MSI >> mfi0: Megaraid SAS driver Ver 4.23 >> mfi0: FW MaxCmds = 928, limiting to 128 >> mfi0: MaxCmd = 928, Drv MaxCmd = 128, MaxSgl = 70, state = 0xb73c03a0 >> ..... >> mfi0: 54944 (boot + 6s/0x0020/info) - Firmware initialization started >> (PCI ID 005d/1000/0809/15d9) >> pcib4: <ACPI PCI-PCI bridge>mfi0: 54945 (boot + 6s/0x0020/info) - >> Firmware version 4.290.00-4536 >> >> >> I have posted screenshots of the panic at: >> www.tegenbosch28.nl/FreeBSD/Crash-LSI3108 >> >> But basically it crashes in >> mfi_tbolt_send_frame() +0x132 >> >> So is there anybody out there that can help me with analyzing and >> fixing this panic? > > I guess it's not the answer you are looking for, but you could try the > mrsas driver and check if it's behaves better for you, by setting 'set > hw.mfi.mrsas_enable=1' from loader prompt. That was a great suggestion. And what I read from the manual page, mrsas plays even nicer with CAM which is a plus. I guess that there are reason not to do this by default. So one gets mrsas unless it does not attach to that specific card in the system? --WjW
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?80510d48-adfe-3f9c-a7cd-81a7e88d9d71>