From: Neftin, Sasha <sasha.neftin@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH] e1000e: bump up timeout to wait when ME un-configure ULP mode
Date: Sun, 5 Apr 2020 09:46:26 +0300 [thread overview]
Message-ID: <00b477c9-ef20-be95-1748-44efba18ebd3@intel.com> (raw)
In-Reply-To: <1c0e602f-1fe7-62b1-2283-b98783782e87@canonical.com>
On 4/3/2020 06:15, Aaron Ma wrote:
> Hi Jeffrey:
>
> I have received the email that you apply this patch to next-queue branch
> dev-queue.
>
> But after this branch is rebased to v5.6, I can't find it.
>
> Will you apply again?
Aaron, Kai,
S0ix flow supported only on none ME system. Our PAE works to communicate
this to OS vendors. You should get BIOS option to disable ME on your system.
This fix just will mask real problem on specific system - won't be solve
the problem. I suggest recall this patch and Lenovo Carbon in DMI black
list.
>
> Thanks,
> Aaron
>
> On 4/2/20 8:31 PM, Hans de Goede wrote:
>>
>> This fix fixes a real problem, on a popular model laptop
>> and since it just extends a timeout it is a pretty harmless
>> (no chance of regressions) fix. As such since there seems
>> to be no other solution in sight, can we please move forward
>> with this fix for now ?
Thanks,
Sasha
prev parent reply other threads:[~2020-04-05 6:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 19:16 [Intel-wired-lan] [PATCH] e1000e: bump up timeout to wait when ME un-configure ULP mode Aaron Ma
2020-03-25 4:17 ` Kai-Heng Feng
2020-03-25 6:36 ` Neftin, Sasha
2020-03-25 6:39 ` Kai-Heng Feng
2020-03-25 6:42 ` Tsai, Rex
2020-03-25 6:49 ` Aaron Ma
2020-03-25 6:43 ` Aaron Ma
2020-03-25 13:58 ` Neftin, Sasha
2020-03-25 14:07 ` Aaron Ma
2020-03-25 15:49 ` Paul Menzel
2020-03-26 11:29 ` Kai-Heng Feng
2020-03-26 11:41 ` Paul Menzel
2020-03-26 14:34 ` Neftin, Sasha
2020-03-26 18:37 ` Paul Menzel
2020-03-28 10:55 ` David Laight
2020-04-02 12:31 ` Hans de Goede
2020-04-03 3:15 ` Aaron Ma
2020-04-03 7:37 ` Paul Menzel
2020-04-05 6:46 ` Neftin, Sasha [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=00b477c9-ef20-be95-1748-44efba18ebd3@intel.com \
--to=sasha.neftin@intel.com \
--cc=intel-wired-lan@osuosl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox