Re: Call for FreeBSD 2014Q1 (January-March) Status Reports

[Gabor Pali]

Dear FreeBSD Community,

Please note that the submission date for the 2014Q1 aka. January to
March 2014 Quarterly Status Reports is April 7th, 2014, that is today.
 Please consult my earlier message for the details:

2014-03-08 10:24 GMT+01:00 Gabor Pali :
> They do not have to be very long -- basically they may be about
> anything that lets people know what is going on around the FreeBSD
> Project.  Submission of reports is not restricted to committers:
> Anyone who is doing anything interesting and FreeBSD-related can (and
> therefore encouraged to) write one!
>
> The preferred and easiest submission method is to use the XML
> generator [1] with the result emailed as an attachment to us, that is,
> mont...@freebsd.org [2].  There is also an XML template [3] which can
> be filled out manually and attached if preferred.  For the expected
> content and style, please study our guidelines on how to write a good
> status report [4].  If you are still unsure what constitutes a good
> status report, check out the last issue [5].
>
> To enable compilation and publication of the quarterly report as soon
> as possible for the April 7th deadline, please be prompt with any
> report submissions you may have.
>
> We are looking forward to all of your 2014Q1 reports!
>
> Thanks,
> Gabor
>
>
> [1] http://www.freebsd.org/cgi/monthly.cgi
> [2] mailto:mont...@freebsd.org
> [3] http://www.freebsd.org/news/status/report-sample.xml
> [4] http://www.freebsd.org/news/status/howto.html
> [5] http://www.freebsd.org/news/status/report-2013-10-2013-12.html
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

[head tinderbox] failure on amd64/amd64

[FreeBSD Tinderbox]

TB --- 2014-04-07 09:20:29 - tinderbox 2.21 running on freebsd-current.sentex.ca
TB --- 2014-04-07 09:20:29 - FreeBSD freebsd-current.sentex.ca 9.2-STABLE 
FreeBSD 9.2-STABLE #0 r263721: Tue Mar 25 09:27:39 EDT 2014 
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC  amd64
TB --- 2014-04-07 09:20:29 - starting HEAD tinderbox run for amd64/amd64
TB --- 2014-04-07 09:20:29 - cleaning the object tree
TB --- 2014-04-07 09:20:29 - /usr/local/bin/svn stat --no-ignore /src
TB --- 2014-04-07 09:20:37 - At svn revision 264220
TB --- 2014-04-07 09:20:38 - building world
TB --- 2014-04-07 09:20:38 - CROSS_BUILD_TESTING=YES
TB --- 2014-04-07 09:20:38 - MAKEOBJDIRPREFIX=/obj
TB --- 2014-04-07 09:20:38 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2014-04-07 09:20:38 - SRCCONF=/dev/null
TB --- 2014-04-07 09:20:38 - TARGET=amd64
TB --- 2014-04-07 09:20:38 - TARGET_ARCH=amd64
TB --- 2014-04-07 09:20:38 - TZ=UTC
TB --- 2014-04-07 09:20:38 - __MAKE_CONF=/dev/null
TB --- 2014-04-07 09:20:38 - cd /src
TB --- 2014-04-07 09:20:38 - /usr/bin/make -B buildworld
>>> Building an up-to-date make(1)
>>> World build started on Mon Apr  7 09:20:46 UTC 2014
>>> Rebuilding the temporary build tree
>>> stage 1.1: legacy release compatibility shims
>>> stage 1.2: bootstrap tools
>>> stage 2.1: cleaning up the object tree
>>> stage 2.2: rebuilding the object tree
>>> stage 2.3: build tools
>>> stage 3: cross tools
>>> stage 4.1: building includes
>>> stage 4.2: building libraries
>>> stage 4.3: make dependencies
>>> stage 4.4: building everything
[...]
file_lookup(const char *path, const char *name, int namelen, char **extlist)
  ^
