On Wed, Aug 9, 2017 at 11:15 PM, Hisashi T Fujinaka <ht...@twofifty.com> wrote:
> On Wed, 9 Aug 2017, Rafael J. Wysocki wrote:
>
>> [You seem to have a stale linux-pm address in your address book,
>> I replaced it with the current one in the CC list.]
>>
>> On Wednesday, August 9, 2017 8:42:31 AM CEST Pavel Machek wrote:
>>>
>>> On Wed 2017-08-09 02:45:54, Rafael J. Wysocki wrote:
>>>>
>>>> On Tuesday, August 8, 2017 11:00:53 AM CEST Pavel Machek wrote:
>>>>>
>>>>> Hi!
>>>>>
>>>>> Perhaps you should get regressi...@kernel.org alias, or something like
>>>>> that?
>>>>>
>>>>>> As always: Are you aware of any other regressions? Then please let me
>>>>>> know. For details see http://bit.ly/lnxregtrackid And please tell me
>>>>>> if
>>>>>> there is anything in the report that shouldn't be there.
>>>>>
>>>>>
>>>>> I am using wake-on-lan quite a bit, and it stopped working. I'll move
>>>>> to -rc4 and test there; but if anyone already has some ideas, let me
>>>>> know.
>>>>>
>>>>> Hardware is thinkpad X220
>>>>>
>>>>> 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network
>>>>> Connection (rev 04)
>>>>
>>>>
>>>> I guess this is ACPI S3 suspend?
>>>
>>>
>>> ACPI S3, right. Machine still wakes up properly when I hit a key on
>>> USB keyboard.
>>
>>
>> OK, so my guess would be a driver issue.  What driver is this, igb?
>>
>>> Does wake on LAN work on you, on any hardware?
>>
>>
>> Yes it does, I checked two machines earlier today, both work.
>>
>> Can you enable dynamic debug in device_pm.c and send a dmesg output
>> with that covering a suspend-resume cycle?
>
>
> 82579 is e1000e

Hmm.  That also is there in my venerable Thoshiba Portege R500 which
wakes on LAN with 4.13-rc4.  So the driver is off the hook I guess.

Reply via email to