Re: misc/180918: [patch] [modules] stable/9 buildworld is broken with MODULES_WITH_WORLD=yes

2013-10-07 Thread pluknet
Synopsis: [patch] [modules] stable/9 buildworld is broken with 
MODULES_WITH_WORLD=yes

State-Changed-From-To: open->closed
State-Changed-By: pluknet
State-Changed-When: Mon Oct 7 12:58:18 UTC 2013
State-Changed-Why: 
Committed to stable/9, thanks!

http://www.freebsd.org/cgi/query-pr.cgi?pr=180918
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


Re: misc/180918: commit references a PR

2013-10-07 Thread dfilter service
The following reply was made to PR misc/180918; it has been noted by GNATS.

From: dfil...@freebsd.org (dfilter service)
To: bug-follo...@freebsd.org
Cc:  
Subject: Re: misc/180918: commit references a PR
Date: Mon,  7 Oct 2013 12:57:36 + (UTC)

 Author: pluknet
 Date: Mon Oct  7 12:57:27 2013
 New Revision: 256109
 URL: http://svnweb.freebsd.org/changeset/base/256109
 
 Log:
   MFC r237560,254319 (by uqs): Fix 'make depend'.
   
   PR:  misc/180918
   Submitted by:Eugene Grosbein 
 
 Modified:
   stable/9/sys/modules/dtrace/sdt/Makefile
   stable/9/sys/modules/rdma/krping/Makefile
   stable/9/sys/modules/toecore/Makefile
 Directory Properties:
   stable/9/sys/   (props changed)
   stable/9/sys/modules/   (props changed)
 
 Modified: stable/9/sys/modules/dtrace/sdt/Makefile
 ==
 --- stable/9/sys/modules/dtrace/sdt/Makefile   Mon Oct  7 12:07:40 2013
(r256108)
 +++ stable/9/sys/modules/dtrace/sdt/Makefile   Mon Oct  7 12:57:27 2013
(r256109)
 @@ -4,7 +4,7 @@
  
  KMOD= sdt
  SRCS= sdt.c
 -SRCS+=vnode_if.h
 +SRCS+=vnode_if.h opt_kdtrace.h
  
  CFLAGS+=  -I${.CURDIR}/../../../cddl/compat/opensolaris \
-I${.CURDIR}/../../../cddl/contrib/opensolaris/uts/common \
 
 Modified: stable/9/sys/modules/rdma/krping/Makefile
 ==
 --- stable/9/sys/modules/rdma/krping/Makefile  Mon Oct  7 12:07:40 2013
(r256108)
 +++ stable/9/sys/modules/rdma/krping/Makefile  Mon Oct  7 12:57:27 2013
(r256109)
 @@ -5,8 +5,8 @@ RDMA= ${.CURDIR}/../../../contrib/rdma/k
  
  KMOD= krping
  SRCS= krping.c krping_dev.c getopt.c
 -SRCS+=  bus_if.h device_if.h opt_sched.h pci_if.h pcib_if.h
 -SRCS+=  vnode_if.h
 -CFLAGS+= -I${.CURDIR}/../../../ofed/include 
 +SRCS+=  bus_if.h device_if.h pci_if.h pcib_if.h vnode_if.h
 +SRCS+=  opt_sched.h opt_inet.h opt_inet6.h
 +CFLAGS+= -I${.CURDIR}/../../../ofed/include
  
  .include 
 
 Modified: stable/9/sys/modules/toecore/Makefile
 ==
 --- stable/9/sys/modules/toecore/Makefile  Mon Oct  7 12:07:40 2013
(r256108)
 +++ stable/9/sys/modules/toecore/Makefile  Mon Oct  7 12:57:27 2013
(r256109)
 @@ -4,6 +4,6 @@
  
  KMOD= toecore
  SRCS= toecore.c
 -SRCS+=opt_ofed.h
 +SRCS+=opt_ofed.h opt_inet.h opt_inet6.h
  
  .include 
 ___
 svn-src-...@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/svn-src-all
 To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
 
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


