kern/179949: clang-3.2 cpp inserts extra white spaces to certain macro values

2013-06-25 Thread Jukka Ukkonen

>Number: 179949
>Category:   kern
>Synopsis:   clang-3.2 cpp inserts extra white spaces to certain macro 
>values
>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 Jun 25 08:10:00 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator: Jukka Ukkonen
>Release:9.1-STABLE
>Organization:
-
>Environment:
FreeBSD sleipnir 9.1-STABLE FreeBSD 9.1-STABLE #0 r252194M: Tue Jun 25 09:01:34 
EEST 2013 root@sleipnir:/usr/obj/usr/src/sys/Sleipnir  amd64
>Description:
The cpp version installed with clang-3.2 breaks all macros which include a dash
in the value by inserting an extra space character before the dash.

This problem was found when ipfw configuration files which had been working just
fine with the gcc version of cpp suddenly started experiencing hiccups.

Assume there is a macro specifying typical windows ports and
an ipfw rule using that macro ...

#define PORTS 137-139, 445
..
add 03020 deny log logamount 0 { tcp or udp } from any to any PORTS via em1

Clang-3.2 version of cpp does this...

add 03020 deny log logamount 0 { tcp or udp } from any to any 137 -139, 445 via 
em1
--+++^+

while the cleaner approach produces ...

add 03020 deny log logamount 0 { tcp or udp } from any to any 137-139, 445 via 
em1

Clang-3.3 version of cpp seems to behave better leaving the macro values
untouched/unmodified.


>How-To-Repeat:
See full description above.
>Fix:
Upgrade clang-3.2 and related tools to clang-3.3 and tools.


>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"


bin/179963: ntpd(8) tries to bind IFDISABLED IPv6 addresses

2013-06-25 Thread Sayetsky Anton

>Number: 179963
>Category:   bin
>Synopsis:   ntpd(8) tries to bind IFDISABLED IPv6 addresses
>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 Jun 25 12:20:02 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator: Sayetsky Anton
>Release:FreeBSD 9.1-RELEASE-p3 amd64
>Organization:
>Environment:
System: FreeBSD pxe.local 9.1-RELEASE-p2 FreeBSD 9.1-RELEASE-p2 #0: Sun Apr 28 
16:07:37 EEST 2013 root@pxe.local:/usr/obj/usr/src/sys/PXESRV  amd64 

>Description:
ntpd tries to bind IPv6 addresses even if the none of them configured. You can 
see the following errors (but sometimes ntpd starts without errors):

Jun 25 14:43:43 pxe kernel: Jun 25 14:43:43 pxe ntpd[701]: bind() fd 27, family 
AF_INET6, port 123, scope 1, addr fe80::250:56ff:febf:12, mcast=0 flags=0x11 
fails: Can't assign requested address
Jun 25 14:43:43 pxe kernel: Jun 25 14:43:43 pxe ntpd[701]: unable to create 
socket on em0 (7) for fe80::250:56ff:febf:12#123

But it still binds to IFDISABLED auto-address:
root@pxe:~# sockstat | grep ntpd
root ntpd   701   3  dgram  -> /var/run/logpriv
root ntpd   701   20 udp4   *:123 *:*
root ntpd   701   21 udp6   *:123 *:*
root ntpd   701   22 udp4   10.0.0.16:123 *:*
root ntpd   701   23 udp6   ::1:123   *:*
root ntpd   701   24 udp6   fe80:3::1:123 *:*
root ntpd   701   25 udp4   127.0.0.1:123 *:*
root ntpd   701   27 udp6   fe80:1::250:56ff:febf:12:123 *:*
root@pxe:~#

Configs below:

root@pxe:~# ifconfig 
em0: flags=8843 metric 0 mtu 1500
options=9b
ether 00:50:56:bf:00:12
inet 10.0.0.16 netmask 0xffe0 broadcast 10.0.0.31
inet6 fe80::250:56ff:febf:12%em0 prefixlen 64 scopeid 0x1 
nd6 options=29
media: Ethernet autoselect (1000baseT )
status: active
ipfw0: flags=8801 metric 0 mtu 65536
nd6 options=29
lo0: flags=8049 metric 0 mtu 16384
options=63
inet6 ::1 prefixlen 128 
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 
inet 127.0.0.1 netmask 0xff00 
nd6 options=21
root@pxe:~# cat /etc/ntp.conf 
#
# $FreeBSD: releng/9.1/etc/ntp.conf 239608 2012-08-23 04:57:56Z delphij $
#
# Default NTP servers for the FreeBSD operating system.
#
# Don't forget to enable ntpd in /etc/rc.conf with:
# ntpd_enable="YES"
#
# The driftfile is by default /var/db/ntpd.drift, check
# /etc/defaults/rc.conf on how to change the location.
#

server ntp.lds.net.ua iburst maxpoll 9
restrict ntp.lds.net.ua nomodify nopeer noquery notrap
server ntp1.lds.net.ua iburst maxpoll 9
restrict ntp1.lds.net.ua nomodify nopeer noquery notrap
server ntp2.lds.net.ua iburst maxpoll 9
restrict ntp2.lds.net.ua nomodify nopeer noquery notrap
restrict 127.0.0.1
restrict -6 ::1
restrict default ignore

server 127.127.1.0
restrict 127.127.1.0
fudge 127.127.1.0 stratum 10

restrict netmon.lds.local nomodify nopeer notrap
restrict netmon.lds.net.ua nomodify nopeer notrap
root@pxe:~# egrep "^ifconfig|^ntpd" /etc/rc.conf
ifconfig_em0="inet 10.0.0.16 netmask 255.255.255.224"
ntpd_enable="YES"
ntpd_config="/etc/ntp.conf"
ntpd_flags="-p /var/run/ntpd.pid -f /var/db/ntpd.drift"
ntpd_sync_on_start="YES"
root@pxe:~#

>How-To-Repeat:
Just enable ntpd on a machine without configured IPv6 addresses.

>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"


misc/179964: net/rwhoisd: do not overwrite configs

2013-06-25 Thread Mark Felder

>Number: 179964
>Category:   misc
>Synopsis:   net/rwhoisd: do not overwrite configs
>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 Jun 25 13:30:00 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator: Mark Felder
>Release:
>Organization:
>Environment:
>Description:
net/rwhoisd overwrites configs by default because a previous maintainer decided 
to remove the etc/rwhoisd/samples directory and put the configs directly in 
/etc/rwhoisd which unfortunately overwrites the live configs upon each 
reinstall.

This patch does the following:

- restores sample configs, copies the necessary samples to the right place 
during @exec if no live configs exist
- removes both the sample and live configs during @unexec if they are identical
- echo a message to notify user of need for net.inet6.ip6.v6only=0 if running 
with ipv6
- redundant mkdir/chown in post-install and @exec; use @exec but change to 
install -d instead of mkdir/chown
- rc script now passes rclint

https://redports.org/buildarchive/20130625130400-7240/


>How-To-Repeat:

>Fix:


Patch attached with submission follows:

Index: Makefile
===
--- Makefile(revision 321736)
+++ Makefile(working copy)
@@ -3,7 +3,7 @@
 
 PORTNAME=  rwhoisd
 PORTVERSION=   1.5.9.6
-PORTREVISION=  1
+PORTREVISION=  2
 CATEGORIES=net ipv6
 MASTER_SITES=  http://projects.arin.net/rwhois/ftp/ \
http://www.rwhois.net/ftp/ \
@@ -34,6 +34,10 @@
 PORTDOCS=  INSTALL.html TODO UPGRADE operations_guide.html \
operations_guide.txt rfc2167.txt security.html security.txt
 
+ETCFILES=  rwhoisd.allow rwhoisd.auth_area rwhoisd.conf rwhoisd.deny \
+   rwhoisd.dir rwhoisd.root rwhoisd.x.dir
+PLIST_SUB+=ETCFILES="${ETCFILES}"
+
 .include 
 
 .if empty(PORT_OPTIONS:MIPV6)
