Date: Sat, 31 Dec 2022 18:43:16 -1000 From: "parv/FreeBSD" <parv.0zero9+freebsd@gmail.com> To: Kevin Oberman <rkoberman@gmail.com> Cc: wireless@freebsd.org Subject: Re: "Alder Lake work-around" (was Re: [Bug 268687] rtwn_usb fails after reset triggered when running ssh) Message-ID: <CABObuOq7xy%2BJ80bKWpte-OWwLPtMaBCQAEjhmtfCrrD-wO5h_Q@mail.gmail.com> In-Reply-To: <CAN6yY1vkwwFCaoWAXQF6LTfscZUFMGYoh8GdVDP%2Bd_HrCVBvhQ@mail.gmail.com> References: <bug-268687-21060@https.bugs.freebsd.org/bugzilla/> <CABObuOowCHw32_2Fp0jKgt1pap%2BN0Qb8w2chC=Uv192puhOvwA@mail.gmail.com> <CAN6yY1vkwwFCaoWAXQF6LTfscZUFMGYoh8GdVDP%2Bd_HrCVBvhQ@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Sat, Dec 31, 2022 at 6:40 PM Kevin Oberman wrote: Hi Kevin, Yes. > Ah, thanks. > The final fix was actually committed about two hour before I opened the > ticket. I just finished building and will be installing the new kernel > before the year ends.It i quite similar to KIB's original fix that I was > referring to. > > I have been running KIB's patch for over a month with no problems... all > cores enabled and the pmap enabled. > Oh, that is good to note. Thank you for testing for me/rest of us. Happy New Year! - parv > On Sat, Dec 31, 2022 at 6:40 PM parv/FreeBSD wrote: > >> On Sat, Dec 31, 2022 at 3:15 PM bugzilla-noreply wrote: >> >>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268687 >>> >>> Bug ID: 268687 >>> Summary: rtwn_usb fails after reset triggered when running ssh >>> >> ... >> >>> FreeBSD ptavv 14.0-CURRENT FreeBSD 14.0-CURRENT #4 >>> main-n259888-701b36961cbd-dirty: Thu Dec 29 22:08:49 PST 2022 >>> root@ptavv:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 >>> >>> Running on an Alder Lake i5-1235U with the Alder Lake work-around . >>> >> >> Sorry, what is this "Alder Lake work-around"? >> Is this thing where Intel E-cores are disabled/turned off & P-cores remain >> enabled/turned on? Is there anything more involved? >> > [-- Attachment #2 --] <div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:monospace">On Sat, Dec 31, 2022 at 6:40 PM Kevin Oberman wrote:</div><div class="gmail_default" style="font-family:monospace"><br></div><div class="gmail_default" style="font-family:monospace">Hi Kevin,<br></div><div class="gmail_default" style="font-family:monospace"><br></div></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div style="font-family:tahoma,sans-serif;font-size:small">Yes.</div></div></blockquote><div><br></div><div><div style="font-family:monospace" class="gmail_default">Ah, thanks.</div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div style="font-family:tahoma,sans-serif;font-size:small">The final fix was actually committed about two hour before I opened the ticket. I just finished building and will be installing the new kernel before the year ends.It i quite similar to KIB's original fix that I was referring to.</div><div style="font-family:tahoma,sans-serif;font-size:small"><br></div><div style="font-family:tahoma,sans-serif;font-size:small">I have been running KIB's patch for over a month with no problems... all cores enabled and the pmap enabled.<br></div></div></blockquote><div><br></div><div><div style="font-family:monospace" class="gmail_default">Oh, that is good to note. Thank you for testing for me/rest of us.</div><div style="font-family:monospace" class="gmail_default"><br></div><div style="font-family:monospace" class="gmail_default">Happy New Year!</div><div style="font-family:monospace" class="gmail_default"><br></div><div style="font-family:monospace" class="gmail_default"><br></div><div style="font-family:monospace" class="gmail_default">- parv<br></div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div style="font-family:tahoma,sans-serif;font-size:small"></div></div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Dec 31, 2022 at 6:40 PM parv/FreeBSD wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div dir="ltr"><div style="font-family:monospace">On Sat, Dec 31, 2022 at 3:15 PM bugzilla-noreply<span class="gmail_default" style="font-family:monospace"> </span>wrote:</div></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268687" rel="noreferrer" target="_blank">https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268687</a><br>; <br> Bug ID: 268687<br> Summary: rtwn_usb fails after reset triggered when running ssh<br></blockquote><div><span class="gmail_default" style="font-family:monospace">...</span> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> FreeBSD ptavv 14.0-CURRENT FreeBSD 14.0-CURRENT #4<br> main-n259888-701b36961cbd-dirty: Thu Dec 29 22:08:49 PST 2022 <br> root@ptavv:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64<br> <br> Running on an Alder Lake i5-1235U with the <span class="gmail_default" style="font-family:monospace"> <span class="gmail_default" style="font-family:monospace"></span>Alder Lake work-around </span>.<br></blockquote><div><br></div><div style="font-family:monospace">Sorry, what is this "Alder Lake work-around"?</div><div style="font-family:monospace">Is this thing where Intel E-cores are disabled/turned off & P-cores remain</div><div style="font-family:monospace">enabled/turned on? Is there anything more involved?</div></div></div></blockquote></div></blockquote><div> </div></div></div>help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CABObuOq7xy%2BJ80bKWpte-OWwLPtMaBCQAEjhmtfCrrD-wO5h_Q>