On Tue, Nov 05, 2019 at 05:04:41PM -0500, Chris Ross wrote:
> > However, if you've already placed
> > mpr_load="YES" in your /etc/loader.conf and rebooted your device, then you
> > probably need to move into a diagnostic phase.
>
> Yeah. I think I see what PCI id is missing in the driver, after digging
> around in the sources. I was just hoping it was a process/human error.
> I'll get another machine running a build, and see if I can stub it in.
Okay. Well, the simple try didn't magically work. I added a few lines in
dev/mpr/mpr_pci.c in releng/12.0, built a new ISO, and booted. Now it
recognizes the part, but says the following:
pcib7: <ACPI PCI-PCI bridge> [...]
pci7: <ACPI PCI bus> numa-domain 0 on pcib7
mpr0: <Avago Technologies (LSI) SAS3516_2> port 0x7000-0x70ff mem
0xb8000000-0xb80fffff,0xb7f00000-0xb7ffffff,0xb7e00000-0xb7efffff at device 0.0
numa-domain 0 on pci7
mpr0: IOC in fault state 0x0, resetting
mpr0: IOC in fault state 0x0, resetting
mpr0: IOC in fault state 0x0, resetting
mpr0: IOC in fault state 0x0, resetting
mpr0: IOC in fault state 0x0, resetting
mpr0: IOC in fault state 0x0, resetting
There is about a 4 second pause between each of the "in fault state, resetting"
lines.
This may not be a freebsd-stable converstion any longer. I'm going to
switch over to freebsd-drivers, unless someone has a suggestion of a
better list for trying to figure out if small adjustments can be made to
the mpr driver to accept this device.
Thanks all.
- Chris
_______________________________________________
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