Re: gnu/154225: The rcsintro manpage should not be in section 1

2013-10-07 Thread pfg
Synopsis: The rcsintro manpage should not be in section 1

State-Changed-From-To: open->closed
State-Changed-By: pfg
State-Changed-When: Mon Oct 7 19:44:14 UTC 2013
State-Changed-Why: 
As of r256095 rcs is no more in the base system.

http://www.freebsd.org/cgi/query-pr.cgi?pr=154225
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


misc/182815: Core dump in net/mDNSResponder-379.38.1 using IPv6

2013-10-07 Thread Anton Fuller

>Number: 182815
>Category:   misc
>Synopsis:   Core dump in net/mDNSResponder-379.38.1 using IPv6
>Confidential:   no
>Severity:   non-critical
>Priority:   low
>Responsible:freebsd-bugs
>State:  open
>Quarter:
>Keywords:   
>Date-Required:
>Class:  sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Oct 07 23:20:00 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator: Anton Fuller
>Release:9.1-RELEASE
>Organization:
ICWU
>Environment:
FreeBSD 9.1-RELEASE amd64
>Description:
Shorty after starting on an IPv6-enabled system, both components of 
mDNSResponder crash. Both /usr/local/sbin/mdnsd and 
/usr/local/bin/mDNSResponderPosix crash and core dump.
>How-To-Repeat:
service start mDNSResponderPosix; service start mdnsd; observe logs to note 
core dumps and assertion errors. Offending file seems to be mDNSPosix/mDNSUNP.h
>Fix:
The patch from:
http://lists.freebsd.org/pipermail/freebsd-bugs/2013-September/053886.html
appears to resolve the issue.

>Release-Note:
>Audit-Trail:
>Unformatted:
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


misc/182817: print/pdftk always rebuilds in poudriere

2013-10-07 Thread Adam McDougall

>Number: 182817
>Category:   misc
>Synopsis:   print/pdftk always rebuilds in poudriere
>Confidential:   no
>Severity:   non-critical
>Priority:   low
>Responsible:freebsd-bugs
>State:  open
>Quarter:
>Keywords:   
>Date-Required:
>Class:  sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Oct 08 00:10:00 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator: Adam McDougall
>Release:9.2-PRERELEASE
>Organization:
>Environment:
FreeBSD build9 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #2 r255480: Wed Sep 11 
20:58:03 EDT 2013 root@build9:/usr/obj/usr/src/sys/BUILD9  amd64
>Description:
Sometime between 20130715 and 20130731, pdftk always gets rebuilt every time I 
run poudriere:

>> Deleting pdftk-1.45.txz: new dependency: lang/gcc

On 20130722, the first message was:

>> Deleting pdftk-1.45.txz: missing dependency: gcc-4.6.3

I think ever since 0722 (0731 and beyond), I get the "new dep" reason.  I 
suspect r323303 based on the timeframe?  It succeeds at building a package, but 
something about the makefile confuses poudriere.  It doesn't take long to build 
pdftk each time, but it shouldn't have to.
>How-To-Repeat:
run poudriere bulk twice in a row using a package list that includes pdftk, it 
will rebuild pdftk every time you run it
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


kern/182818: Slow writes to AHCI SATA on Soekris net6501 (Intel EG20T) in *BSD

2013-10-07 Thread Adam McDougall

>Number: 182818
>Category:   kern
>Synopsis:   Slow writes to AHCI SATA on Soekris net6501 (Intel EG20T) in 
>*BSD
>Confidential:   no
>Severity:   non-critical
>Priority:   low
>Responsible:freebsd-bugs
>State:  open
>Quarter:
>Keywords:   
>Date-Required:
>Class:  sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Oct 08 00:40:00 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator: Adam McDougall
>Release:10.0-ALPHA2
>Organization:
>Environment:
FreeBSD hoegaarden 10.0-ALPHA2 FreeBSD 10.0-ALPHA2 #0 r255793: Sun Sep 22 
17:05:25 EDT 2013 root@build9:/usr/obj/proto/src10/src/sys/AMD64-10  amd64
>Description:
I discovered these symptoms initially on 9.x, and this weekend upgraded to 10 
just to check for improvement.

