Date: Thu, 9 Sep 2010 13:48:13 -0700 From: Jack Vogel <jfvogel@gmail.com> To: John Baldwin <jhb@freebsd.org> Cc: Kurt Jaeger <pi@opsec.eu>, freebsd-stable@freebsd.org Subject: Re: MSIX failure Message-ID: <AANLkTingpUm_TMVMfXm-777sVv6V92tVnPZ7Ymx684hg@mail.gmail.com> In-Reply-To: <201009091620.25299.jhb@freebsd.org> References: <AANLkTikdGGgpGhy4MJF_K-ttLvjQOBj%2BAb5r-a2uhJ_Y@mail.gmail.com> <201009091437.21563.jhb@freebsd.org> <AANLkTim68p1gO8ZBYz=Qi-jMUk8JeVJxhxLvsUHF-tyA@mail.gmail.com> <201009091620.25299.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Gareth's email bouncing for anybody else or is it just me? Gareth, set hw.pci.honor_msi_blacklist=0, you'll have to do that at boot btw. Tell me more exactly the make/model of the hardware so I might try to get my hands on one? Jack On Thu, Sep 9, 2010 at 1:20 PM, John Baldwin <jhb@freebsd.org> wrote: > On Thursday, September 09, 2010 3:04:27 pm Jack Vogel wrote: > > On Thu, Sep 9, 2010 at 11:37 AM, John Baldwin <jhb@freebsd.org> wrote: > > > > > On Thursday, September 09, 2010 12:41:07 pm Jack Vogel wrote: > > > > On Thu, Sep 9, 2010 at 7:33 AM, Kurt Jaeger <pi@opsec.eu> wrote: > > > > > > > > > Hi! > > > > > > > > > > > > Is this within a jail or something else along those lines? I > can't > > > > > > > reproduce the problem otherwise. Frustrating! Someone else on > the > > > > > list > > > > > > > might have ideas as to what could cause this. > > > > > > > > > > > > Nope, this's a normal host. I've got securelevel on 1, but doubt > that > > > > > > would affect this? > > > > > > > > > > I assume it affects it. > > > > > > > > > > http://www.freebsd.org/doc/en/books/faq/security.html#SECURELEVEL > > > > > > > > > > Basically, when the securelevel is positive, the kernel restricts > > > > > certain tasks; not even the superuser (i.e., root) is allowed to > > > > > do them. > > > > > > > > > > There: > > > > > > > > > > # Write to kernel memory via /dev/mem and /dev/kmem. > > > > > > > > > > So I assume it also restricts reading /dev/kmem ? > > > > > > > > > > > > > > OH YUCK, another root isn't really root, so is it also possibly > > > > the reason for the MSIX failure?? Is this pile, er feature, on by > > > default? > > > > > > securelevel does not affect any of the MSI/MSI-X bits. > > > > > > > Well then there's something else funny going on with that hardware, as at > > least MSI should work with the chipset, I am not able to get that exact > > skew from what I am told. > > I think the first would be to disable the MSI blacklists via a tunable to > see > if that enables MSI. > > -- > John Baldwin >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTingpUm_TMVMfXm-777sVv6V92tVnPZ7Ymx684hg>