boot broken on VMWare somewhere between r300069 and r300176

I did an IFC on my drm-next-4.6 branch yesterday at r300069. I just did an IFC to r300176 and boot will hang right ater printing out "setting hostid: ". ^T just shows sh [piperd]. ddb just shows the shell as hanging in piperead. Diffing between those two revisions I don't see any obvious offenders

Jenkins build is back to normal : FreeBSD_HEAD_sparc64 #74

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

Build failed in Jenkins: FreeBSD_HEAD_sparc64 #73

See -- Started by upstream project "FreeBSD_HEAD" build number 290 originally caused by: Started by an SCM change > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote

Re: r299512 breaks dhclient on some networks

On Wed, May 18, 2016 at 5:19 PM, Don Lewis wrote: > > It looks to me like r299512 is changing the format of the client > identifier by inserting the struct hardware hlen field into it. Yes. The problem with r299512 is that it assumed the client_id was actually a valid struct hardware, as the arr

Re: r299512 breaks dhclient on some networks

On 05/18/16 20:19, Don Lewis wrote > It looks to me like r299512 is changing the format of the client > identifier by inserting the struct hardware hlen field into it. That's > not valid if htype is non-zero the way I interpret RFC 2132. On the > other hand, I would think that the server would in

Re: r299512 breaks dhclient on some networks

On 05/18/16 19:49, Conrad Meyer wrote: > Hey Ian, > > r299512 incorrectly encoded client identifiers because I misunderstood > the intent of the sizeof()-scaled client_id. I reverted that change > and replaced it with r300174, which I believe fixes the first overrun > more correctly. Just checked

Re: r299512 breaks dhclient on some networks

On 18 May, To: c...@freebsd.org wrote: > On 18 May, Conrad Meyer wrote: >> Hey Ian, >> >> r299512 incorrectly encoded client identifiers because I misunderstood >> the intent of the sizeof()-scaled client_id. I reverted that change >> and replaced it with r300174, which I believe fixes the first

Re: r299512 breaks dhclient on some networks

On 18 May, Conrad Meyer wrote: > Hey Ian, > > r299512 incorrectly encoded client identifiers because I misunderstood > the intent of the sizeof()-scaled client_id. I reverted that change > and replaced it with r300174, which I believe fixes the first overrun > more correctly. > > (Coverity may s

Re: r299512 breaks dhclient on some networks

On 18 May, Ian FREISLICH wrote: > Hi > > I cannot for the life of me figure out why the change in r299512 breaks > DHCP on one network I use but not on another network. > > The only clue I can find is that the request whose response is ignored > has the following client ID: > 1:6:0:22:5f:70:a1:d

Re: r299512 breaks dhclient on some networks

Hey Ian, r299512 incorrectly encoded client identifiers because I misunderstood the intent of the sizeof()-scaled client_id. I reverted that change and replaced it with r300174, which I believe fixes the first overrun more correctly. (Coverity may still complain about CID 1305550, but I don't be

Re: riscv buildkernel error

> On 18 May 2016, at 22:40 , Shawn Webb wrote: > >> On May 17, 2016, at 4:47 PM, Shawn Webb wrote: >> >> Hey All, >> >> I’m getting this error when doing a buildkernel for RISC-V on the latest >> HEAD: >> >> === Begin Log === >> In file included from /usr/src/sys/riscv/riscv/genassym.c:44:0

r299512 breaks dhclient on some networks

Hi I cannot for the life of me figure out why the change in r299512 breaks DHCP on one network I use but not on another network. The only clue I can find is that the request whose response is ignored has the following client ID: 1:6:0:22:5f:70:a1:df The request whose response is use has this cl

Re: riscv buildkernel error

> On May 17, 2016, at 4:47 PM, Shawn Webb wrote: > > Hey All, > > I’m getting this error when doing a buildkernel for RISC-V on the latest HEAD: > > === Begin Log === > In file included from /usr/src/sys/riscv/riscv/genassym.c:44:0: > /usr/src/sys/sys/bus.h:688:23: fatal error: device_if.h: No

Jenkins build is back to normal : FreeBSD_HEAD_sparc64 #71

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

Build failed in Jenkins: FreeBSD_HEAD_sparc64 #70

See -- [...truncated 179887 lines...] --- tty_outq.o --- cc -c -O -pipe -g -nostdinc -I. -I/builds/workspace/FreeBSD_HEAD_sparc64/src/sys -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_glob

alc0 aliases not working anymore after update to r300138

Hello all. I just rebuild current today, and now I can not use aliases on my network interface anymore. FreeBSD desk.server.testdomain.nl 11.0-CURRENT FreeBSD 11.0-CURRENT #6 r300138: Wed May 18 14:30:38 CEST 2016 r...@desk.server.testdomain.nl:/usr/obj/usr/src/sys/KRNL amd64 my /etc/rc.con

Build failed in Jenkins: FreeBSD_HEAD_sparc64 #69

See -- [...truncated 180267 lines...] cc -c -O -pipe -g -nostdinc -I. -I/builds/workspace/FreeBSD_HEAD_sparc64/src/sys -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -MD -MF.depe

Build failed in Jenkins: FreeBSD_HEAD_sparc64 #68

See -- [...truncated 207735 lines...] --- tty.o --- cc -c -O -pipe -g -nostdinc -I. -I/builds/workspace/FreeBSD_HEAD_sparc64/src/sys -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h

Build failed in Jenkins: FreeBSD_HEAD_sparc64 #67

See -- Started by upstream project "FreeBSD_HEAD" build number 159 originally caused by: Started by an SCM change > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote

Build failed in Jenkins: FreeBSD_HEAD #285

See -- [...truncated 315716 lines...] ===> usr.sbin/makemap (installconfig) ===> usr.sbin/praliases (installconfig) ===> usr.sbin/sendmail (installconfig) ===> usr.sbin/tcpdchk (installconfig) ===> usr.sbin