@@ -45,8 +49,6 @@
 .endif
 
 post-patch:
-   @${REINPLACE_CMD} -e 's,rwhoisd/samples,rwhoisd,' \
-   ${WRKSRC}/sample.data/Makefile.in
@${REINPLACE_CMD} -e 's,userid: rwhoisd,userid: nobody,' \
  -e 's,pid-file: rwhoisd.pid,pid-file: 
/var/run/rwhoisd/rwhoisd.pid,' \
${WRKSRC}/sample.data/rwhoisd.conf
@@ -54,8 +56,6 @@
${WRKSRC}/common/conf.h
 
 post-install:
-   @${MKDIR} /var/log/rwhoisd /var/run/rwhoisd
-   @${CHOWN} -R nobody /var/log/rwhoisd /var/run/rwhoisd
${INSTALL_MAN} ${WRKSRC}/doc/rwhois_indexer.8 ${PREFIX}/man/man8
${INSTALL_MAN} ${WRKSRC}/doc/rwhoisd.8 ${PREFIX}/man/man8
 .if ${PORT_OPTIONS:MDOCS}
Index: files/rwhoisd.in
===
--- files/rwhoisd.in(revision 321736)
+++ files/rwhoisd.in(working copy)
@@ -1,5 +1,7 @@
 #!/bin/sh
-
+#
+# $FreeBSD$
+#
 # PROVIDE: rwhoisd
 # REQUIRE: LOGIN
 # KEYWORD: shutdown
@@ -15,18 +17,17 @@
 
 . /etc/rc.subr
 
-name="rwhoisd"
+name=rwhoisd
 rcvar=rwhoisd_enable
-
-command=%%PREFIX%%/sbin/${name}
-pidfile=${rwhoisd_pidfile}
-
 load_rc_config $name
 
-: ${rwhoisd_enable="NO"}
+: ${rwhoisd_enable:=NO}
 : ${rwhoisd_config="%%PREFIX%%/etc/rwhoisd/rwhoisd.conf"}
 : ${rwhoisd_pidfile="/var/run/${name}/${name}.pid"}
 
+command=%%PREFIX%%/sbin/${name}
+pidfile=${rwhoisd_pidfile}
+
 command_args="-d -c $rwhoisd_config"
 
 run_rc_command "$1"
Index: pkg-plist
===
--- pkg-plist   (revision 321736)
+++ pkg-plist   (working copy)
@@ -2,66 +2,70 @@
 bin/rwhois_indexer
 bin/rwhois_repack
 sbin/rwhoisd
-etc/rwhoisd/a.com/attribute_defs/asn.tmpl
-etc/rwhoisd/a.com/attribute_defs/contact.tmpl
-etc/rwhoisd/a.com/attribute_defs/domain.tmpl
-etc/rwhoisd/a.com/attribute_defs/guardian.tmpl
-etc/rwhoisd/a.com/attribute_defs/host.tmpl
-etc/rwhoisd/a.com/attribute_defs/org.tmpl
-etc/rwhoisd/a.com/attribute_defs/referral.tmpl
-etc/rwhoisd/a.com/data/asn/asn.txt
-etc/rwhoisd/a.com/data/contact/contact.txt
-etc/rwhoisd/a.com/data/domain/domain.txt
-etc/rwhoisd/a.com/data/guardian/guardian.txt
-etc/rwhoisd/a.com/data/host/host.txt
-etc/rwhoisd/a.com/data/org/org.txt
-etc/rwhoisd/a.com/data/referral/referral.txt
-etc/rwhoisd/a.com/schema
-etc/rwhoisd/a.com/soa
-etc/rwhoisd/net-10.0.0.0-8/attribute_defs/contact.tmpl
-etc/rwhoisd/net-10.0.0.0-8/attribute_defs/guardian.tmpl
-etc/rwhoisd/net-10.0.0.0-8/attribute_defs/host.tmpl
-etc/rwhoisd/net-10.0.0.0-8/attribute_defs/network.tmpl
-etc/rwhoisd/net-10.0.0.0-8/attribute_defs/referral.tmpl
-etc/rwhoisd/net-10.0.0.0-8/data/network/network.txt
-etc/rwhoisd/net-10.0.0.0-8/data/referral/referral.txt
-etc/rwhoisd/net-10.0.0.0-8/schema
-etc/rwhoisd/net-10.0.0.0-8/soa
-etc/rwhoisd/net-fd00:1234::-32/attribute_defs/host.tmpl
-etc/rwhoisd/net-fd00:1234::-32/attribute_defs/referral.tmpl
-etc

