Has anything changed from 11.2 to 12.0 in PCI MSI/MSIX path?
Rajesh Kumar
rajfbsd at gmail.com
Tue Oct 30 08:23:04 UTC 2018
Hi John,
Thanks for your updates. I assume you are talking about having a unified
intr_machdep.h compared to having seperate amd64 and i386 versions.
Can you please update this thread once all changes are MFC complete or tag
me in necessary place? So that I can give a try in my board once it's ready.
On Mon, Oct 29, 2018 at 11:08 PM John Baldwin <jhb at freebsd.org> wrote:
> On 10/25/18 10:24 AM, Rajesh Kumar wrote:
> > Hi John,
> >
> > Thanks a lot. It helps. I backported the changes to 11.2 and tried
> booting in my board with success without any need for the said tunables.
> >
> > I see those changes are marked for MFC after 2 Weeks. But I don't see
> them still in stable/11 branch. So, will it be taken into stable/11 branch
> by any chance? If not, can the backported changes be submitted for review
> to take into stable/11 branch?
>
> I'm working on the MFC. The current patch I've tested an MFC of is the
> one to
> unify sys/x86/include/intr_machdep.h as a precursor to MFC'ing this change.
>
> > On Thu, Oct 25, 2018 at 1:17 AM John Baldwin <jhb at freebsd.org <mailto:
> jhb at freebsd.org>> wrote:
> >
> > On 10/24/18 3:40 AM, Rajesh Kumar wrote:
> > > Hi,
> > >
> > > I have a amd64 based board. When I tried to boot 11.1 (or) 11.2 in
> that, I
> > > needed the following tunables to be set from loader prompt to get
> it booted
> > > (otherwise machine reboots continuously).
> > >
> > > hw.usb.xhci.msi=0
> > > hw.usb.xhci.msix=0
> > > hw.pci.enable_msi=0
> > > hw.pci.enable_msix=0
> > >
> > > But, when I tried with 12.0 - ALPHA4, I could able to get it
> booted without
> > > any tunables. So, has anything changed significantly on PCI
> MSI/MSI-X
> > > path?
> > >
> > > Note: I have a forum topic with my observations about the issue on
> > > 11.1/11.2 in the following thread
> > >
> https://forums.freebsd.org/threads/freebsd-11-1-installation-fails-and-rebooting.65814/
> > >
> > > Let me know if you need any details.
> >
> > I believe this was fixed by r338360.
> >
> > --
> > John Baldwin
> >
>
>
> --
> John Baldwin
>
More information about the freebsd-drivers
mailing list