Re: failure to build current

2014-05-12 Thread Riccardo Mottola
Hi, nobody has a clue on this? I tried to build twice... getting the same error... Riccardo On 05/11/14 08:46, Riccardo Mottola wrote: Hi, while building distribution I get: includes === external/mit/xorg/include/xf86vidmodeproto includes === external/mit/xorg/include/renderproto includes

Re: Strange boot problems on amd64-current (6.99.40)

2014-05-12 Thread Robert Elz
Date:Sun, 11 May 2014 22:53:48 -0400 From:chris...@zoulas.com (Christos Zoulas) Message-ID: 20140512025348.ab23b17f...@rebar.astron.com | This should work... But it is sub-optimal. It returns the state to as it was before the 1.306 commit. That is, previously,

Re: failure to build current

2014-05-12 Thread Thomas Klausner
On Mon, May 12, 2014 at 09:10:07AM +0200, Riccardo Mottola wrote: nobody has a clue on this? I tried to build twice... getting the same error... Forgotten -Pd when updating your source tree? Thomas

Re: Strange boot problems on amd64-current (6.99.40)

2014-05-12 Thread Chavdar Ivanov
Just for the record, the suggested patch did not make any difference for my problem, which otherwise appears to be linked to this discussion - root on raidframe. In my case GENERIC still boots fine if I enable DEBUG and DIAGNOSTIC. Chavdar On 12 May 2014 09:19, Robert Elz k...@munnari.oz.au

Re: Strange boot problems on amd64-current (6.99.40)

2014-05-12 Thread Christos Zoulas
On May 12, 3:19pm, k...@munnari.oz.au (Robert Elz) wrote: -- Subject: Re: Strange boot problems on amd64-current (6.99.40) | One possibility that would be a backwards compatible, and slightly less | hacky (and more flexible) solution, might be to use | | booted_partition =

Re: Strange boot problems on amd64-current (6.99.40)

2014-05-12 Thread Christos Zoulas
On May 12, 4:24pm, ci4...@gmail.com (Chavdar Ivanov) wrote: -- Subject: Re: Strange boot problems on amd64-current (6.99.40) | Just for the record, the suggested patch did not make any difference | for my problem, which otherwise appears to be linked to this | discussion - root on raidframe. In

interface send-q stall in 6.99.40?

2014-05-12 Thread Frank Kardel
Hi, I have two observations on 6.99.44 (amd64/evbarm) where a wm-interface send-queue is filled to the max. sendto()-calls terminate with ENOBUFS. net.interfaces.wm3.sndq.len = 256 net.interfaces.wm3.sndq.maxlen = 256 net.interfaces.wm3.sndq.drops = 20007 the interface status is: wm3:

Re: interface send-q stall in 6.99.40?

2014-05-12 Thread SAITOH Masanobu
Hi, Frank. (2014/05/13 4:56), Frank Kardel wrote: Hi, I have two observations on 6.99.44 (amd64/evbarm) where a wm-interface send-queue is filled to the max. sendto()-calls terminate with ENOBUFS. net.interfaces.wm3.sndq.len = 256 net.interfaces.wm3.sndq.maxlen = 256

Re: interface send-q stall in 6.99.40?

2014-05-12 Thread Manuel Bouyer
On Mon, May 12, 2014 at 09:56:30PM +0200, Frank Kardel wrote: [...] traceroute packets from outside look like the are anwsered, but ICMP ECHO is not answered. The interface recovers with an ifconfig wmX down/up. While I do not know how to provoke this on wm (just happens once a week). I

Re: interface send-q stall in 6.99.40?

2014-05-12 Thread Frank Kardel
On 05/12/14 22:39, Manuel Bouyer wrote: On Mon, May 12, 2014 at 09:56:30PM +0200, Frank Kardel wrote: [...] traceroute packets from outside look like the are anwsered, but ICMP ECHO is not answered. The interface recovers with an ifconfig wmX down/up. While I do not know how to provoke this

daily CVS update output

2014-05-12 Thread NetBSD source update
Updating src tree: P src/crypto/external/bsd/heimdal/dist/kadmin/rpc.c P src/crypto/external/bsd/heimdal/dist/lib/gssapi/krb5/verify_mic.c P src/crypto/external/bsd/heimdal/dist/lib/gssapi/ntlm/creds.c P src/crypto/external/bsd/heimdal/dist/lib/krb5/pac.c P