Re: NFSv4 crash of CURRENT

2024-01-15 Thread Rick Macklem
809af95b at fast_syscall_common+0xf8 > > > > > > > > > > > >> On 15 Jan 2024, at 06:46, FreeBSD User > >> <mailto:free...@walstatt-de.de>> wrote: > > >> > > >> Am Sun, 14 Jan 2024 20:34:12 -0800 > > >>

Re: NFSv4 crash of CURRENT

2024-01-15 Thread FreeBSD User
t; >>> time = 1705306940 > >>> KDB: stack backtrace: > >>> #0 0x806232f5 at kdb_backtrace+0x65 > >>> #1 0x805d7a02 at vpanic+0x152 > >>> #2 0x805d78a3 at panic+0x43 > >>> #3 0x809d58a

Re: NFSv4 crash of CURRENT

2024-01-15 Thread FreeBSD User
reeBSD User >> <mailto:free...@walstatt-de.de>> wrote: > >> > >> Am Sun, 14 Jan 2024 20:34:12 -0800 > >> Cy Schubert mailto:cy.schub...@cschubert.com>> > >> schrieb: > >> > >>> In message > >>> &g

Re: NFSv4 crash of CURRENT

2024-01-15 Thread Peter Blok
+0x38d >>> #4 0x809d58ff at trap_pfault+0x4f >>> #5 0x809af048 at calltrap+0x8 >>> #6 0xffff804c7a7e at ncl_bioread+0xb7e >>> #7 0x804b9d90 at nfs_readdir+0x1f0 >>> #8 0x8069c61a at vop_sigdefer+0x2a >>> #9 0xf

Re: NFSv4 crash of CURRENT

2024-01-15 Thread Peter Blok
; #6 0x804c7a7e at ncl_bioread+0xb7e >> #7 0x804b9d90 at nfs_readdir+0x1f0 >> #8 0xffff8069c61a at vop_sigdefer+0x2a >> #9 0x809f8ae0 at VOP_READDIR_APV+0x20 >> #10 0x81ce75de at autofs_readdir+0x2ce >> #11 0x809f8ae0 at VOP_READDIR

Re: NFSv4 crash of CURRENT

2024-01-15 Thread Rick Macklem
3a9 at sys_getdirentries+0x29 > #14 0x809d6180 at amd64_syscall+0x110 > #15 0x809af95b at fast_syscall_common+0xf8 > > > > On 15 Jan 2024, at 06:46, FreeBSD User wrote: > > Am Sun, 14 Jan 2024 20:34:12 -0800 > Cy Schubert schrieb: > > In message

Re: NFSv4 crash of CURRENT

2024-01-15 Thread Peter Blok
cschubert.com>> >> schrieb: >> >>> In message >>> >> <mailto:CAM5tNy5aat8vUn2fsX9jV=D9yGZdnO20Q0Ea7qtszx+zSES2bw@mail.gmail.c> >>> om> >>> , Rick Macklem writes: >>>> On Sat, Jan 13, 2024 at 12:39=E2=80=AFPM Ron

Re: NFSv4 crash of CURRENT

2024-01-15 Thread Peter Blok
gt;> >>>> >>>> Van: FreeBSD User >>>> Datum: 13 januari 2024 19:34 >>>> Aan: FreeBSD CURRENT >>>> Onderwerp: NFSv4 crash of CURRENT >>>> >>>> Hello, >>>> >>>> running CURRENT client (Fre

Re: NFSv4 crash of CURRENT

2024-01-14 Thread FreeBSD User
19:34 > > > Aan: FreeBSD CURRENT > > > Onderwerp: NFSv4 crash of CURRENT > > > > > > Hello, > > > > > > running CURRENT client (FreeBSD 15.0-CURRENT #4 > > > main-n267556-69748e62e82a= > > : Sat Jan 13 18:08:32 > > &

Re: NFSv4 crash of CURRENT

2024-01-14 Thread Cy Schubert
In message , Rick Macklem writes: > On Sat, Jan 13, 2024 at 12:39=E2=80=AFPM Ronald Klop = > wrote: > > > > > > Van: FreeBSD User > > Datum: 13 januari 2024 19:34 > > Aan: FreeBSD CURRENT > > Onderwerp: NFSv4 crash of CURRENT > > > > Hello

Re: NFSv4 crash of CURRENT

2024-01-14 Thread FreeBSD User
Am Sat, 13 Jan 2024 19:41:30 -0800 Rick Macklem schrieb: > On Sat, Jan 13, 2024 at 12:39 PM Ronald Klop wrote: > > > > > > Van: FreeBSD User > > Datum: 13 januari 2024 19:34 > > Aan: FreeBSD CURRENT > > Onderwerp: NFSv4 crash of CURRENT > > >

Re: NFSv4 crash of CURRENT

2024-01-13 Thread Rick Macklem
On Sat, Jan 13, 2024 at 12:39 PM Ronald Klop wrote: > > > Van: FreeBSD User > Datum: 13 januari 2024 19:34 > Aan: FreeBSD CURRENT > Onderwerp: NFSv4 crash of CURRENT > > Hello, > > running CURRENT client (FreeBSD 15.0-CURRENT #4 main-n267556-69748e62e82a: > Sat

Re: NFSv4 crash of CURRENT

2024-01-13 Thread Ronald Klop
Van: FreeBSD User Datum: 13 januari 2024 19:34 Aan: FreeBSD CURRENT Onderwerp: NFSv4 crash of CURRENT Hello, running CURRENT client (FreeBSD 15.0-CURRENT #4 main-n267556-69748e62e82a: Sat Jan 13 18:08:32 CET 2024 amd64). One NFSv4 server is same OS revision as the mentioned client, other