Re: conf/178611: [patch] daily_status_security_inline broken in 450.status-security

2013-06-25 Thread jhb
Synopsis: [patch] daily_status_security_inline broken in 450.status-security

State-Changed-From-To: open->patched
State-Changed-By: jhb
State-Changed-When: Tue Jun 25 15:45:42 UTC 2013
State-Changed-Why: 
Variant committed to HEAD, take this for the MFC reminder.  Thanks!


Responsible-Changed-From-To: freebsd-bugs->jhb
Responsible-Changed-By: jhb
Responsible-Changed-When: Tue Jun 25 15:45:42 UTC 2013
Responsible-Changed-Why: 
Variant committed to HEAD, take this for the MFC reminder.  Thanks!

http://www.freebsd.org/cgi/query-pr.cgi?pr=178611
___
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/179964: net/rwhoisd: do not overwrite configs

2013-06-25 Thread remko
Synopsis: net/rwhoisd: do not overwrite configs

Responsible-Changed-From-To: freebsd-bugs->freebsd-ports-bugs
Responsible-Changed-By: remko
Responsible-Changed-When: Tue Jun 25 16:56:24 UTC 2013
Responsible-Changed-Why: 
reassign to ports team

http://www.freebsd.org/cgi/query-pr.cgi?pr=179964
___
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/179065: Add RDRAND/F16C support to misc/cpuid

2013-06-25 Thread eadler
Synopsis: Add RDRAND/F16C support to misc/cpuid

Responsible-Changed-From-To: eadler->freebsd-bugs
Responsible-Changed-By: eadler
Responsible-Changed-When: Tue Jun 25 19:39:12 UTC 2013
Responsible-Changed-Why: 
I have no time to deal with this.A


http://www.freebsd.org/cgi/query-pr.cgi?pr=179065
___
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/177319: [kernel] [patch] Add more x86 CPU feature flag definitions

2013-06-25 Thread eadler
Synopsis: [kernel] [patch] Add more x86 CPU feature flag definitions

Responsible-Changed-From-To: eadler->freebsd-bugs
Responsible-Changed-By: eadler
Responsible-Changed-When: Tue Jun 25 19:40:57 UTC 2013
Responsible-Changed-Why: 
 I don't have time to deal with this.


http://www.freebsd.org/cgi/query-pr.cgi?pr=177319
___
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/179975: igb(4) fails to do polling(4)

2013-06-25 Thread Antoine Beaupre

>Number: 179975
>Category:   kern
>Synopsis:   igb(4) fails to do polling(4)
>Confidential:   no
>Severity:   serious
>Priority:   medium
>Responsible:freebsd-bugs
>State:  open
>Quarter:
>Keywords:   
>Date-Required:
>Class:  sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Jun 25 19:50:00 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator: Antoine Beaupre
>Release:FreeBSD 9.1-RELEASE-p3 amd64
>Organization:
Koumbit.org
>Environment:
System: FreeBSD rtr1.koumbit.net 9.1-RELEASE-p3 FreeBSD 9.1-RELEASE-p3 #0 
r251605: Mon Jun 10 16:17:26 EDT 2013 
r...@rtr1.koumbit.net:/usr/obj/usr/src/sys/KOUMBIT1 amd64

>Description:

the igb(4) driver doesn't work properly in polling mode, despite advertising 
that capability.

This may be related to VLAN configuration here.

igb0: flags=8843 metric 0 mtu 1500

options=400bb