3 warnings generated.
cc  -O2 -pipe   -fPIC -I. -I/src/sys/boot/amd64/efi/../../efi/include 
-I/src/sys/boot/amd64/efi/../../efi/include/amd64 
-I/src/sys/boot/amd64/efi/../../../contrib/dev/acpica/include 
-I/src/sys/boot/amd64/efi/../../.. -DBOOT_FORTH 
-I/src/sys/boot/amd64/efi/../../ficl -I/src/sys/boot/amd64/efi/../../ficl/amd64 
-DLOADER_DISK_SUPPORT -DLOADER_GPT_SUPPORT -DLOADER_MBR_SUPPORT 
-I/src/sys/boot/amd64/efi/../../common -I/src/sys/boot/amd64/efi/../../common 
-ffreestanding -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float 
-std=gnu99 -Qunused-arguments   -c /src/sys/boot/amd64/efi/../../common/panic.c
cc  -O2 -pipe   -fPIC -I. -I/src/sys/boot/amd64/efi/../../efi/include 
-I/src/sys/boot/amd64/efi/../../efi/include/amd64 
-I/src/sys/boot/amd64/efi/../../../contrib/dev/acpica/include 
-I/src/sys/boot/amd64/efi/../../.. -DBOOT_FORTH 
-I/src/sys/boot/amd64/efi/../../ficl -I/src/sys/boot/amd64/efi/../../ficl/amd64 
-DLOADER_DISK_SUPPORT -DLOADER_GPT_SUPPORT -DLOADER_MBR_SUPPORT 
-I/src/sys/boot/amd64/efi/../../common -I/src/sys/boot/amd64/efi/../../common 
-ffreestanding -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float 
-std=gnu99 -Qunused-arguments   -c 
/src/sys/boot/amd64/efi/../../common/load_elf32.c
cc  -O2 -pipe   -fPIC -I. -I/src/sys/boot/amd64/efi/../../efi/include 
-I/src/sys/boot/amd64/efi/../../efi/include/amd64 
-I/src/sys/boot/amd64/efi/../../../contrib/dev/acpica/include 
-I/src/sys/boot/amd64/efi/../../.. -DBOOT_FORTH 
-I/src/sys/boot/amd64/efi/../../ficl -I/src/sys/boot/amd64/efi/../../ficl/amd64 
-DLOADER_DISK_SUPPORT -DLOADER_GPT_SUPPORT -DLOADER_MBR_SUPPORT 
-I/src/sys/boot/amd64/efi/../../common -I/src/sys/boot/amd64/efi/../../common 
-ffreestanding -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float 
-std=gnu99 -Qunused-arguments   -c 
/src/sys/boot/amd64/efi/../../common/load_elf32_obj.c
cc  -O2 -pipe   -fPIC -I. -I/src/sys/boot/amd64/efi/../../efi/include 
-I/src/sys/boot/amd64/efi/../../efi/include/amd64 
-I/src/sys/boot/amd64/efi/../../../contrib/dev/acpica/include 
-I/src/sys/boot/amd64/efi/../../.. -DBOOT_FORTH 
-I/src/sys/boot/amd64/efi/../../ficl -I/src/sys/boot/amd64/efi/../../ficl/amd64 
-DLOADER_DISK_SUPPORT -DLOADER_GPT_SUPPORT -DLOADER_MBR_SUPPORT 
-I/src/sys/boot/amd64/efi/../../common -I/src/sys/boot/amd64/efi/../../common 
-ffreestanding -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float 
-std=gnu99 -Qunused-arguments   -c 
/src/sys/boot/amd64/efi/../../common/reloc_elf32.c
cc  -O2 -pipe   -fPIC -I. -I/src/sys/boot/amd64/efi/../../efi/include 
-I/src/sys/boot/amd64/efi/../../efi/include/amd64 
-I/src/sys/boot/amd64/efi/../../../contrib/dev/acpica/include 
-I/src/sys/boot/amd64/efi/../../.. -DBOOT_FORTH 
-I/src/sys/boot/amd64/efi/../../ficl -I/src/sys/boot/amd64/efi/../../ficl/amd64 
-DLOADER_DISK_SUPPORT -DLOADER_GPT_SUPPORT -DLOADER_MBR_SUPPORT 
-I/src/sys/boot/amd64/efi/../../common -I/src/sys/boot/amd64/efi/../../common 
-ffreestanding -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float 
-std=gnu99 -Qunused-arguments   -c 
/src/sys/boot/amd64/efi/../../common/load_elf64.c
cc  -O2 -pipe   -fPIC -I. -I/src/sys/boot/amd64/efi/../../efi/include 
-I/src/sys/boot/amd64/efi/../../efi/include/amd64 
-I/src/sys/boot/amd64/efi/../../../contrib/dev/acpica/include 
-

Regarding Netmap and Last Updates

[Fred Pedrisa]

Hi, guys.

 