The total AHCI SATA write speed on the net6501 (*BSD only?)
has a strange 20MB/sec limitation but reads can go over 100MB/sec.  If I
write to one disk I get 20MB/sec, but if I write to both SATA disks (such as 
mirroring) I get 10MB/sec each for a total of 20.  Writes are equally slow on a 
high end SSD.  Both someone running OpenBSD and I running FreeBSD reported the 
same symptoms to the soekris-tech mailing list and received no useful replies 
towards getting that problem solved.  I believe I duplicated the symptoms on 
NetBSD.  I tested the write speed briefly with Linux and it did not appear to 
have the 20MB/sec limitation (I wrote enough data that I was satisfied it could 
not be cached in ram).  I did confirm it was using MSI of some form with boot 
-v.  The disks I tested with are fine in normal computers.  I have three of 
these systems.  They are all acting as firewalls where write speed is not 
critical to operation, although one is considered a spare that I can experiment 
with.  They are not my property so I don't think I can mail one for personal 
inspection.
>How-To-Repeat:
Use something (dd?) to write to the raw devices or to a filesystem, use gstat 
-I 5 to confirm a total limitation of 20MB/sec disk IO whether it is to one 
disk or two (10 each).
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


kern/182819: pfctl interprets "# .... \" as multi-line comment

2013-10-07 Thread Adam McDougall

>Number: 182819
>Category:   kern
>Synopsis:   pfctl interprets "#  \" as multi-line comment
>Confidential:   no
>Severity:   non-critical
>Priority:   low
>Responsible:freebsd-bugs
>State:  open
>Quarter:
>Keywords:   
>Date-Required:
>Class:  sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Oct 08 01:10:00 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator: Adam McDougall
>Release:9.1-STABLE
>Organization:
>Environment:
FreeBSD hostname 9.1-STABLE FreeBSD 9.1-STABLE #0 r247358: Tue Feb 26 19:02:48 
EST 2013 root@build9:/usr/obj/proto/src9/src/sys/AMD64-9  amd64
>Description:
Twice I've been burned by pfctl ignoring a line in pf.conf because it was 
preceded by a comment that happened to end in a backslash:

# pass in on blah blah blah doesn't matter this is a comment \
pass in on blah blah doesn't matter because this is treated as part of the 
comment

I try to keep my firewall rules less than 80 chars in case I need to edit them 
on a dumb terminal.  Sometimes I end up duplicating a line to make changes to 
an alternate copy and comment out the original, but if the commented out line 
ends in a backslash, my intended replacement is ignored.  It becomes really 
confusing why my firewall rule is ignored yet no errors from pfctl -f.  
Eventually I figure it out.  But in my opinion, a system that treats lines 
starting with # as a comment ought to unconditionally treat them as a single 
line comment, and not "except if it ends in a \".  I don't know if this happens 
in any other pf implementation, or if it is intentional, but it is troublesome. 
 I think it would be better to parse and potentially accept lines following 
comments.  If they are faulty, pfctl will throw an error.  If they are valid, 
they should be honored.
>How-To-Repeat:
# pass in on blah blah blah doesn't matter this is a comment \
pass in on blah blah doesn't matter because this is treated as part of the 
comment

pfctl -f yourfilename, it will ignore the second line
>Fix:
When a # is encountered in pf.conf, unconditionally ignore the rest of the 
line.  Might be a problem with the order things are parsed?

>Release-Note:
>Audit-Trail:
>Unformatted:
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


Re: misc/182817: print/pdftk always rebuilds in poudriere

2013-10-07 Thread Adam McDougall
The following reply was made to PR misc/182817; it has been noted by GNATS.