capabilities=505fb
ether 90:e2:ba:39:d3:7c
inet 199.58.81.2 netmask 0xffc0 broadcast 199.58.81.63
inet6 fe80::92e2:baff:fe39:d37c%igb0 prefixlen 64 scopeid 0x1
nd6 options=29
media: Ethernet autoselect (1000baseT )
status: active
supported media:
media autoselect
media 1000baseT
media 1000baseT mediaopt full-duplex
media 100baseTX mediaopt full-duplex
media 100baseTX
media 10baseT/UTP mediaopt full-duplex
media 10baseT/UTP

here's some bits from the dmesg:

igb0:  mem 
0xf7b0-0xf7b7,0xf7b8c000-0xf7b8 irq 16 at
device 0.0 on pci1
igb0: Using MSIX interrupts with 5 vectors
igb0: Ethernet address: 90:e2:ba:39:d3:7c
igb0: Bound queue 0 to cpu 0
igb0: Bound queue 1 to cpu 1
igb0: Bound queue 2 to cpu 2
igb0: Bound queue 3 to cpu 3
igb1:  mem 
0xf7a0-0xf7a7,0xf7b88000-0xf7b8bfff irq 17 at device 0.1 on pci1
igb1: Using MSIX interrupts with 5 vectors
igb1: Ethernet address: 90:e2:ba:39:d3:7d
igb1: Bound queue 0 to cpu 0
igb1: Bound queue 1 to cpu 1
igb1: Bound queue 2 to cpu 2
igb1: Bound queue 3 to cpu 3
igb2:  mem 
0xf798-0xf79f,0xf7b84000-0xf7b87fff irq 18 at device 0.2 on pci1
igb2: Using MSIX interrupts with 5 vectors
igb2: Ethernet address: 90:e2:ba:39:d3:7e
igb2: Bound queue 0 to cpu 0
igb2: Bound queue 1 to cpu 1
igb2: Bound queue 2 to cpu 2
igb2: Bound queue 3 to cpu 3
igb3:  mem 
0xf790-0xf797,0xf7b8-0xf7b83fff irq 19 at device 0.3 on pci1
igb3: Using MSIX interrupts with 5 vectors
igb3: Ethernet address: 90:e2:ba:39:d3:7f
igb3: Bound queue 0 to cpu 0
igb3: Bound queue 1 to cpu 1
igb3: Bound queue 2 to cpu 2
igb3: Bound queue 3 to cpu 3

Note that we cannot reproduce the problem with the following interface:

em0:  port 0xe000-0xe01f mem 
0xf7d0-0xf7d1,0xf7d2-0xf7d23fff ir
q 18 at device 0.0 on pci3
em0: Using MSIX interrupts with 3 vectors
em0: Ethernet address: 00:25:90:ae:dc:02

>How-To-Repeat:

Here's our kernel configuration:

include GENERIC
ident KOUMBIT0
device  pf
device  pflog
device  pfsync
options ALTQ
options ALTQ_CBQ
options ALTQ_RED
options ALTQ_RIO
options ALTQ_HFSC
options ALTQ_CDNR
options ALTQ_PRIQ
options   IPSEC#IP security
devicecrypto
options DEVICE_POLLING
device  carp

In our configuration, we are building a new router (rtr1 FreeBSD 9.1) to 
replace our old router (rtr0, FreeBSD 8.3).

Configure igb0 with an IP, enable polling and some VLANs:

ifconfig_igb0="inet 199.58.81.2 netmask 255.255.255.192 polling"
cloned_interfaces="vlan141 vlan60"
ifconfig_vlan141="inet 199.58.80.2 netmask 255.255.255.128 vlan 141 vlandev 
igb0"
ifconfig_vlan60="inet 199.58.82.2 netmask 255.255.255.192 vlan 60 vlandev igb0"
ifconfig_vlan60_alias0="inet 199.58.81.254 netmask 255.255.255.192"

Configure a switch with those VLANs. Make the VLANs 141 and 60 be tagged and 
share an untagged VLAN for the native interface.

Configure another router with a similar configuration.