I've saw that the 'netmap pipes' were introduced, in order to understand the
new changes, I wanted to know if the latest bridge.c (zero copy) method, is
already an usage example of the netmap pipes ?

 

Sincerely,

 

Fred

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

Regarding Netmap and Last Updates

[Fred Pedrisa]

Hi, guys.

 

I've saw that the 'netmap pipes' were introduced, in order to understand the
new changes, I wanted to know if the latest bridge.c (zero copy) method, is
already an usage example of the netmap pipes ?

 

Sincerely,

 

Fred

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

Regarding Netmap and Last Updates

[Fred Pedrisa]

Hi, guys.

 

I've saw that the 'netmap pipes' were introduced, in order to understand the
new changes, I wanted to know if the latest bridge.c (zero copy) method, is
already an usage example of the netmap pipes ?

 

Sincerely,

 

Fred

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

Prefetch()

[Fred Pedrisa]

Hi, guys.

 

Does anyone knows what is the method : prefetch() used for ?

 

Sincerely,

 

Fred

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

Re: Regarding Netmap and Last Updates

[Adrian Chadd]

yup. it works fine. Just run it like:

./bridge -i netmap:ix0 -i netmap:ix1

or something.


-a


On 7 April 2014 06:22, Fred Pedrisa  wrote:
> Hi, guys.
>
>
>
> I've saw that the 'netmap pipes' were introduced, in order to understand the
> new changes, I wanted to know if the latest bridge.c (zero copy) method, is
> already an usage example of the netmap pipes ?
>
>
>
> Sincerely,
>
>
>
> Fred
>
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: panic: LK_RETRY set with incompatible flags (0x200400) or an error occured (11)

[Konstantin Belousov]

On Tue, Feb 18, 2014 at 03:43:28PM +0200, Andriy Gapon wrote:
> on 18/02/2014 15:39 Jeremie Le Hen said the following:
> > On Tue, Feb 18, 2014 at 03:31:53PM +0200, Andriy Gapon wrote:
> >>
> >> So, VV_ROOT is indeed set in v_vflag.
> >> Thank you.
> > 
> > So there's no need for me to reboot with kib's patch, right?
> 
> You better ask kib.  I do not see any misbehavior in ZFS code so far.
> 
Returning to this old thread.

I need to see the v_vflag of the nullfs vnode, in addition to the zfs
vnode' v_vflag.  I suspect that nullfs flag is somehow lost, and this
is what my patch tried to restore.  But please show me the nullfs
vnode dump before.


pgpHWKxVpZ5Ey.pgp
Description: PGP signature

RES: Regarding Netmap and Last Updates

[Fred Pedrisa]

Hi,

I know how to use, but this wasn't the question !

What I wanted to know is if this example, currently implement the new netmap
pipes or not.

-Mensagem original-
De: owner-freebsd-curr...@freebsd.org
[mailto:owner-freebsd-curr...@freebsd.org] Em nome de Adrian Chadd
Enviada em: segunda-feira, 7 de abril de 2014 14:47
Para: Fred Pedrisa
Cc: freebsd-current
Assunto: Re: Regarding Netmap and Last Updates

yup. it works fine. Just run it like:

./bridge -i netmap:ix0 -i netmap:ix1

or something.


-a


On 7 April 2014 06:22, Fred Pedrisa  wrote:
> Hi, guys.
>
>
>
> I've saw that the 'netmap pipes' were introduced, in order to 
> understand the new changes, I wanted to know if the latest bridge.c 
> (zero copy) method, is already an usage example of the netmap pipes ?
>
>
>
> Sincerely,
>
>
>
> Fred
>
> ___
> freebsd-current@freebsd.org mailing list 
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

Re: Regarding Netmap and Last Updates

[Adrian Chadd]

It's using the zerocopy buffer flipping. I don't know what you mean
about the "new pipes". it's just using the netmap user API that's
available.


-a


