'Protocol not supported' on linux socket call ( r313313 amd64 )

After upgrading of current on amd64 box to r313313 I noticed that skype has stopped working. Below is the end of 'truss' output for skype: 36723: linux_socketcall(1,{ LINUX_SOCKET, 0x0 }) ERR#-93 'Protocol not supported' 36723: write(6,"@",1) = 1 (0x1) 36723: close(6)

Re: 'Protocol not supported' on linux socket call ( r313313 amd64 )

> On Feb 8, 2017, at 07:44, Oleg V. Nauman wrote: > > After upgrading of current on amd64 box to r313313 I noticed that skype has > stopped working. > Below is the end of 'truss' output for skype: > > 36723: linux_socketcall(1,{ LINUX_SOCKET, 0x0 }) ERR#-93 'Protocol

RE: gptzfsboot trouble

The disk is small 320GB but I have tried on a vanilla 600GB drive - same issue - as a matter of fact I have tried on all 5 SATA drives - but I suspect that BIOS could be an issue but I have not seen any updates for years (old machine) I have tried with single drive pools on both 600GB drive and

Re: 'Protocol not supported' on linux socket call ( r313313 amd64 )

Hi Oleg, It seems likely it is related to r313284. Best, Conrad On Wed, Feb 8, 2017 at 7:44 AM, Oleg V. Nauman wrote: > After upgrading of current on amd64 box to r313313 I noticed that skype has > stopped working. > Below is the end of 'truss' output for skype: > >

Re: 'Protocol not supported' on linux socket call ( r313313 amd64 )

On Wednesday 08 February 2017 09:06:43 Conrad Meyer wrote: > Hi Oleg, > > It seems likely it is related to r313284. Kernel compilation fails cc -O2 -pipe -DCOMPAT_FREEBSD32 -DCOMPAT_LINUX32 -march=nehalem -fno-strict- aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -

Re: 'Protocol not supported' on linux socket call ( r313313 amd64 )

On Wednesday 08 February 2017 08:39:50 Ngie Cooper wrote: > > On Feb 8, 2017, at 07:44, Oleg V. Nauman wrote: > > > > After upgrading of current on amd64 box to r313313 I noticed that skype > > has > > stopped working. > > Below is the end of 'truss' output for skype: > >

Re: 'Protocol not supported' on linux socket call ( r313313 amd64 )

On Wednesday 08 February 2017 09:06:43 Conrad Meyer wrote: > Hi Oleg, Hello Conrad, > > It seems likely it is related to r313284. I have reverted both r313285 and r313284, it makes linux socket happy. skype is working now. Thank you! > > Best, > Conrad > > On Wed, Feb 8, 2017 at 7:44 AM,

Crochet build for Pi3 fails to boot on r313441 (and later), works on r313109

r313441 blows up on the Pi3 in /boot/loader.efi with: FreeBSD/arm64 EFI loader, Revision 1.1 (Tue Feb 7 15:15:52 CST 2017 free...@newfs.denninger.net) Failed to start image provided by UFS (14) "Synchronous Abort" handler, esr 0x9604 ELR: 3af62cec LR: 3af61d60 x0 : 0001

RE: gptzfsboot trouble

Getting more and more weird - Installed a vanilla 11-RELEASE using UFS rather ZFS and it issues no errors. Tried to roll back an older snapshot but getting issues as the pool is build using 11-CURRENT. Looking at the part - the LBA complained about is an empty sector (did a dd if=/dev/zero

Re: gptzfsboot trouble

On Tue, 07 Feb 2017 17:08:44 +0100, Thomas Sparrevohn wrote: Hi all Last week I decided to upgrade my FreeBSD installation - it's been a while (September 16 was last time). Unfortunately CURRENT does not boot and cash in a weird way. Both 11-RELEASE

Re: gptzfsboot trouble

> On 8. veebr 2017, at 14:26, Ronald Klop wrote: > > On Tue, 07 Feb 2017 17:08:44 +0100, Thomas Sparrevohn > wrote: > >> Hi all >> >> >> Last week I decided to upgrade my FreeBSD installation - it's been a while >> (September 16 was

Re: gptzfsboot trouble

On Wed, 08 Feb 2017 13:35:22 +0100, Thomas Sparrevohn wrote: What would help? Takes a little while as I have to rebuild to 11-RELEASE each time? 12-CURRENT cashed either before the boot menu or immediately after which could be unrelated - I have photos but

Re: gptzfsboot trouble

On Wed, 08 Feb 2017 13:40:25 +0100, Thomas Sparrevohn wrote: The bug in the bugzilla could be related - what is weird is I have been running this setup for years without issues - which I guess just shows how good ye'ol FreeBSD still is ;-) Tried to run

Re: gptzfsboot trouble

> On 8. veebr 2017, at 14:51, Ronald Klop wrote: > > On Wed, 08 Feb 2017 13:40:25 +0100, Thomas Sparrevohn > wrote: > >> >> The bug in the bugzilla could be related - what is weird is I have been >> running this setup for years

RE: gptzfsboot trouble

Ok Basic data included -Original Message- From: Ronald Klop [mailto:ronald-li...@klop.ws] Sent: 08 February 2017 12:51 To: Thomas Sparrevohn ; FreeBSD Current Subject: Re: gptzfsboot trouble On Wed, 08 Feb 2017 13:40:25