Expected results:

 * all those IPs are pingable from the other router
 * the other router should also be pingable
 * adding the other router as a gateway should make it pingable

Actual results:

 * ICMP request packets go out of the interface, are received by the other 
router which responds
 * ICMP response packets are not picked up by the interface until POLLING is 
disabled

This may be related with http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/155030

>Fix:

No known fix. Workaround:

ifconfig igb0 -polling
ifconfig igb0 polling

It seems that cycling the polling configuration fixes the problem, at least 
temporarily.

We have yet to put this server in production and would really, really 
appreciate some help here. We are a small non-profit ISP, but we are skilled 
enough to test patches on the kernel tree, and would be ready to offer a bounty 
(100$?) to see this problem fixed quickly.

Our ETA for 

Re: kern/179975: igb(4) fails to do polling(4)

2013-06-25 Thread Antoine Beaupré
Correction: cycling polling(4) doesn't actually work. The interface
failed to route packets after a while.

I'm trying the patch from kern/155030.

A.

-- 
Ils versent un pauvre miel sur leurs mots pourris et te parlent de pénurie
Et sur ta faim, sur tes amis, ils aiguisent leur appétit
- Richard Desjardins, La maison est ouverte
___
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/179975: igb(4) fails to do polling(4)

2013-06-25 Thread Antoine Beaupré
The following reply was made to PR kern/179975; it has been noted by GNATS.

From: Antoine =?utf-8?Q?Beaupr=C3=A9?= 
To: freebsd-gnats-sub...@freebsd.org, freebsd-bugs@FreeBSD.org
Cc:  
Subject: Re: kern/179975: igb(4) fails to do polling(4)
Date: Tue, 25 Jun 2013 16:08:08 -0400

 Correction: cycling polling(4) doesn't actually work. The interface
 failed to route packets after a while.
 
 I'm trying the patch from kern/155030.
 
 A.
 
 --=20
 Ils versent un pauvre miel sur leurs mots pourris et te parlent de p=C3=A9n=
 urie
 Et sur ta faim, sur tes amis, ils aiguisent leur app=C3=A9tit
 - Richard Desjardins, La maison est ouverte
___
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/179975: igb(4) fails to do polling(4)

2013-06-25 Thread Mark Johnston
The following reply was made to PR kern/179975; it has been noted by GNATS.

From: Mark Johnston 
To: Antoine Beaupre 
Cc: bug-follo...@freebsd.org
Subject: Re: kern/179975: igb(4) fails to do polling(4)
Date: Tue, 25 Jun 2013 16:10:10 -0400

 On Tue, Jun 25, 2013 at 03:39:32PM -0400, Antoine Beaupre wrote:
 > 
 > >Number: 179975
 > >Category:   kern
 > >Synopsis:   igb(4) fails to do polling(4)
 > >Confidential:   no
 > >Severity:   serious
 > >Priority:   medium
 > >Responsible:freebsd-bugs
 > >State:  open
 > >Quarter:
 > >Keywords:   
 > >Date-Required:
 > >Class:  sw-bug
 > >Submitter-Id:   current-users
 > >Arrival-Date:   Tue Jun 25 19:50:00 UTC 2013
 > >Closed-Date:
 > >Last-Modified:
 > >Originator: Antoine Beaupre
 > >Release:FreeBSD 9.1-RELEASE-p3 amd64
 > >Organization:
 > Koumbit.org
 > >Environment:
 > System: FreeBSD rtr1.koumbit.net 9.1-RELEASE-p3 FreeBSD 9.1-RELEASE-p3 #0 
 > r251605: Mon Jun 10 16:17:26 EDT 2013 
 > r...@rtr1.koumbit.net:/usr/obj/usr/src/sys/KOUMBIT1 amd64
 > 
 > >Description:
 > 
 > the igb(4) driver doesn't work properly in polling mode, despite advertising 
 > that capability.
 >
 > [snip snip]
 > 
 > This may be related with 
 > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/155030
 > 
 > >Fix:
 > 
 > No known fix. Workaround:
 > 
 > ifconfig igb0 -polling
 > ifconfig igb0 polling
 > 
 > It seems that cycling the polling configuration fixes the problem, at least 
 > temporarily.
 > 
 > We have yet to put this server in production and would really, really 
 > appreciate some help here. We are a small non-profit ISP, but we are skilled 
 > enough to test patches on the kernel tree, and would be ready to offer a 
 > bounty (100$?) to see this problem fixed quickly.
 > 
 > Our ETA for production is july 9th.
 
 Hello,
 
 Prior to the change in the above-mentioned PR, igb's polling mode only
 worked with a single queue enabled. I submitted a patch to get it to
 work with multiple queues, and it was committed in r239109. It didn't
 make it into 9.1 though, so igb's polling mode with multiple queues is
 broken.
 
 You have two options. The first is to apply the above revision to your
 driver and recompile the kernel. I can help you with this if you need
 it. The second is to tell igb to only use one queue, using the following
 lines in /boot/loader.conf:
 
 hw.igb.num_queues=1
 
 You'll need to reboot to apply it. I don't think there's really much
 reason to have multiple queues enabled in polling mode, I just had a
 special use case.
 
 HTH,
 -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: ports/179065: Add RDRAND/F16C support to misc/cpuid

