On Thursday, September 09, 2010 3:04:27 pm Jack Vogel wrote: > On Thu, Sep 9, 2010 at 11:37 AM, John Baldwin <j...@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 <p...@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 _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
