daily CVS update output

Updating src tree: P src/sys/arch/x86/include/pmap.h P src/sys/arch/x86/x86/pmap.c P src/sys/arch/x86/x86/vm_machdep.c P src/sys/dev/mii/inbmphyreg.h P src/sys/dev/mii/inphy.c P src/sys/dev/mii/makphy.c P src/sys/dev/pci/if_wm.c P src/sys/kern/kern_exit.c P src/tests/kernel/t_ptrace.c P

Re: wait4(2) do not fail with WNOHANG if there is no child

Date:Sun, 6 Nov 2016 09:34:17 +0100 From:Nicolas Joly Message-ID: <20161106083417.ga6...@issan.sis.pasteur.fr> | Just encountered a case where wait(4) + WNOHANG do not fail with | expected ECHILD when there is no process to wait. Can you

Re: ffs_newvnode: inode has non zero blocks

> | There are some further changes needed to cover a possible dup alloc , > | and to keep the !wapbl case recoverable by fsck. There is ongoing > | discussion on source-changes about that, hope we finalise fix later in > | the week. > > Leaving a filesystem problem committed on head that can cause

Re: ffs_newvnode: inode has non zero blocks

On Nov 8, 11:51am, jaromir.dole...@gmail.com (=?UTF-8?B?SmFyb23DrXIgRG9sZcSNZWs=?=) wrote: -- Subject: Re: ffs_newvnode: inode has non zero blocks | Yes, that problem is related to the wapbl change. I've committed a bug | fix, so newer kernel shouldn't trigger the panic any more. | | There are

Re: ffs_newvnode: inode has non zero blocks

Yes, that problem is related to the wapbl change. I've committed a bug fix, so newer kernel shouldn't trigger the panic any more. There are some further changes needed to cover a possible dup alloc , and to keep the !wapbl case recoverable by fsck. There is ongoing discussion on source-changes

Re: wm WOL not working anymore

Hi, Frank. On 2016/10/24 14:56, Masanobu SAITOH wrote: Hello. On 2016/10/22 19:32, Frank Kardel wrote: Hi ! There has be quite some work going on for wm interfaces. When testing current kernels I found that some time after if_wm.c:1.347 the WOL functionality has stopped working on my ASRock