2013-06-25 Thread Oliver Pinter
mostly commited this change by rpaulo, see r249601

On 6/25/13, ead...@freebsd.org  wrote:
> Synopsis: Add RDRAND/F16C support to misc/cpuid
>
> Responsible-Changed-From-To: eadler->freebsd-bugs
> Responsible-Changed-By: eadler
> Responsible-Changed-When: Tue Jun 25 19:39:12 UTC 2013
> Responsible-Changed-Why:
> I have no time to deal with this.A
>
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=179065
> ___
> 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"
>
___
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/179975: igb(4) fails to do polling(4)

2013-06-25 Thread Antoine Beaupré
The following reply was made to PR kern/179975; it has been noted by GNATS.

From: Antoine =?utf-8?Q?Beaupr=C3=A9?= 
To: Mark Johnston 
Cc: bug-follo...@freebsd.org
Subject: Re: kern/179975: igb(4) fails to do polling(4)
Date: Tue, 25 Jun 2013 16:20:05 -0400

 --=-=-=
 Content-Transfer-Encoding: quoted-printable
 
 On 2013-06-25 16:10:10, Mark Johnston wrote:
 > Hello,
 >
 > Prior to the change in the above-mentioned PR, igb's polling mode only
 > worked with a single queue enabled. I submitted a patch to get it to
 > work with multiple queues, and it was committed in r239109. It didn't
 > make it into 9.1 though, so igb's polling mode with multiple queues is
 > broken.
 >
 > You have two options. The first is to apply the above revision to your
 > driver and recompile the kernel. I can help you with this if you need
 > it. The second is to tell igb to only use one queue, using the following
 > lines in /boot/loader.conf:
 >
 > hw.igb.num_queues=3D1
 >
 > You'll need to reboot to apply it. I don't think there's really much
 > reason to have multiple queues enabled in polling mode, I just had a
 > special use case.
 
 Hi!
 
 Thank you very much for the fast response!
 
 I have recompiled with the patch and things seem to be holding. I will
 keep the loader.conf hack in mind for now.
 
 Will this patch make it to 9.2 or 9.1-p4?
 
 Thanks!
 
 =2D-=20
 The individual has always had to struggle to keep from being overwhelmed
 by the tribe. If you try it, you will be lonely often, and sometimes
 frightened. But no price is too high to pay for the privilege of owning
 yourself.- Friedrich Nietzsche
 
 --=-=-=
 Content-Type: application/pgp-signature
 
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.12 (GNU/Linux)
 
 iQIcBAEBCAAGBQJRyft1AAoJEHkhUlJ7dZIeqkgP/1wap1S1kLlPHYP1SUxFgDXL
 gvPoeCZC3rdmPUWL6jWcR1G6G3oX5+SrYVMOotlZ7rsq7zbCxWwPvQFDEe9Tja2n
 1azv4TiqrM1lpUHR88bptch91mi1QwznSNfsIazF3bfWsuGCMSCmVrB3XXxweibN
 Yjvpoz7lVY1CpDhfdD5FC6dXb8ibSXv/VpNrwB83BLIl/wnetizwCuLZAOs8hG/6
 UF0nuOaLRTvqSKy0GrezUCchQDx9cy67TlpOOdi1L3187C9MXx2/hrkHD4NjC0T7
 wcl4OHtGjA7Q+mu/owZbrdzHVR9LRUXwQuQpRLWb5aEBCt/jXeSLwZ+K0kj5+3F8
 cVmtYNwnuKpa9k28rLQ7LU+9x2McIN5in53IfOH9vfPcWHKzP+hZxlANL9qugO+k
 ubQ00m38R61a4tC6HHzkJjWtMnBL8uXDJqsFt30owOE0oNgZKOieZ1AFdseR2IxY
 /0hxznFx+hk9ePbKysPFBQLIrFwzQR5R95gIcSNmQyRcrJ+NxdOPl2m3LLoxQ+n9
 jxkpOZAVm6UPymmErMHp/UWtVk5URRi4E4m8EpeGTetDqAFZReKclAUY4e+KhVuc
 BFzgU3n+InJXo3psDZNwhJ74V+ulQv4Nw2UewrtmHEhm2OJRgoU76rVKERbsAkdA
 oGGSDFVrBjAI9XbwXno2
 =2M7g
 -END PGP SIGNATURE-
 --=-=-=--
