Haswell graphics (i915) still not in CURRENT

2016-02-24 Thread Carsten Kunze 
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 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 
up the debugging/testing of this driver.

--Carsten
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Haswell graphics (i915) still not in CURRENT

2016-02-24 Thread Jean-Sébastien Pédron 
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 up the debugging/testing of this
> driver.

The problem is not the stability of Haswell support, but more the
regressions on already supported GPUs.

Currently, there is one big regression:
https://github.com/freebsd/freebsd-base-graphics/issues/2

It takes seconds to panic a Sandybridge or Haswell (so I suppose Ivy
Bridge is impacted too).

Once this is fixed (and so far my attempts failed), I believe the patch
can go in -CURRENT. Haswell support won't be rock solid but anyway,
Linux 3.8, the base we use, had only initial support. Many bugfixes came
in Linux 3.9 and 3.10. Hopefully, we'll get there more quickly.

-- 
Jean-Sébastien Pédron



signature.asc
Description: OpenPGP digital signature

Lock order reversal in CURRENT

2016-02-24 Thread Eax Melanhovich 
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/doc/faq/troubleshoot.html#idp63366608

Do I have to report this issue anywhere except freebsd-current@ ?

-- 
Best regards,
Eax Melanhovich
http://eax.me/
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Haswell graphics (i915) still not in CURRENT

2016-02-24 Thread Shawn Webb 
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 would be that more users would test the driver and could
> > give response. This may speed up the debugging/testing of this
> > driver.
> 
> The problem is not the stability of Haswell support, but more the
> regressions on already supported GPUs.
> 
> Currently, there is one big regression:
> https://github.com/freebsd/freebsd-base-graphics/issues/2
> 
> It takes seconds to panic a Sandybridge or Haswell (so I suppose Ivy
> Bridge is impacted too).
> 
> Once this is fixed (and so far my attempts failed), I believe the patch
> can go in -CURRENT. Haswell support won't be rock solid but anyway,
> Linux 3.8, the base we use, had only initial support. Many bugfixes came
> in Linux 3.9 and 3.10. Hopefully, we'll get there more quickly.

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/hardened/experimental/master-i915

Latest builds are here:

http://jenkins.hardenedbsd.org/builds/HardenedBSD-CURRENT-i915kms-amd64-LATEST/ISO-IMAGES/

Thanks,

-- 
Shawn Webb
HardenedBSD

GPG Key ID:  0x6A84658F52456EEE
GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89  3D9E 6A84 658F 5245 6EEE


signature.asc
Description: PGP signature

Re: sr-iov issues, reset_hw() failed with error -100

2016-02-24 Thread Ultima 
 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 are enabled and have hw.ix.num_queues="4" in /boot/loader.conf. Is
there anything else that may need to be set? .(It did work on vmware)

 For my second test, I moved the X540-AT1 to the board with the X540-AT2.
It functioned with the same issues as the AT2 tho.


I don't think I listed the motherboards in question yet so ill list them
now.

S1200BTLRM -
http://ark.intel.com/products/69633/Intel-Server-Board-S1200BTLRM?q=S1200BTLRM
MD80-TM0 - http://b2b.gigabyte.com/products/product-page.aspx?pid=5146#ov

I'm not sure if it will be of any help tho.

Ultima
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: pwcview and cheese - Device not configured / Invalid argument erros

2016-02-24 Thread Miguel C 
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 found
>>> error, like your problem. So, I unplugged the webcam and plug it again
>>> and
>>> it works. It is no frequently but occurs. Your camera is fixed or you can
>>> try something like this?
>>>
>>>
>> Nah its fixed :P
>>
>> Its an acer ultrabook, the devices is conencted as a usb but its not like
>> I
>> can plug it of  unless I remove the LCD or something :P
>>
>> I was jsut think that this might be driver related, which seems to be uvc:
>>
>> % v4l2-dbg -D
>> Driver info:
>>  Driver name   : uvcvideo
>>  Card type : 1.3M HD WebCam
>>  Bus info  : usb-/dev/usb-/dev/usb
>>  Driver version: 2.6.38
>>  Capabilities  : 0x8421
>>  Video Capture
>>  Streaming
>>  Extended Pix Format
>>  Device Capabilities
>>
>> maybe its a bug in the driver that presenting something unexpected to
>> /dev/video, I was just tried with ffpmeg, recompiled with v4l support and
>> get the same error using -i /dev/video
>>
>> [video4linux2,v4l2 @ 0x80ac6f000] ioctl(VIDIOC_STREAMON): Device not
>> configured
>> /dev/video0: Device not configured
>>
>>
> Hi,
>
> Can you try to get a newer version of webcamd:
>
> pkg install -f webcamd
>

This would just reinstall the one I already have (cause I do have the
latest version from ports), but in any case I did try to reinstall and
recompile a few times.


> Need to run the command below to make webamd re-attach.
>
> Further, try "usbconfig -d ugenX.1 reset", where X is the bus number for
> your webcam device.
>

Tried that too, I need to restart webcamd after doing it, but it still gets
me the same result.

>
> Else it is possible to compile webcamd with debugging on, and run it in
> the foreground to see what the error is about.
>
>
I was assuming it was a driver or permissions issue, but its certainly a
good idea to see if I get any debug info from webcamd, recompiling with
DEBUG on.

FYI today even cheese fails with:
"cheese:18761): cheese-WARNING **: Device '/dev/video0' is busy:
gstv4l2object.c(3267): gst_v4l2_object_set_format_full ():
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin35/GstV4l2Src:v4l2src1:
"

This is after restarting and I have not upgrade kernel/userland since I've
noticed this issue so that's strange.


> --HPS
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: pwcview and cheese - Device not configured / Invalid argument erros

2016-02-24 Thread Miguel C 
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:
>>>
>>> Miguel, I have noted that on my system, sometime I get a file not found
 error, like your problem. So, I unplugged the webcam and plug it again
 and
 it works. It is no frequently but occurs. Your camera is fixed or you
 can
 try something like this?


>>> Nah its fixed :P
>>>
>>> Its an acer ultrabook, the devices is conencted as a usb but its not
>>> like I
>>> can plug it of  unless I remove the LCD or something :P
>>>
>>> I was jsut think that this might be driver related, which seems to be
>>> uvc:
>>>
>>> % v4l2-dbg -D
>>> Driver info:
>>>  Driver name   : uvcvideo
>>>  Card type : 1.3M HD WebCam
>>>  Bus info  : usb-/dev/usb-/dev/usb
>>>  Driver version: 2.6.38
>>>  Capabilities  : 0x8421
>>>  Video Capture
>>>  Streaming
>>>  Extended Pix Format
>>>  Device Capabilities
>>>
>>> maybe its a bug in the driver that presenting something unexpected to
>>> /dev/video, I was just tried with ffpmeg, recompiled with v4l support and
>>> get the same error using -i /dev/video
>>>
>>> [video4linux2,v4l2 @ 0x80ac6f000] ioctl(VIDIOC_STREAMON): Device not
>>> configured
>>> /dev/video0: Device not configured
>>>
>>>
>> Hi,
>>
>> Can you try to get a newer version of webcamd:
>>
>> pkg install -f webcamd
>>
>
> This would just reinstall the one I already have (cause I do have the
> latest version from ports), but in any case I did try to reinstall and
> recompile a few times.
>
>
>> Need to run the command below to make webamd re-attach.
>>
>> Further, try "usbconfig -d ugenX.1 reset", where X is the bus number for
>> your webcam device.
>>
>
> Tried that too, I need to restart webcamd after doing it, but it still
> gets me the same result.
>
>>
>> Else it is possible to compile webcamd with debugging on, and run it in
>> the foreground to see what the error is about.
>>
>>
> I was assuming it was a driver or permissions issue, but its certainly a
> good idea to see if I get any debug info from webcamd, recompiling with
> DEBUG on.
>
> FYI today even cheese fails with:
> "cheese:18761): cheese-WARNING **: Device '/dev/video0' is busy:
> gstv4l2object.c(3267): gst_v4l2_object_set_format_full ():
> /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin35/GstV4l2Src:v4l2src1:
> "
>
> This is after restarting and I have not upgrade kernel/userland since I've
> noticed this issue so that's strange.
>
> Ok after recompiling with debug and running in foreground I see what seems
to be a driver related error:

% sudo webcamd -N 1-3M-HD-WebCam-SuYin
multimedia/webcamd r2d2
: USB HID core driver
Linux video capture interface: v2.00
lirc_dev: IR Remote Control driver registered, major 14
IR NEC protocol handler initialized
IR RC5(x/sz) protocol handler initialized
IR RC6 protocol handler initialized
IR JVC protocol handler initialized
IR Sony protocol handler initialized
IR SANYO protocol handler initialized
IR LIRC bridge handler initialized
IR XMP protocol handler initialized
b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver chip loaded
successfully
uvcvideo: Unable to create debugfs directory
USB Video Class driver (1.1.1)
cpia2: V4L-Driver for Vision CPiA2 based cameras v3.0.1
pvrusb2: V4L in-tree version:Hauppauge WinTV-PVR-USB2 MPEG2 Encoder/Tuner
pvrusb2: Debug mask is 31 (0x1f)
USBVision USB Video Device Driver for Linux : 0.9.11
em28xx: Registered (Em28xx v4l2 Extension) extension
em28xx: Registered (Em28xx dvb Extension) extension
Attached to ugen0.5[0]
uvcvideo: Found UVC 1.00 device 1.3M HD WebCam (064e:c321)
Creating /dev/video0
uvcvideo: Failed to submit URB 0 (-32). <-- Shows if I run
cheese (nothing happens here if I run pwcview


>> --HPS
>>
>
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

emulators/virtualbox-ose-kmod build error

2016-02-24 Thread Ivan Klymenko 
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  -Werror -D_KERNEL -DKLD_MODULE -nostdinc  
-Iinclude -I. -Ir0drv -I. -I/usr/src/sys -fno-common  -fno-omit-frame-pointer 
-mno-omit-leaf-frame-pointer  -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse 
-msoft-float  -fno-asynchronous-unwind-tables -ffreestanding -fwrapv 
-fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef 
-Wno-pointer-sign -D__printf__=__freebsd_kprintf__  -Wmissing-include-dirs 
-fdiagnostics-show-option  -Wno-unknown-pragmas  
-Wno-error-tautological-compare -Wno-error-empty-body  
-Wno-error-parentheses-equality -Wno-error-unused-function  
-Wno-error-pointer-sign -Wno-error-shift-negative-value  -fvectorize 
-fslp-vectorize -fbloc
 ks -fcolor-diagnostics -mno-aes -mno-avx  -std=iso9899:1999 -c 
/media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c
 -o memobj-r0drv-freebsd.o
--- assert-r0drv-freebsd.o ---
In file included from 
/media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/assert-r0drv-freebsd.c:34:
In file included from 
/media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/the-freebsd-kernel.h:39:
/usr/src/sys/sys/bus.h:659:10: fatal error: 'device_if.h' file not found
#include "device_if.h"
 ^
--- alloc-r0drv-freebsd.o ---
In file included from 
/media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/alloc-r0drv-freebsd.c:34:
In file included from 
/media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/the-freebsd-kernel.h:39:
/usr/src/sys/sys/bus.h:659:10: fatal error: 'device_if.h' file not found
#include "device_if.h"
 ^
--- assert-r0drv-freebsd.o ---
1 error generated.
--- initterm-r0drv-freebsd.o ---
In file included from 
/media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/initterm-r0drv-freebsd.c:34:
In file included from 
/media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/the-freebsd-kernel.h:39:
/usr/src/sys/sys/bus.h:659:10: fatal error: 'device_if.h' file not found
#include "device_if.h"
 ^
--- assert-r0drv-freebsd.o ---
*** [assert-r0drv-freebsd.o] Error code 1

make[3]: stopped in 
/media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv
--- initterm-r0drv-freebsd.o ---
1 error generated.
--- alloc-r0drv-freebsd.o ---
1 error generated.
--- initterm-r0drv-freebsd.o ---
*** [initterm-r0drv-freebsd.o] Error code 1

make[3]: stopped in 
/media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv
--- memobj-r0drv-freebsd.o ---
In file included from 
/media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c:36:
In file included from 
/media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/the-freebsd-kernel.h:39:
/usr/src/sys/sys/bus.h:659:10: fatal error: 'device_if.h' file not found
#include "device_if.h"
 ^
--- alloc-r0drv-freebsd.o ---
*** [alloc-r0drv-freebsd.o] Error code 1

make[3]: stopped in 
/media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv
--- memobj-r0drv-freebsd.o ---
1 error generated.
*** [memobj-r0drv-freebsd.o] Error code 1

make[3]: stopped in 
/media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv
4 errors

make[3]: stopped in 
/media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv
*** [all] Error code 2

make[2]: stopped in 
/media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src
1 error

make[2]: stopped in 
/media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src
===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
the maintainer.
*** Error code 1

Stop.
make[1]:

Re: Lock order reversal in CURRENT

2016-02-24 Thread Benjamin Kaduk 
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 it could be a sign of a deadlock:
>
> https://www.freebsd.org/doc/faq/troubleshoot.html#idp63366608
>
> Do I have to report this issue anywhere except freebsd-current@ ?

That particular one, though not in the table at
http://sources.zabbadoz.net/freebsd/lor.html, seems similar enough to a
ufs/devfs entry that shows up very often and is harmless, to make me think
that just the mail you have sent is quite sufficient.

Thanks,

Ben Kaduk
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Aw: Re: Haswell graphics (i915) still not in CURRENT

2016-02-24 Thread Carsten Kunze 
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/hardened/experime
> ntal/master-i915
> 
> Latest builds are here:
> 
> http://jenkins.hardenedbsd.org/builds/HardenedBSD-CURRENT-i915kms-amd64-LATE
> ST/ISO-IMAGES/

Thank you for that suggestion, this works well!

--Carsten
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: sr-iov issues, reset_hw() failed with error -100

2016-02-24 Thread Eric Joyner 
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, 2016 at 8:09 AM Ultima  wrote:

>  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 are enabled and have hw.ix.num_queues="4" in /boot/loader.conf. Is
> there anything else that may need to be set? .(It did work on vmware)
>
>  For my second test, I moved the X540-AT1 to the board with the X540-AT2.
> It functioned with the same issues as the AT2 tho.
>
>
> I don't think I listed the motherboards in question yet so ill list them
> now.
>
> S1200BTLRM -
>
> http://ark.intel.com/products/69633/Intel-Server-Board-S1200BTLRM?q=S1200BTLRM
> MD80-TM0
> 
> - http://b2b.gigabyte.com/products/product-page.aspx?pid=5146#ov
>
> I'm not sure if it will be of any help tho.
>
> Ultima
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: sr-iov issues, reset_hw() failed with error -100

2016-02-24 Thread Ultima 
 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?
>
> 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, 2016 at 8:09 AM Ultima  wrote:
>
>>  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 are enabled and have hw.ix.num_queues="4" in /boot/loader.conf. Is
>> there anything else that may need to be set? .(It did work on vmware)
>>
>>  For my second test, I moved the X540-AT1 to the board with the X540-AT2.
>> It functioned with the same issues as the AT2 tho.
>>
>>
>> I don't think I listed the motherboards in question yet so ill list them
>> now.
>>
>> S1200BTLRM -
>>
>> http://ark.intel.com/products/69633/Intel-Server-Board-S1200BTLRM?q=S1200BTLRM
>> MD80-TM0
>> 
>> - http://b2b.gigabyte.com/products/product-page.aspx?pid=5146#ov
>>
>> I'm not sure if it will be of any help tho.
>>
>> Ultima
>> ___
>> freebsd-current@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org
>> "
>>
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: emulators/virtualbox-ose-kmod build error

2016-02-24 Thread O. Hartmann 
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
> -DVBOX_WITH_HARDENING -DVBOX_WITH_64_BITS_GUESTS -DRT_ARCH_AMD64 
> -march=native  -Werror
> -D_KERNEL -DKLD_MODULE -nostdinc  -Iinclude -I. -Ir0drv -I. -I/usr/src/sys 
> -fno-common
> -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer  -mcmodel=kernel 
> -mno-red-zone
> -mno-mmx -mno-sse -msoft-float  -fno-asynchronous-unwind-tables 
> -ffreestanding -fwrapv
> -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
> -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef 
> -Wno-pointer-sign
> -D__printf__=__freebsd_kprintf__  -Wmissing-include-dirs 
> -fdiagnostics-show-option
> -Wno-unknown-pragmas  -Wno-error-tautological-compare -Wno-error-empty-body
> -Wno-error-parentheses-equality -Wno-error-unused-function  
> -Wno-error-pointer-sign
> -Wno-error-shift-negative-value  -fvectorize -fslp-vectorize -fbloc ks
> -fcolor-diagnostics -mno-aes -mno-avx  -std=iso9899:1999
> -c 
> /media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c
> -o memobj-r0drv-freebsd.o --- assert-r0drv-freebsd.o --- In file included
> from 
> /media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/assert-r0drv-freebsd.c:34:
> In file included
> from 
> /media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/the-freebsd-kernel.h:39:
>  /usr/src/sys/sys/bus.h:659:10:
> fatal error: 'device_if.h' file not found #include "device_if.h" ^ ---
> alloc-r0drv-freebsd.o --- In file included
> from 
> /media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/alloc-r0drv-freebsd.c:34:
> In file included
> from 
> /media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/the-freebsd-kernel.h:39:
>  /usr/src/sys/sys/bus.h:659:10:
> fatal error: 'device_if.h' file not found #include "device_if.h" ^ ---
> assert-r0drv-freebsd.o --- 1 error generated. --- initterm-r0drv-freebsd.o 
> --- In file
> included
> from 
> /media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/initterm-r0drv-freebsd.c:34:
> In file included
> from 
> /media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/the-freebsd-kernel.h:39:
>  /usr/src/sys/sys/bus.h:659:10:
> fatal error: 'device_if.h' file not found #include "device_if.h" ^ ---
> assert-r0drv-freebsd.o --- *** [assert-r0drv-freebsd.o] Error code 1
> 
> make[3]: stopped
> in 
> /media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv
> --- initterm-r0drv-freebsd.o --- 1 error generated.
> --- alloc-r0drv-freebsd.o ---
> 1 error generated.
> --- initterm-r0drv-freebsd.o ---
> *** [initterm-r0drv-freebsd.o] Error code 1
> 
> make[3]: stopped
> in 
> /media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv
> --- memobj-r0drv-freebsd.o --- In file included
> from 
> /media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c:36:
> In file included
> from 
> /media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/the-freebsd-kernel.h:39:
>  /usr/src/sys/sys/bus.h:659:10:
> fatal error: 'device_if.h' file not found #include "device_if.h" ^
> --- alloc-r0drv-freebsd.o ---
> *** [alloc-r0drv-freebsd.o] Error code 1
> 
> make[3]: stopped
> in 
> /media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv
> --- memobj-r0drv-freebsd.o --- 1 error generated.
> *** [memobj-r0drv-freebsd.o] Error code 1
> 
> make[3]: stopped
> in 
> /media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv
> 4 errors
> 
> make[3]: stopped
> in 
> /media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv
> *** [all] Error code 2
> 
> make[2]: stopped
> in 
> /media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src
> 1 error
> 
> make[2]: stopped
> in 
> /media/da0s1/obj/usr/ports/emulators/virtualbox-ose-km