Re: NFSv3 issues with latest -current

2017-10-31 Thread Yuri Pankov
On Wed, 1 Nov 2017 00:27:50 +, Rick Macklem wrote: Rodney W. Grimes wrote: [stuff snipped] I wrote: Btw, NFS often causes this because... - Typically TSO is limited to a 64K packet (including TCP/IP and MAC headers). - When NFS does reading/writing, it will do 64K + NFS, TCP/IP and MAC head

Re: NFSv3 issues with latest -current

2017-10-31 Thread Rick Macklem
Rodney W. Grimes wrote: [stuff snipped] > I wrote: >> Btw, NFS often causes this because... >> - Typically TSO is limited to a 64K packet (including TCP/IP and MAC >> headers). >> - When NFS does reading/writing, it will do 64K + NFS, TCP/IP and MAC headers >> for an RPC (or a multiple of 64K li

Re: Segfault in _Unwind_* code called from pthread_exit

2017-10-31 Thread Gerald Pfeifer
On Tue, 31 Oct 2017, Andreas Tobler wrote: > Do we, FreeBSD'ers, want to have gcc unwind support on older than > FreeBSD 9.3 releases? I think the gcc folks do not care, but we are the > ones who might have an need for such a support? > @Gerald, do you have an opinion? Yes. No. :-) Those possib

Re: Segfault in _Unwind_* code called from pthread_exit

2017-10-31 Thread Andreas Tobler
On 31.10.17 22:36, Gerald Pfeifer wrote: On Tue, 31 Oct 2017, Andreas Tobler wrote: Do we, FreeBSD'ers, want to have gcc unwind support on older than FreeBSD 9.3 releases? I think the gcc folks do not care, but we are the ones who might have an need for such a support? @Gerald, do you have an op

Re: Segfault in _Unwind_* code called from pthread_exit

2017-10-31 Thread Konstantin Belousov
On Tue, Oct 31, 2017 at 08:37:29PM +0100, Andreas Tobler wrote: > On 31.10.17 10:28, Konstantin Belousov wrote: > > On Mon, Oct 30, 2017 at 10:54:05PM +0100, Andreas Tobler wrote: > >> On 30.10.17 15:32, Tijl Coosemans wrote: > >>> On Sun, 29 Oct 2017 20:40:46 +0100 Andreas Tobler > >>> wrote: >

Re: Segfault in _Unwind_* code called from pthread_exit

2017-10-31 Thread Andreas Tobler
On 31.10.17 10:28, Konstantin Belousov wrote: On Mon, Oct 30, 2017 at 10:54:05PM +0100, Andreas Tobler wrote: On 30.10.17 15:32, Tijl Coosemans wrote: On Sun, 29 Oct 2017 20:40:46 +0100 Andreas Tobler wrote: Attached what I have for libgcc. It can be applied to gcc5-8, should give no issues.

Re: NFSv3 issues with latest -current

2017-10-31 Thread Rodney W. Grimes
> Cy Schubert wrote: > [stuff snipped] > >The sysctl is net.inet.tcp.tso. You can also disable tso through ifconfig > >for an interface. > > > For testing this case, I'd recommend using the sysctl. Since the net device > driver is often the culprit, that device driver might not handle the > "ifcon

Re: panic: vtopde on a uva/gpa 0x1030000 @r325228 (amd64)

2017-10-31 Thread David Wolfskill
On Tue, Oct 31, 2017 at 02:35:19PM +0200, Andriy Gapon wrote: > On 31/10/2017 14:32, David Wolfskill wrote: > > Andriy, I "cloned" the slice before doing the above, so I can poke > > at this a bit more (e.g., try to get a crash dump), if that would > > still be useful. > > Yes, it would be, as I c

Re: NFSv3 issues with latest -current

2017-10-31 Thread Rick Macklem
Cy Schubert wrote: [stuff snipped] >The sysctl is net.inet.tcp.tso. You can also disable tso through ifconfig >for an interface. > For testing this case, I'd recommend using the sysctl. Since the net device driver is often the culprit, that device driver might not handle the "ifconfig" correctly ei

Re: panic: vtopde on a uva/gpa 0x1030000 @r325228 (amd64)

2017-10-31 Thread Andriy Gapon
On 31/10/2017 14:32, David Wolfskill wrote: > Andriy, I "cloned" the slice before doing the above, so I can poke > at this a bit more (e.g., try to get a crash dump), if that would > still be useful. Yes, it would be, as I currently do not see what the problem with r325227 is. -- Andriy Gapon __

Re: panic: vtopde on a uva/gpa 0x1030000 @r325228 (amd64)

2017-10-31 Thread David Wolfskill
On Tue, Oct 31, 2017 at 01:53:27PM +0200, Konstantin Belousov wrote: > ... > > db> > > Try to revert r325227. OK; did that, via "svn merge -c -r325227 ^/head"; rebuilt/installed kernel, and a reboot was ... boringly normal. :-) FreeBSD freebeast.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT

Re: panic: vtopde on a uva/gpa 0x1030000 @r325228 (amd64)

2017-10-31 Thread Andriy Gapon
On 31/10/2017 13:37, David Wolfskill wrote: > Any suggestions for diagnosing or fixing it? Try setting a dump device via loader.conf (e.g. dumpdev="ada0p99") and obtaining a crash dump. -- Andriy Gapon ___ freebsd-current@freebsd.org mailing list https

Re: panic: vtopde on a uva/gpa 0x1030000 @r325228 (amd64)

2017-10-31 Thread Konstantin Belousov
On Tue, Oct 31, 2017 at 04:37:10AM -0700, David Wolfskill wrote: > Performed the usual src update in head/amd64; today was from r325137 to > r325228. Laptop had no complaints; everything Just Worked (as usual). > > GEOM: new disk da1 > panic: vtopde on a uva/gpa 0x103 > cpuid = 5 > time = 15

panic: vtopde on a uva/gpa 0x1030000 @r325228 (amd64)

2017-10-31 Thread David Wolfskill
Performed the usual src update in head/amd64; today was from r325137 to r325228. Laptop had no complaints; everything Just Worked (as usual). This time, it was the build machine that whined -- rather less inconvenient for me. :-} Here's what it says currently: ... APIC: Using the MADT enumerato

Re: Segfault in _Unwind_* code called from pthread_exit

2017-10-31 Thread Tijl Coosemans
On Mon, 30 Oct 2017 22:54:05 +0100 Andreas Tobler wrote: > On 30.10.17 15:32, Tijl Coosemans wrote: >> On Sun, 29 Oct 2017 20:40:46 +0100 Andreas Tobler >> wrote: >>> Attached what I have for libgcc. It can be applied to gcc5-8, should >>> give no issues. The mentioned tc from this thread and

Re: Segfault in _Unwind_* code called from pthread_exit

2017-10-31 Thread Konstantin Belousov
On Mon, Oct 30, 2017 at 10:54:05PM +0100, Andreas Tobler wrote: > On 30.10.17 15:32, Tijl Coosemans wrote: > > On Sun, 29 Oct 2017 20:40:46 +0100 Andreas Tobler > > wrote: > >> Attached what I have for libgcc. It can be applied to gcc5-8, should > >> give no issues. The mentioned tc from this thr