Am Wed, 24 Feb 2016 22:04:29 +0200
Ivan Klymenko schrieb:
> After update from r295867 to r295994:
>
> ...
> /usr/local/bin/ccache cc -O2 -pipe -march=native -fno-strict-aliasing
> -DRT_OS_FREEBSD
> -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DSUPDRV_WITH_RELEASE_LOGGER -DVBOX
> -DRT_WITH_VBOX -w
> -DVB
Yeah, still getting the -100 error, I do have sendmail disabled. I just
tested with sendmail up and running then add the VF's and it still shows
the error message.
On Wed, Feb 24, 2016 at 8:04 PM, Eric Joyner wrote:
> Are you still getting the -100 errors when trying to load the VF driver?
>
>
Are you still getting the -100 errors when trying to load the VF driver?
I've tried SR-IOV on a system here, and I can confirm that traffic stops
passing on the PF interface when you create a VF interface. That didn't
used to happen, so I'm investigating why that is right now.
On Wed, Feb 24, 201
Shawn Webb wrote:
> We at HardenedBSD have an experimental branch that is kept up-to-date
> with FreeBSD HEAD along with Jean-Sebastien's excellent work (and
> HardenedBSD's awesomeness on top of that).
>
> The code is here:
>
> https://github.com/HardenedBSD/hardenedBSD-playground/tree/hardene
On Wed, 24 Feb 2016, Eax Melanhovich wrote:
> Hello.
>
> Yesterday I built a kernel and world using master branch (6a8922d3) of
> FreeBSD GitHub repository (a mirror of SVN as I understand?). Today I
> got a "lock order reversal" report:
>
> http://i.imgur.com/jDZ4A3O.png
>
> According to this FAQ
After update from r295867 to r295994:
...
/usr/local/bin/ccache cc -O2 -pipe -march=native -fno-strict-aliasing
-DRT_OS_FREEBSD -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DSUPDRV_WITH_RELEASE_LOGGER
-DVBOX -DRT_WITH_VBOX -w -DVBOX_WITH_HARDENING -DVBOX_WITH_64_BITS_GUESTS
-DRT_ARCH_AMD64 -march=native
On Wed, Feb 24, 2016 at 5:32 PM, Miguel C wrote:
>
>
> On Wed, Feb 24, 2016 at 7:28 AM, Hans Petter Selasky
> wrote:
>
>> On 02/24/16 00:58, Miguel C wrote:
>>
>>> I just noticed the last messages were never CC'ed to the list
>>>
>>> On Wed, Feb 10, 2016 at 8:56 PM, Otacílio
>>> wrote:
>>>
>>>
On Wed, Feb 24, 2016 at 7:28 AM, Hans Petter Selasky
wrote:
> On 02/24/16 00:58, Miguel C wrote:
>
>> I just noticed the last messages were never CC'ed to the list
>>
>> On Wed, Feb 10, 2016 at 8:56 PM, Otacílio
>> wrote:
>>
>> Miguel, I have noted that on my system, sometime I get a file not fo
Decided to do some more tests, I actually have a second board with sr-iov
capabilities that I used for awhile with vmware esxi. I decided to test
this out and unfortunately it won't activate, it is giving the no space
left on device error message. I double checked bios and all VT-d related
options
On Wed, Feb 24, 2016 at 12:40:27PM +0100, Jean-S??bastien P??dron wrote:
> On 24/02/2016 10:59, Carsten Kunze wrote:
> > Hello,
>
> Hi!
>
> > At the moment CURRENT can't be used on laptops with i915 graphics,
> > so it may not harm to integrate a buggy i915 support in CURRENT. The
> > advantage
Hello.
Yesterday I built a kernel and world using master branch (6a8922d3) of
FreeBSD GitHub repository (a mirror of SVN as I understand?). Today I
got a "lock order reversal" report:
http://i.imgur.com/jDZ4A3O.png
According to this FAQ it could be a sign of a deadlock:
https://www.freebsd.org/
On 24/02/2016 10:59, Carsten Kunze wrote:
> Hello,
Hi!
> At the moment CURRENT can't be used on laptops with i915 graphics,
> so it may not harm to integrate a buggy i915 support in CURRENT. The
> advantage would be that more users would test the driver and could
> give response. This may speed
Hello,
Haswell graphics (i915) still seems not to be in CURRENT. There is a suggested
test procedure on
https://wiki.freebsd.org/Graphics/Update%20i915%20GPU%20driver%20to%20Linux%203.8
but currently I'm to busy with other projects to test this.
At the moment CURRENT can't be used on laptops
13 matches
Mail list logo