Re: 7.99.42/Nov 2 panic: kernel diagnostic assertion "l->l_md.md_gc_ptp == NULL" failed

49691

Re: ffs_newvnode: inode has non zero blocks

Earlier, I wrote: > Also, I have now narrowed down the appearance of the problem on the > testbed to the following commit: > > 2016.10.30.15.01.46 christos src/sys/ufs/ffs/ffs_alloc.c 1.154 > > The mystery remains because the commit message says there should be no > functional change, and I

Re: 7.99.42/Nov 2 panic: kernel diagnostic assertion "l->l_md.md_gc_ptp == NULL" failed

On Mon, Nov 07, 2016 at 10:13:16PM +, co...@sdf.org wrote: > 49691 Thanks. So it's most visible with go programs, and there are two patches to discuss. https://mail-index.netbsd.org/port-amd64/2015/06/23/msg002276.html by KAMADA Ken'ichi and

Re: ffs_newvnode: inode has non zero blocks

Jaromír Doleček wrote: > There was recenly change a change in FFS in the general area for > WAPBL. Can you try attached patch and check if following KASSERT() > triggers? I'm afraid I took your request literally and tested a release build with your patch and no other changes. Since KASSERT does

TCP on IPv6 when IPV6_USE_MIN_MTU is set

Folks, This is not limited to NetBSD current but with all NetBSD releases with IPv6, and other BSD based varients as well. Applications which do not want to depend on Path MTU Discovery may set IPV6_USE_MIN_MTU=1 to use IPv6_MMTU (1280) as defined in RFC3542. This works well for UDP as long as

Re: Automated report: NetBSD-current/i386 build success

In article , seeman doy wrote: >-=-=-=-=-=- > >hi im installing a netbsd_7.0 in a computer with 1.3ghz amd duron k7 >cpu,ram is 256mb,my computer wont boot,i used the i386iso,should I use the >amd64iso,,,pls

Re: Automated report: NetBSD-current/i386 build success

hi im installing a netbsd_7.0 in a computer with 1.3ghz amd duron k7 cpu,ram is 256mb,my computer wont boot,i used the i386iso,should I use the amd64iso,,,pls help me thanks,,, On Tue, Nov 1, 2016 at 1:45 PM, NetBSD Test Fixture wrote: > The NetBSD-current/i386 build is