From: Adam McDougall 
To: freebsd-gnats-sub...@freebsd.org
Cc:  
Subject: Re: misc/182817: print/pdftk always rebuilds in poudriere
Date: Mon, 07 Oct 2013 21:27:56 -0400

 On 10/07/13 20:09, Adam McDougall wrote:
 >> Number: 182817
 >> Category:   misc
 >> Synopsis:   print/pdftk always rebuilds in poudriere
 >>
 Oops, I intended this to be Category: ports
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


Re: ports/182815: Core dump in net/mDNSResponder-379.38.1 using IPv6

2013-10-07 Thread linimon
Synopsis: Core dump in net/mDNSResponder-379.38.1 using IPv6

Responsible-Changed-From-To: freebsd-bugs->freebsd-ports-bugs
Responsible-Changed-By: linimon
Responsible-Changed-When: Tue Oct 8 02:12:02 UTC 2013
Responsible-Changed-Why: 
ports PR.

http://www.freebsd.org/cgi/query-pr.cgi?pr=182815
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


Re: ports/182817: print/pdftk always rebuilds in poudriere

2013-10-07 Thread linimon
Synopsis: print/pdftk always rebuilds in poudriere

Responsible-Changed-From-To: freebsd-bugs->freebsd-ports-bugs
Responsible-Changed-By: linimon
Responsible-Changed-When: Tue Oct 8 02:12:27 UTC 2013
Responsible-Changed-Why: 
ports PR.

http://www.freebsd.org/cgi/query-pr.cgi?pr=182817
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


Re: kern/182610: [patch] arc4random(): replace RC4 with ChaCha20, follow OpenBSD

2013-10-07 Thread linimon
Old Synopsis: arc4random(): replace RC4 with ChaCha20, follow OpenBSD
New Synopsis: [patch] arc4random(): replace RC4 with ChaCha20, follow OpenBSD

Responsible-Changed-From-To: freebsd-bugs->secteam
Responsible-Changed-By: linimon
Responsible-Changed-When: Tue Oct 8 02:25:56 UTC 2013
Responsible-Changed-Why: 
Over to maintainer(s).

http://www.freebsd.org/cgi/query-pr.cgi?pr=182610
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


Re: kern/182536: [zfs] zfs deadlock

2013-10-07 Thread linimon
Old Synopsis: zfs deadlock
New Synopsis: [zfs] zfs deadlock

Responsible-Changed-From-To: freebsd-bugs->freebsd-fs
Responsible-Changed-By: linimon
Responsible-Changed-When: Tue Oct 8 02:34:26 UTC 2013
Responsible-Changed-Why: 
Over to maintainer(s).

http://www.freebsd.org/cgi/query-pr.cgi?pr=182536
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


Re: bin/182703: [patch] camcontrol(8) security command can't set master password

2013-10-07 Thread Mark Johnston
The following reply was made to PR bin/182703; it has been noted by GNATS.

From: Mark Johnston 
To: Scott Burns , bug-follo...@freebsd.org
Cc:  
Subject: Re: bin/182703: [patch] camcontrol(8) security command can't set
 master password
Date: Tue, 8 Oct 2013 00:05:00 -0400

 If I'm not mistaken, the -U option is optional and defaults to master in
 this case, so it should still be possible to do what you want by
 omitting -U entirely.
 
 -Mark
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


Re: bin/182703: [patch] camcontrol(8) security command can't set master password

2013-10-07 Thread markj
Synopsis: [patch] camcontrol(8) security command can't set master password

State-Changed-From-To: open->patched
State-Changed-By: markj
State-Changed-When: Tue Oct 8 04:18:26 UTC 2013
State-Changed-Why: 
Fixed in r256133.


Responsible-Changed-From-To: freebsd-bugs->markj
Responsible-Changed-By: markj
Responsible-Changed-When: Tue Oct 8 04:18:26 UTC 2013
Responsible-Changed-Why: 
Fixed in r256133.

http://www.freebsd.org/cgi/query-pr.cgi?pr=182703
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"