Date: Fri, 17 Mar 2023 21:09:08 +0100 From: Attila Nagy <nagy.attila@gmail.com> To: Juraj Lutter <juraj@lutter.sk> Cc: Rick Macklem <rick.macklem@gmail.com>, freebsd-stable@freebsd.org Subject: Re: Kernel DHCP unpredictable/fails (PXE boot), userspace DHCP works just fine Message-ID: <CAM2hQG_ZtmGfN5fH=zRN-aUMm1xGooW8C95j9mR6NMpPzVJFwQ@mail.gmail.com> In-Reply-To: <B49BB94F-D1DC-4423-976F-60BFCDCACC48@lutter.sk> References: <CAM2hQG-p=bfSh_nxuah9zcTBbz7HQ9pYyvOR2f6rC=CUGePKsg@mail.gmail.com> <CAM2hQG-oDRsoccg3S1LykyUF=joWbdJz=GSPOnUroDRxjZ2_iQ@mail.gmail.com> <CAM5tNy5riHWthqzdCYncRkqOcTDdoTVy4J0WjNPbsx3zxPksKw@mail.gmail.com> <B49BB94F-D1DC-4423-976F-60BFCDCACC48@lutter.sk>
next in thread | previous in thread | raw e-mail | index | archive | help
--00000000000003c0d905f71e2795 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Juraj Lutter <juraj@lutter.sk> ezt =C3=ADrta (id=C5=91pont: 2023. m=C3=A1rc= . 16., Cs, 23:11): > > > On 16 Mar 2023, at 23:01, Rick Macklem <rick.macklem@gmail.com> wrote: > Haven't you at least partially answered the question yourself here? > In other words, it sounds like there is an issue with the NIC driver > for the newer chip. (If you can replace the NIC with one with > a different chip, I'd try that.) > > > There are more PRs open for bnxt(4) driver, with no obvious solutions. > My personal experience with bnxt(4) is also very ambigous. > > In my last 26 years with FreeBSD, having a Broadcom NIC in my machine has never been a good thing. :( But I still think the problem here lies in bootp_subr. --00000000000003c0d905f71e2795 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">= <div dir=3D"ltr" class=3D"gmail_attr">Juraj Lutter <<a href=3D"mailto:ju= raj@lutter.sk">juraj@lutter.sk</a>> ezt =C3=ADrta (id=C5=91pont: 2023. m= =C3=A1rc. 16., Cs, 23:11):<br></div><blockquote class=3D"gmail_quote" style= =3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding= -left:1ex"><div style=3D"overflow-wrap: break-word;"><br><div><br><blockquo= te type=3D"cite"><div>On 16 Mar 2023, at 23:01, Rick Macklem <<a href=3D= "mailto:rick.macklem@gmail.com" target=3D"_blank">rick.macklem@gmail.com</a= >> wrote:</div><div><span style=3D"font-family:SourceCodePro-Regular;fon= t-size:12px;font-style:normal;font-variant-caps:normal;font-weight:400;lett= er-spacing:normal;text-align:start;text-indent:0px;text-transform:none;whit= e-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inl= ine">Haven't you at least partially answered the question yourself here= ?</span><br style=3D"font-family:SourceCodePro-Regular;font-size:12px;font-= style:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal= ;text-align:start;text-indent:0px;text-transform:none;white-space:normal;wo= rd-spacing:0px;text-decoration:none"><span style=3D"font-family:SourceCodeP= ro-Regular;font-size:12px;font-style:normal;font-variant-caps:normal;font-w= eight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-trans= form:none;white-space:normal;word-spacing:0px;text-decoration:none;float:no= ne;display:inline">In other words, it sounds like there is an issue with th= e NIC driver</span><br style=3D"font-family:SourceCodePro-Regular;font-size= :12px;font-style:normal;font-variant-caps:normal;font-weight:400;letter-spa= cing:normal;text-align:start;text-indent:0px;text-transform:none;white-spac= e:normal;word-spacing:0px;text-decoration:none"><span style=3D"font-family:= SourceCodePro-Regular;font-size:12px;font-style:normal;font-variant-caps:no= rmal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px= ;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:no= ne;float:none;display:inline">for the newer chip. (If you can replace the N= IC with one with</span><br style=3D"font-family:SourceCodePro-Regular;font-= size:12px;font-style:normal;font-variant-caps:normal;font-weight:400;letter= -spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-= space:normal;word-spacing:0px;text-decoration:none"><span style=3D"font-fam= ily:SourceCodePro-Regular;font-size:12px;font-style:normal;font-variant-cap= s:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent= :0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoratio= n:none;float:none;display:inline">a different chip, I'd try that.)</spa= n><br style=3D"font-family:SourceCodePro-Regular;font-size:12px;font-style:= normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-= align:start;text-indent:0px;text-transform:none;white-space:normal;word-spa= cing:0px;text-decoration:none"><br style=3D"font-family:SourceCodePro-Regul= ar;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:40= 0;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:non= e;white-space:normal;word-spacing:0px;text-decoration:none"></div></blockqu= ote><div><br></div>There are more PRs open for bnxt(4) driver, with no obvi= ous solutions.<div>My personal experience with bnxt(4) is also very ambigou= s.</div><br></div></div></blockquote><div>In my last 26 years with FreeBSD,= having a Broadcom NIC in my machine has never been a good thing. :(</div><= div><br></div><div>But I still think the problem here lies in bootp_subr.<b= r></div></div></div> --00000000000003c0d905f71e2795--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAM2hQG_ZtmGfN5fH=zRN-aUMm1xGooW8C95j9mR6NMpPzVJFwQ>