Re: panic: sleeping thread on r352386

2019-09-18 Thread Peter Jeremy
On 2019-Sep-17 15:24:30 +0300, Konstantin Belousov wrote: >Try this. > >diff --git a/sys/fs/nfsclient/nfs_clport.c b/sys/fs/nfsclient/nfs_clport.c >index 63ea4736707..a23b4ba4efa 100644 Sorry for the delay but I'm not seeing problems with this version of your patch (now r352457) either. Thank

Re: panic: sleeping thread on r352386

2019-09-17 Thread Masachika ISHIZUKA
>> >Try the following change, which more accurately tries to avoid >> >vnode_pager_setsize(). The real cause requires much more extensive >> >changes. >> > >> >diff --git a/sys/fs/nfsclient/nfs_clport.c b/sys/fs/nfsclient/nfs_clport.c >> >index 63ea4736707..16dc7745c77 100644 >> >---

Re: panic: sleeping thread on r352386

2019-09-17 Thread Konstantin Belousov
On Tue, Sep 17, 2019 at 08:18:26PM +1000, Peter Jeremy wrote: > On 2019-Sep-17 11:06:58 +0300, Konstantin Belousov > wrote: > >Try the following change, which more accurately tries to avoid > >vnode_pager_setsize(). The real cause requires much more extensive > >changes. > > > >diff --git

Re: panic: sleeping thread on r352386

2019-09-17 Thread Masachika ISHIZUKA
>>Try the following change, which more accurately tries to avoid >>vnode_pager_setsize(). The real cause requires much more extensive >>changes. >> >>diff --git a/sys/fs/nfsclient/nfs_clport.c b/sys/fs/nfsclient/nfs_clport.c >>index 63ea4736707..16dc7745c77 100644 >>---

Re: panic: sleeping thread on r352386

2019-09-17 Thread Peter Jeremy
On 2019-Sep-17 11:06:58 +0300, Konstantin Belousov wrote: >Try the following change, which more accurately tries to avoid >vnode_pager_setsize(). The real cause requires much more extensive >changes. > >diff --git a/sys/fs/nfsclient/nfs_clport.c b/sys/fs/nfsclient/nfs_clport.c >index

Re: panic: sleeping thread on r352386

2019-09-17 Thread Konstantin Belousov
On Tue, Sep 17, 2019 at 02:42:51PM +0900, Masachika ISHIZUKA wrote: > >> This panic happens on 1300047 (both r352239 and r352386) with core > >> i5-7500 as follows. This panic dose not happen on r351728 (1300044). > >> (The following lines were typed by hand so they might have some miss > >>

Re: panic: sleeping thread on r352386

2019-09-16 Thread Masachika ISHIZUKA
>> This panic happens on 1300047 (both r352239 and r352386) with core >> i5-7500 as follows. This panic dose not happen on r351728 (1300044). >> (The following lines were typed by hand so they might have some miss >> typed letters.) >> >> == >> Sleeping thread (tid 100177, pid 1814) owns a

Re: panic: sleeping thread on r352386

2019-09-16 Thread Alastair Hogge
On Monday, 16 September 2019 7:55:32 PM AWST Masachika ISHIZUKA wrote: > Hi. > > This panic happens on 1300047 (both r352239 and r352386) with core > i5-7500 as follows. This panic dose not happen on r351728 (1300044). > (The following lines were typed by hand so they might have some miss >

panic: sleeping thread on r352386

2019-09-16 Thread Masachika ISHIZUKA
Hi. This panic happens on 1300047 (both r352239 and r352386) with core i5-7500 as follows. This panic dose not happen on r351728 (1300044). (The following lines were typed by hand so they might have some miss typed letters.) == Sleeping thread (tid 100177, pid 1814) owns a non-sleepable lock