On 7 April 2014 12:20, Fred Pedrisa  wrote:
> Hi,
>
> I know how to use, but this wasn't the question !
>
> What I wanted to know is if this example, currently implement the new netmap
> pipes or not.
>
> -Mensagem original-
> De: owner-freebsd-curr...@freebsd.org
> [mailto:owner-freebsd-curr...@freebsd.org] Em nome de Adrian Chadd
> Enviada em: segunda-feira, 7 de abril de 2014 14:47
> Para: Fred Pedrisa
> Cc: freebsd-current
> Assunto: Re: Regarding Netmap and Last Updates
>
> yup. it works fine. Just run it like:
>
> ./bridge -i netmap:ix0 -i netmap:ix1
>
> or something.
>
>
> -a
>
>
> On 7 April 2014 06:22, Fred Pedrisa  wrote:
>> Hi, guys.
>>
>>
>>
>> I've saw that the 'netmap pipes' were introduced, in order to
>> understand the new changes, I wanted to know if the latest bridge.c
>> (zero copy) method, is already an usage example of the netmap pipes ?
>>
>>
>>
>> Sincerely,
>>
>>
>>
>> Fred
>>
>> ___
>> freebsd-current@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

RES: Regarding Netmap and Last Updates

[Fred Pedrisa]

Hi,

I am speaking about this :

"netmap / VALE is a framework for high speed packet I/O. Implemented as a
kernel module for FreeBSD and Linux, it supports access to network cards
(NICs), host stack, virtual ports (the "VALE" switch), and "netmap pipes".
netmap can easily do line rate on 10G NICs (14.88 Mpps), moves over 20 Mpps
on VALE ports, and over 100 Mpps on netmap pipes."

-Mensagem original-
De: owner-freebsd-curr...@freebsd.org
[mailto:owner-freebsd-curr...@freebsd.org] Em nome de Adrian Chadd
Enviada em: segunda-feira, 7 de abril de 2014 16:22
Para: Fred Pedrisa
Cc: freebsd-current
Assunto: Re: Regarding Netmap and Last Updates

It's using the zerocopy buffer flipping. I don't know what you mean about
the "new pipes". it's just using the netmap user API that's available.


-a


On 7 April 2014 12:20, Fred Pedrisa  wrote:
> Hi,
>
> I know how to use, but this wasn't the question !
>
> What I wanted to know is if this example, currently implement the new 
> netmap pipes or not.
>
> -Mensagem original-
> De: owner-freebsd-curr...@freebsd.org
> [mailto:owner-freebsd-curr...@freebsd.org] Em nome de Adrian Chadd 
> Enviada em: segunda-feira, 7 de abril de 2014 14:47
> Para: Fred Pedrisa
> Cc: freebsd-current
> Assunto: Re: Regarding Netmap and Last Updates
>
> yup. it works fine. Just run it like:
>
> ./bridge -i netmap:ix0 -i netmap:ix1
>
> or something.
>
>
> -a
>
>
> On 7 April 2014 06:22, Fred Pedrisa  wrote:
>> Hi, guys.
>>
>>
>>
>> I've saw that the 'netmap pipes' were introduced, in order to 
>> understand the new changes, I wanted to know if the latest bridge.c 
>> (zero copy) method, is already an usage example of the netmap pipes ?
>>
>>
>>
>> Sincerely,
>>
>>
>>
>> Fred
>>
>> ___
>> freebsd-current@freebsd.org mailing list 
>> http://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to
"freebsd-current-unsubscr...@freebsd.org"
> ___
> freebsd-current@freebsd.org mailing list 
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

Re: Regarding Netmap and Last Updates

[Adrian Chadd]

Yup. It's all that.