___
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/179975: igb(4) fails to do polling(4)

2013-06-25 Thread Mark Johnston
The following reply was made to PR kern/179975; it has been noted by GNATS.

From: Mark Johnston 
To: Antoine =?iso-8859-1?Q?Beaupr=E9?= 
Cc: bug-follo...@freebsd.org
Subject: Re: kern/179975: igb(4) fails to do polling(4)
Date: Tue, 25 Jun 2013 16:32:00 -0400

 On Tue, Jun 25, 2013 at 04:20:05PM -0400, Antoine Beaupré wrote:
 > On 2013-06-25 16:10:10, Mark Johnston wrote:
 > > Hello,
 > >
 > > Prior to the change in the above-mentioned PR, igb's polling mode only
 > > worked with a single queue enabled. I submitted a patch to get it to
 > > work with multiple queues, and it was committed in r239109. It didn't
 > > make it into 9.1 though, so igb's polling mode with multiple queues is
 > > broken.
 > >
 > > You have two options. The first is to apply the above revision to your
 > > driver and recompile the kernel. I can help you with this if you need
 > > it. The second is to tell igb to only use one queue, using the following
 > > lines in /boot/loader.conf:
 > >
 > > hw.igb.num_queues=1
 > >
 > > You'll need to reboot to apply it. I don't think there's really much
 > > reason to have multiple queues enabled in polling mode, I just had a
 > > special use case.
 > 
 > Hi!
 > 
 > Thank you very much for the fast response!
 > 
 > I have recompiled with the patch and things seem to be holding. I will
 > keep the loader.conf hack in mind for now.
 > 
 > Will this patch make it to 9.2 or 9.1-p4?
 
 It has already been merged to the stable/9 branch, so it'll be in 9.2.
 Existing releases only receive fixes for security-related issues, so
 this change will never become part of 9.1.
___
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/179975: [igb] igb(4) fails to do polling(4)

2013-06-25 Thread linimon
Old Synopsis: igb(4) fails to do polling(4)
New Synopsis: [igb] igb(4) fails to do polling(4)

State-Changed-From-To: open->patched
State-Changed-By: linimon
State-Changed-When: Wed Jun 26 06:32:48 UTC 2013
State-Changed-Why: 
apparently is already in 9-STABLE.


Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Wed Jun 26 06:32:48 UTC 2013
Responsible-Changed-Why: 

http://www.freebsd.org/cgi/query-pr.cgi?pr=179975
___
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"