kern/147756: [libc] open_socket_in: Protocol not supported -
after a few days?
Martin Minkus
martin.minkus at pulseutilities.co.nz
Mon Aug 9 21:40:05 UTC 2010
The following reply was made to PR kern/147756; it has been noted by GNATS.
From: Martin Minkus <martin.minkus at pulseutilities.co.nz>
To: bug-followup <bug-followup at FreeBSD.org>, dot <dot at kkursor.ru>
Cc:
Subject: RE: kern/147756: [libc] open_socket_in: Protocol not supported - after
a few days?
Date: Tue, 10 Aug 2010 09:23:21 +1200
--2_0_c2_b54b62MHTML_=_01
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
In my case it was bad hardware. Seemed to be the PCI bus, so probably
the southbridge.
=20
Anything using PCIe was completely unaffected, and mem tests running for
days passed fine.
=20
Traffic going over the pci bus, even the onboard nic would silently get
corrupted.
=20
Moved the hardware onto a new motherboard and all the issues magically
disappeared.....
=20
From: Kirill A Sarksyan [mailto:dot at kkursor.ru]=20
Sent: Tuesday, 10 August 2010 00:35
To: bug-followup at FreeBSD.org; Martin Minkus
Subject: Re: kern/147756: [libc] open_socket_in: Protocol not supported
- after a few days?
=20
I confirm this on FreeBSD 7.3-RELEASE #12: Thu Jul 1 01:27:47 MSD 2010.
On start Samba log contains:
[2010/08/09 16:19:04, 1] smbd/files.c:177(file_init)
file_init: Information only: requested 16384 open files, 7014 are
available.
[2010/08/09 16:19:04, 0] lib/util_sock.c:902(open_socket_in)
open_socket_in(): socket() call failed: Protocol not supported
[2010/08/09 16:19:04, 0] smbd/server.c:457(smbd_open_one_socket)
smbd_open_once_socket: open_socket_in: Protocol not supported
[2010/08/09 16:19:04, 0] lib/util_sock.c:902(open_socket_in)
open_socket_in(): socket() call failed: Protocol not supported
[2010/08/09 16:19:04, 0] smbd/server.c:457(smbd_open_one_socket)
smbd_open_once_socket: open_socket_in: Protocol not supported
%pkg_info | grep samba
samba34-3.4.8 A free SMB and CIFS client and server for UNIX
And Windows clients cannot use Samba shares at all.
--2_0_c2_b54b62MHTML_=_01
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-mi=
crosoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:wo=
rd" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D=
"http://www.w3.org/TR/REC-html40">
<head>
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
=2EMsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3DEN-NZ link=3Dblue vlink=3Dpurple>
<div class=3DWordSection1>
<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri=
","sans-serif";
color:#1F497D'>In my case it was bad hardware. Seemed to be the PCI bus, s=
o
probably the southbridge.<o:p></o:p></span>
</p>
<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri=
","sans-serif";
color:#1F497D'><o:p> </o:p></span>
</p>
<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri=
","sans-serif";
color:#1F497D'>Anything using PCIe was completely unaffected, and mem tes=
ts
running for days passed fine.<o:p></o:p></span>
</p>
<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri=
","sans-serif";
color:#1F497D'><o:p> </o:p></span>
</p>
<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri=
","sans-serif";
color:#1F497D'>Traffic going over the pci bus, even the onboard nic would=
silently get corrupted.<o:p></o:p></span>
</p>
<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri=
","sans-serif";
color:#1F497D'><o:p> </o:p></span>
</p>
<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri=
","sans-serif";
color:#1F497D'>Moved the hardware onto a new motherboard and all the issu=
es magically
disappeared.....<o:p></o:p></span>
</p>
<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri=
","sans-serif";
color:#1F497D'><o:p> </o:p></span>
</p>
<div>
<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0c=
m 0cm 0cm'>
<p class=3DMsoNormal><b><span lang=3DEN-US style=3D'font-size:10.0pt;font=
-family:
"Tahoma","sans-serif"'>From:</span></b><span lang=3DEN-US style=3D'font-s=
ize:10.0pt;
font-family:"Tahoma","sans-serif"'> Kirill A Sarksyan [mailto:dot at kkursor=
=2Eru] <br>
<b>Sent:</b> Tuesday, 10 August 2010 00:35<br>
<b>To:</b> bug-followup at FreeBSD.org; Martin Minkus<br>
<b>Subject:</b> Re: kern/147756: [libc] open_socket_in: Protocol not supp=
orted
- after a few days?<o:p></o:p></span>
</p>
</div>
</div>
<p class=3DMsoNormal><o:p> </o:p>
</p>
<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>I confirm this on Fre=
eBSD
7.3-RELEASE #12: Thu Jul 1 01:27:47 MSD 2010.<br>
On start Samba log contains:<br>
[2010/08/09 16:19:04, 1] smbd/files.c:177(file_init)<br>
file_init: Information only: requested 16384 open files, 7014 are
available.<br>
[2010/08/09 16:19:04, 0] lib/util_sock.c:902(open_socket_in)<br>
open_socket_in(): socket() call failed: Protocol not supported<br>=
[2010/08/09 16:19:04, 0] smbd/server.c:457(smbd_open_one_socket)<br=
>
smbd_open_once_socket: open_socket_in: Protocol not supported<br>
[2010/08/09 16:19:04, 0] lib/util_sock.c:902(open_socket_in)<br>
open_socket_in(): socket() call failed: Protocol not supported<br>=
[2010/08/09 16:19:04, 0] smbd/server.c:457(smbd_open_one_socket)<br=
>
smbd_open_once_socket: open_socket_in: Protocol not supported<br>
<br>
%pkg_info | grep samba<br>
samba34-3.4.8 A free SMB and CIFS cli=
ent
and server for UNIX<br>
<br>
And Windows clients cannot use Samba shares at all.<br>
<br>
<o:p></o:p>
</p>
</div>
</body>
</html>
--2_0_c2_b54b62MHTML_=_01--
More information about the freebsd-bugs
mailing list