From nobody Sun Jan 01 04:43:16 2023 X-Original-To: wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Nl60w4s0Sz2nXVC for ; Sun, 1 Jan 2023 04:47:12 +0000 (UTC) (envelope-from parv.0zero9@gmail.com) Received: from mail-ej1-x62a.google.com (mail-ej1-x62a.google.com [IPv6:2a00:1450:4864:20::62a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Nl60w2gRNz3GnP for ; Sun, 1 Jan 2023 04:47:12 +0000 (UTC) (envelope-from parv.0zero9@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x62a.google.com with SMTP id gh17so60148746ejb.6 for ; Sat, 31 Dec 2022 20:47:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=gJodF+aIZYTXOzj9CG7AJvS6WmJ+BNwjSHnh8AQN/2s=; b=OnXb+X4ZQSMv8vyjCobyl9Jzfsg1X38CP1DRGkJgw+fSW4uRTNDsLrqSo+6v6n9fKq HK7i2HMKVlVYxshhe1LSjR96E3en9PG9Y2RO9KGcl7rlRtRy0ZBxI5bgO1z3M1KaP01t +69HxQO2vzEczNBgWTaxGpSjOgvP+vVbmAIvfE7bYBsHRj5Jqw4goWtC+KxuX2T9Z3lk FiRHM8Es/4edW2t5Kt+komwqf9qBNhpTXV/NqYhBGC3HnNRKRS7KkXhcbfhelAjHfzuQ HmgM/tj1tN3VrqS8gmkkWk8Bk8lSLgxQLhsRdeR4k/PE/pZuTj76IX11UhEZalHMcUfj PLhQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=gJodF+aIZYTXOzj9CG7AJvS6WmJ+BNwjSHnh8AQN/2s=; b=QAiGeyfyJ4SsUUJEWKepJG2w5Fb2F2CmqLNSFb7FM6Hdn8mC9IL6i/sN/7o9cyMWK/ CdhWTSROJlZ7wNX8HyIotOhCfcg/rqnRtgXjaHYaG5+PFAfvnR3JheHOif11XlaHhs8A 9hVNN46OYw2BtnqquZzeVdnEYwRW/REapsEyJZbl0UuJoznwuxurg3r9hpPeHH/qathM cpAutGyIxEVv34ZCT1zx8kYmztTyyF88szSGHaENXs3a2iSbXhGozPAZ5tA3RW8jD6lA IG9NwPucCBsxlcjYliCCDwqEPdbGrTHTV1OaSrXQySo1CYbzLZcXWCTIgtihdlcB0GpD 5+GQ== X-Gm-Message-State: AFqh2kpbjysSulOf6zZPx57avirVnI1iaKZdY7greN/rM/LQKLU+htJ1 i171cGzCJUCxaT+sJ0hjNMfVR78RV1E0atoY3S0OGerL6cA= X-Google-Smtp-Source: AMrXdXuT5AtRvp0Cy1ikETJZrei9PkjVu0ABRgREWS+lDUL8knsXGCd2Rsob1b5gh1ygiBLmq4PwBlxVukY0Ia71W+k= X-Received: by 2002:a17:906:cc87:b0:7c4:ec55:59e with SMTP id oq7-20020a170906cc8700b007c4ec55059emr2184468ejb.611.1672548431139; Sat, 31 Dec 2022 20:47:11 -0800 (PST) List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: "parv/FreeBSD" Date: Sat, 31 Dec 2022 18:43:16 -1000 Message-ID: Subject: Re: "Alder Lake work-around" (was Re: [Bug 268687] rtwn_usb fails after reset triggered when running ssh) To: Kevin Oberman Cc: wireless@freebsd.org Content-Type: multipart/alternative; boundary="0000000000001b984205f12c8763" X-Rspamd-Queue-Id: 4Nl60w2gRNz3GnP X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[freebsd] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --0000000000001b984205f12c8763 Content-Type: text/plain; charset="UTF-8" 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? >> > --0000000000001b984205f12c8763 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sat, Dec 31, 2022 at 6:40 PM Kevin Oberman wrote:

<= div class=3D"gmail_default" style=3D"font-family:monospace">Hi Kevin,

=
Yes.

Ah, thanks.

=C2=A0
The f= inal 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 y= ear ends.It i quite similar to KIB's original fix that I was referring = to.

<= /div>
I have be= en running KIB's patch for over a month with no problems... all cores e= nabled and the pmap enabled.

Oh, that is = good to note. Thank you for testing for me/rest of us.

Happy New Year!


- parv

= =C2=A0
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_bu= g.cgi?id=3D268687

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Bug ID: 268687
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Summary: rtwn_usb fails after rese= t triggered when running ssh
...=C2=A0
FreeBSD ptavv 14.0-CURRENT FreeBSD 14.0-CURRENT #4
main-n259888-701b36961cbd-dirty: Thu Dec 29 22:08:49 PST 2022=C2=A0 =C2=A0 =
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/t= urned off & P-cores remain
en= abled/turned on? Is there anything more involved?
=C2=A0
--0000000000001b984205f12c8763--