Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 15 Jul 2020 23:46:34 +0300
From:      Lev Serebryakov <lev@FreeBSD.org>
To:        Yuri Pankov <yuripv@yuripv.dev>, Willem Jan Withagen <wjw@digiware.nl>, freebsd current <freebsd-current@freebsd.org>
Subject:   Re: Current panics on connecting disks to a LSI-3108 controller
Message-ID:  <3e4b85bc-e605-5a60-759f-c250cbe28a0a@FreeBSD.org>
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
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--OdNqU5Kj9mlijAEummkyV2hiQqDZmFAZR
Content-Type: multipart/mixed; boundary="oOWBdmlUmdWwUS2kBUKsDMwOtUAy0HVkS"

--oOWBdmlUmdWwUS2kBUKsDMwOtUAy0HVkS
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 14.07.2020 1:47, Yuri Pankov wrote:

>> AVAGO MegaRAID SAS FreeBSD mrsas driver version: 07.709.04.00-fbsd
>> mfi0: <Invader> port 0x6000-0x60ff mem 0xc7300000-0xc730ffff,0xc720000=
0-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 =3D 928, limiting to 128
>> mfi0: MaxCmd =3D 928, Drv MaxCmd =3D 128, MaxSgl =3D 70, state =3D 0xb=
73c03a0
>> .....
>> 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) - Firm=
ware version 4.290.00-4536
>>
>>
>> I have posted screenshots of the panic at:
>> =C2=A0=C2=A0=C2=A0=C2=A0 www.tegenbosch28.nl/FreeBSD/Crash-LSI3108
>>
>> But basically it crashes in
>> =C2=A0=C2=A0=C2=A0=C2=A0 mfi_tbolt_send_frame() +0x132
>>
>> So is there anybody out there that can help me with analyzing and fixi=
ng this panic?
>=20
> 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=
=2Emfi.mrsas_enable=3D1' from loader prompt.

 I'm puzzled. I'm have SuperMicro add-on card based on LSI/Avago/Broadcom=
 3008. An I'm using "mpr" driver:

mpr0: <Avago Technologies (LSI) SAS3008> port 0xe000-0xe0ff mem 0xf724000=
0-0xf724ffff,0xf7200000-0xf723ffff irq 16 at device 0.0 on pci1
mpr0: Firmware: 14.00.00.00, Driver: 23.00.00.00-fbsd
mpr0: IOCCapabilities: 7a85c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRet=
ry,EventReplay,MSIXIndex,HostDisc,FastPath,RDPQArray>

 "man mpr" mentions LSI-3108 too, and "man mfi" doesn't mention LSI-3xxx =
chips. Why does "mfi" attaches to LSI-3xxx? What is proper driver for the=
se chips?


--=20
// Lev Serebryakov


--oOWBdmlUmdWwUS2kBUKsDMwOtUAy0HVkS--

--OdNqU5Kj9mlijAEummkyV2hiQqDZmFAZR
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQKTBAEBCgB9FiEE+W0coLX0MYtnSzMK6rA8WL/cR48FAl8PaypfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEY5
NkQxQ0EwQjVGNDMxOEI2NzRCMzMwQUVBQjAzQzU4QkZEQzQ3OEYACgkQ6rA8WL/c
R49Dxg//TKpvK6aMMWGZmab8/TjSbpfRZbSmaTpm32ycz9gq3v/24HSFeBZIAPmu
wy6NKy5Fm3chP5n4q3hxYs1IqxsCZhvZIMjoIT9H1CoAFE6pg3Q5zGjYIHSnn/j+
ZWjzYLn7cIx1ejq+hiakrtIhofKIC6ezAwR4DM18GvM1Q1snkNCaWBoTOpMZLECM
cht7pcxeJgxO/krT097QeAHK7iIHtM0z04Rp+6T3YVIwa0zm2EBXM0kgcWRZ1jIY
+hN0pRlVxPIDfKSZHDb6V6DYf63Bo2hixbPF/7sNsBemxW9ApaDBKFWGYOVN2DNR
XOlnntKUIj1w8fIohjQcRb0VVzimzoV4IG+kT+BwJ4Gdp9YvyWSUJLgPLy9sxNuh
w1gdcvwj7KL/cWmZMOYeWlUDC9fHqgX9GwG2WHAWFhERy0kyVb3umk29ruNguir1
hQcT7AurmlDEUaAPLRhOl7KP/DX7Gw27I3/7LgSJ7McbKEj2fq/wTuVSSsRHGy/r
tC2dS2NDc/yGVwk2ra+KuU36vXckPJ7kJ6I4nzUppKkcbfzBZ7ZxVof3be9wyRHx
7eGW4DdvGdruQP0LHFa6S/8zoQ/eLy59rmrmJlRIqL2gSnr35qXPrXeS/lUJcnSq
WkrkYe80bOILFje59ytE5HuBbBFOLVg2Mh8haQr943YKqPDNTCI=
=dgH8
-----END PGP SIGNATURE-----

--OdNqU5Kj9mlijAEummkyV2hiQqDZmFAZR--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3e4b85bc-e605-5a60-759f-c250cbe28a0a>