Received-SPF: pass (google.com: domain of linux-kernel+bounces-181752-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161;
Message-ID: <51c51cb7-db66-4187-a7e4-6dd3044579b7@molgen.mpg.de>
Date: Fri, 17 May 2024 07:50:32 +0200
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [Intel-wired-lan] [linus:master] [e1000e] 861e808602:
 suspend-stress.fail (e1000e: move force SMBUS from enable ulp function to
 avoid PHY loss issue)
To: Rui Zhang <rui.zhang@intel.com>, Oliver Sang <oliver.sang@intel.com>
Cc: Yu C Chen <yu.c.chen@intel.com>, Dima Ruinskiy <dima.ruinskiy@intel.com>,
 Vitaly Lifshits <vitaly.lifshits@intel.com>,
 Naamax Meir <naamax.meir@linux.intel.com>, intel-wired-lan@lists.osuosl.org,
 oe-lkp@lists.linux.dev, linux-kernel@vger.kernel.org,
 Anthony L Nguyen <anthony.l.nguyen@intel.com>,
 Jacob Keller <jacob.e.keller@intel.com>, Hui Wang <hui.wang@canonical.com>
References: <202405150942.f9b873b1-oliver.sang@intel.com>
 <23f86436-cd8a-45b0-9378-1ec3adecfc82@molgen.mpg.de>
 <7ef3669807799a83aa40e94e2bdd21a11dbe393b.camel@intel.com>
Content-Language: en-US
From: Paul Menzel <pmenzel@molgen.mpg.de>
In-Reply-To: <7ef3669807799a83aa40e94e2bdd21a11dbe393b.camel@intel.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Dear Rui,


Thank you for your quick reply.


Am 15.05.24 um 11:29 schrieb Zhang, Rui:

> On Wed, 2024-05-15 at 06:57 +0200, Paul Menzel wrote:
>>
>> Can you please share on what test system this fails, and provide the
>> hardware information?
> 
> This is an Intel BroadWell NUC.
> The problem is reproduced on this platform only, we have 20+ other
> platforms but doesn't see this issue.
> 
> lspci output attached, any other info needed?

The `-nn` to show PCI vendor and device codes also as numbers would be nice.

>> Also, do you have Linux logs until starting the tests?
>
> dmesg after boot attached.
> After that I run "rtcwake -m freeze -s 30" and system freezes.

Just as a heads-up, that the referenced commit also caused regression on 
another system [1]. Would you be able to test that patch?


Kind regards,

Paul


[1]: 
https://lore.kernel.org/intel-wired-lan/20240413092743.1548310-1-hui.wang@canonical.com/