On 7 April 2014 13:05, Fred Pedrisa  wrote:
> Hi,
>
> I am speaking about this :
>
> "netmap / VALE is a framework for high speed packet I/O. Implemented as a
> kernel module for FreeBSD and Linux, it supports access to network cards
> (NICs), host stack, virtual ports (the "VALE" switch), and "netmap pipes".
> netmap can easily do line rate on 10G NICs (14.88 Mpps), moves over 20 Mpps
> on VALE ports, and over 100 Mpps on netmap pipes."
>
> -Mensagem original-
> De: owner-freebsd-curr...@freebsd.org
> [mailto:owner-freebsd-curr...@freebsd.org] Em nome de Adrian Chadd
> Enviada em: segunda-feira, 7 de abril de 2014 16:22
> Para: Fred Pedrisa
> Cc: freebsd-current
> Assunto: Re: Regarding Netmap and Last Updates
>
> It's using the zerocopy buffer flipping. I don't know what you mean about
> the "new pipes". it's just using the netmap user API that's available.
>
>
> -a
>
>
> On 7 April 2014 12:20, Fred Pedrisa  wrote:
>> Hi,
>>
>> I know how to use, but this wasn't the question !
>>
>> What I wanted to know is if this example, currently implement the new
>> netmap pipes or not.
>>
>> -Mensagem original-
>> De: owner-freebsd-curr...@freebsd.org
>> [mailto:owner-freebsd-curr...@freebsd.org] Em nome de Adrian Chadd
>> Enviada em: segunda-feira, 7 de abril de 2014 14:47
>> Para: Fred Pedrisa
>> Cc: freebsd-current
>> Assunto: Re: Regarding Netmap and Last Updates
>>
>> yup. it works fine. Just run it like:
>>
>> ./bridge -i netmap:ix0 -i netmap:ix1
>>
>> or something.
>>
>>
>> -a
>>
>>
>> On 7 April 2014 06:22, Fred Pedrisa  wrote:
>>> Hi, guys.
>>>
>>>
>>>
>>> I've saw that the 'netmap pipes' were introduced, in order to
>>> understand the new changes, I wanted to know if the latest bridge.c
>>> (zero copy) method, is already an usage example of the netmap pipes ?
>>>
>>>
>>>
>>> Sincerely,
>>>
>>>
>>>
>>> Fred
>>>
>>> ___
>>> freebsd-current@freebsd.org mailing list
>>> http://lists.freebsd.org/mailman/listinfo/freebsd-current
>>> To unsubscribe, send any mail to
> "freebsd-current-unsubscr...@freebsd.org"
>> ___
>> freebsd-current@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>>
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Jenkins build is back to normal : FreeBSD_HEAD #423

[jenkins-admin]

See 

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

Re: another Make (maybe) problem

[Warner Losh]

What happens if you say ‘DEBUG_FLAGS+= -gdwarf-2’ instead of a naked -g?

Warner

On Apr 2, 2014, at 9:47 PM, Robert Huff  wrote:

> Warner:
> 
> >  This will happen with fmake. I?ve put some safety belts in place in
> >  another fix to keep this from tripping people up (and plan on using >  a 
> > similar technique to keep people from hitting the aicasm bug on
> >  such systems).
> 
>   As long as make-related issues are on the table ...
> 
>   I have a system, running
> 
> FreeBSD 11.0-CURRENT #0 r263263: Mon Mar 17 15:09:18 EDT 2014 amd64
> 
>   where "make buildworld" fails.  The immediate problem can be seen at:
> 
> http://users.rcn.com/roberthuff/bw_tail
> 
>   the full log at
> 
> http://users.rcn.com/roberthuff/bwl.bz2
> 
>   "make.conf" is appended.  There is no "src.conf".
> 
>   I never seen anything like this before; nothing like has come across 
> current@ (recently); and nothing in src/UPDATING appears relevant.
>   Help, please?
> 
> 
>   Robert Huff
> 
> ◙♪
>   make.conf
> 
> BDBCFLAGS+=   -O -pipe
> DEBUG_FLAGS+= -g
> STRIP=
> SYMVER_ENABLED=   yes
> X_WINDOW_SYSTEM=  xorg
> HAVE_MOTIF=   yes
> 
> #FC="gfortran42"
> 
> KERNCONF=JERUSALEM
> 
> # To avoid building various parts of the base system:
> # (copied from /usr/share/examples/etc/make.conf
> 
> NO_BIND_ETC=   true# Do not install files to /etc/namedb
> NO_BLUETOOTH=  true# do not build Bluetooth related stuff
> NO_PROFILE= true# Avoid compiling profiled libraries
> 
> # to get automatic SASL in sendmail
> 
> SENDMAIL_CFLAGS+= -I/usr/local/include/ -DSASL=2
> SENDMAIL_LDFLAGS+=-L/usr/local/lib
> SENDMAIL_LDADD+=  -lsasl2
> 
> #
> # to make CUPS magically keep working
> # See: http://www.csua.berkeley.edu/~ranga/notes/freebsd_cups.html
> #
> 
> CUPS_OVERWRITE_BASE=  yes
> NO_LPR=   true
> 
> # added per /usr/ports/UPDATING entry 20090401
> 
> OVERRIDE_LINUX_BASE_PORT=f10
> OVERRIDE_LINUX_NONBASE_PORTS=f10
> 
> #
> 
> WITH_MOZILLA= libxul
> WITH_GECKO=   libxul
> 
> #
> # added 2007/03/04 per advice of 
> # in re science/gramps
> #
> 
> WITH_BERKELEYDB=db6
> WITH_BDB_VER=6
> WANT_OPENLDAP_VER=24
> WANT_OPENLDAP_SASL=true
> 
> #
> #  as required by ports/UPDATING of 20121012
> #
> 
> SAMBA_ENABLE=YES
> 
> #
> # PORTS: use clang unless gcc is explicitly required
> #
> 
> #
> # default to using clang for all port builds, with the following
> # exceptions
> 
> .if !empty(.CURDIR:M/usr/ports/graphics/libcdr) && 
> exists(/usr/local/bin/gcc47)
> CC=gcc47
> CXX=g++47
> CPP=cpp47
> .endif
> 
> 
> .if ${.CURDIR:M*/usr/ports/*}
> .if !defined(USE_GCC)
> .if !defined(CC) || ${CC} == "cc"
> CC=clang
> .endif
> .if !defined(CXX) || ${CXX} == "c++"
> CXX=clang++
> .endif
> .if !defined(CPP) || ${CPP} == "cpp"
> CPP=clang-cpp
> .endif
> .endif
> .endif
> 
> 
> WITH_NEW_XORG="yes"
> WITH_GALLIUM="yes"
> 
> WITH_BSD_SORT=
> 
> 
> WITH_PKGNG=yes
> 
> 
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

Cycle Count

[Fred Pedrisa]

Hi, guys.

 

How can we get a precise cycle count since the computer has started AND the
estimated number of cycles per second for the current core ?

 

Sincerely,

 

Fred Pedrisa

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

[head tinderbox] failure on amd64/amd64

[FreeBSD Tinderbox]

TB --- 2014-04-07 21:20:24 - tinderbox 2.21 running on freebsd-current.sentex.ca
TB --- 2014-04-07 21:20:24 - FreeBSD freebsd-current.sentex.ca 9.2-STABLE 
FreeBSD 9.2-STABLE #0 r263721: Tue Mar 25 09:27:39 EDT 2014 
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC  amd64
TB --- 2014-04-07 21:20:24 - starting HEAD tinderbox run for amd64/amd64
TB --- 2014-04-07 21:20:24 - cleaning the object tree
TB --- 2014-04-07 21:21:36 - /usr/local/bin/svn stat --no-ignore /src
TB --- 2014-04-07 21:21:40 - At svn revision 264240
TB --- 2014-04-07 21:21:41 - building world
TB --- 2014-04-07 21:21:41 - CROSS_BUILD_TESTING=YES
TB --- 2014-04-07 21:21:41 - MAKEOBJDIRPREFIX=/obj
TB --- 2014-04-07 21:21:41 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2014-04-07 21:21:41 - SRCCONF=/dev/null
TB --- 2014-04-07 21:21:41 - TARGET=amd64
TB --- 2014-04-07 21:21:41 - TARGET_ARCH=amd64
TB --- 2014-04-07 21:21:41 - TZ=UTC
TB --- 2014-04-07 21:21:41 - __MAKE_CONF=/dev/null
TB --- 2014-04-07 21:21:41 - cd /src
TB --- 2014-04-07 21:21:41 - /usr/bin/make -B buildworld
>>> Building an up-to-date make(1)
>>> World build started on Mon Apr  7 21:21:48 UTC 2014
>>> Rebuilding the temporary build tree
>>> stage 1.1: legacy release compatibility shims
>>> stage 1.2: bootstrap tools
>>> stage 2.1: cleaning up the object tree
>>> stage 2.2: rebuilding the object tree
>>> stage 2.3: build tools
>>> stage 3: cross tools
>>> stage 4.1: building includes
>>> stage 4.2: building libraries
>>> stage 4.3: make dependencies
>>> stage 4.4: building everything
[...]
cc   -O2 -pipe   -ffreestanding -mno-mmx -mno-3dnow -mno-sse -mno-sse2 
-mno-sse3 -msoft-float -std=gnu99 -Qunused-arguments-fPIC 
-I/src/sys/boot/ficl -I/src/sys/boot/ficl/amd64  -I/src/sys/boot/ficl/../common 
-c /src/sys/boot/ficl/words.c -o words.o
/src/sys/boot/ficl/words.c:2573:60: warning: implicit conversion from 'unsigned 
long' to 'int' changes value from 18446744073709551615 to -1 
[-Wconstant-conversion]
flag = ((pFW != NULL) && (pFW->flags & FW_ISOBJECT)) ? FICL_TRUE : 
FICL_FALSE;
 ~ ^
/src/sys/boot/ficl/ficl.h:252:21: note: expanded from macro 'FICL_TRUE'
#define FICL_TRUE  ((unsigned long)~(0L))
^~~~
1 warning generated.
cc   -O2 -pipe   -ffreestanding -mno-mmx -mno-3dnow -mno-sse -mno-sse2 
-mno-sse3 -msoft-float -std=gnu99 -Qunused-arguments-fPIC 
-I/src/sys/boot/ficl -I/src/sys/boot/ficl/amd64  -I/src/sys/boot/ficl/../common 
-c /src/sys/boot/ficl/amd64/sysdep.c -o sysdep.o
cc   -O2 -pipe   -ffreestanding -mno-mmx -mno-3dnow -mno-sse -mno-sse2 
-mno-sse3 -msoft-float -std=gnu99 -Qunused-arguments-fPIC 
-I/src/sys/boot/ficl -I/src/sys/boot/ficl/amd64  -I/src/sys/boot/ficl/../common 
-c softcore.c -o softcore.o
building static ficl library
ranlib libficl.a
===> sys/boot/amd64 (all)
===> sys/boot/amd64/efi (all)
Warning: Object directory not changed from original /src/sys/boot/amd64/efi
bmake[5]: .depend, 1171: ignoring stale .depend for 
/src/sys/boot/amd64/efi/../../ficl/libficl.a
bmake[5]: .depend, 1171: ignoring stale .depend for 
/src/sys/boot/amd64/efi/../../efi/libefi/libefi.a
cc  -O2 -pipe   -fPIC -I. -I/src/sys/boot/amd64/efi/../../efi/include 
-I/src/sys/boot/amd64/efi/../../efi/include/amd64 
-I/src/sys/boot/amd64/efi/../../../contrib/dev/acpica/include 
-I/src/sys/boot/amd64/efi/../../.. -DBOOT_FORTH 
-I/src/sys/boot/amd64/efi/../../ficl -I/src/sys/boot/amd64/efi/../../ficl/amd64 
-DLOADER_DISK_SUPPORT -DLOADER_GPT_SUPPORT -DLOADER_MBR_SUPPORT 
-I/src/sys/boot/amd64/efi/../../common -I/src/sys/boot/amd64/efi/../../common 
-ffreestanding -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float 
-std=gnu99 -Qunused-arguments   -Wl,-T/src/sys/boot/amd64/efi/ldscript.amd64 
-Wl,-Bsymbolic -shared -Wl,-znocombreloc -nostdlib -o loader.sym autoload.o 
bootinfo.o conf.o copy.o devicename.o elf64_freebsd.o framebuffer.o main.o 
reloc.o vers.o amd64_tramp.o start.o boot.o commands.o console.o devopen.o 
interp.o interp_backslash.o interp_parse.o ls.o misc.o module.o panic.o 
load_elf32.o load_elf32_obj.o reloc_elf32.o load_elf64.o load_elf64_obj.o 
reloc_elf64!
 .o disk.o part.o crc32.o bcache.o interp_forth.o 
/src/sys/boot/amd64/efi/../../ficl/libficl.a 
/src/sys/boot/amd64/efi/../../efi/libefi/libefi.a 
/obj/amd64.amd64/src/tmp/usr/lib/libstand.a
cc: error: no such file or directory: 
'/src/sys/boot/amd64/efi/../../ficl/libficl.a'
cc: error: no such file or directory: 
'/src/sys/boot/amd64/efi/../../efi/libefi/libefi.a'
*** Error code 1

Stop.
bmake[5]: stopped in /src/sys/boot/amd64/efi
*** Error code 1

Stop.
bmake[4]: stopped in /src/sys/boot/amd64
*** Error code 1

Stop.
bmake[3]: stopped in /src/sys/boot
*** Error code 1

Stop.
bmake[2]: stopped in /src/sys
*** Error code 1

Stop.
bmake[1]: stopped in /src
*** Error code 1

Stop.
bmake: stopped in /src
*** [buildworld] Error code 1

Stop in /src.
TB --- 2014-04-08 00:34:05 - WARNING: /

Re: Cycle Count

[Adrian Chadd]

Kinda? It's called the TSC.


-a


On 7 April 2014 16:51, Fred Pedrisa  wrote:
> Hi, guys.
>
>
>
> How can we get a precise cycle count since the computer has started AND the
> estimated number of cycles per second for the current core ?
>
>
>
> Sincerely,
>
>
>
> Fred Pedrisa
>
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"