Re: kern/53945: -current wm WOL regression

[Masanobu SAITOH <msaitoh%execsw.org@localhost>]

On 2019/02/04 23:45, kardel%netbsd.org@localhost wrote:
> > Number:         53945
> > Category:       kern
> > Synopsis:       -current wm WOL for I211 ceased working
> > Confidential:   no
> > Severity:       serious
> > Priority:       high
> > Responsible:    kern-bug-people
> > State:          open
> > Class:          sw-bug
> > Submitter-Id:   net
> > Arrival-Date:   Mon Feb 04 14:45:00 +0000 2019
> > Originator:     Frank Kardel
> > Release:        NetBSD 8.99.34
> > Organization:
> 	
> > Environment:
> 	
> 	
> System: NetBSD pip.kardel.name 8.99.34 NetBSD 8.99.34 (GENERIC) #2: Sun Feb 3 13:31:03 CET 2019 kardel%pip.kardel.name@localhost:/src/NetBSD/cur/src/obj.amd64/sys/arch/amd64/compile/GENERIC amd64
> Architecture: x86_64
> Machine: amd64
> > Description:
> 	Somewhere between
>          $NetBSD: if_wm.c,v 1.601 2018/11/22 15:09:46 msaitoh Exp $
> 	and
>          $NetBSD: if_wm.c,v 1.620 2019/01/25 08:04:07 msaitoh Exp $
>          WOL functionality for I211 stopped working.
> 	dmesg for 8.99.26
> 		wm0: for TX and RX interrupting at msix3 vec 0 affinity to 1
> 		wm0: for TX and RX interrupting at msix3 vec 1 affinity to 2
> 		wm0: for LINK interrupting at msix3 vec 2
> 		wm0: PCI-Express bus
> 		wm0: 64 words iNVM, version 0.4
> 		wm0: Ethernet address xx:xx:xx:xx:xx:xx
> 		wm0: Copper
> works		wm0: 0xc214420<INVM,IOH_VALID,PCIE,NEWQUEUE,WOL,PLLWA>
> 	dmesg for 8.99.31-34
> 		wm0: for TX and RX interrupting at msix3 vec 0 affinity to 1
> 		wm0: for TX and RX interrupting at msix3 vec 1 affinity to 2
> 		wm0: for LINK interrupting at msix3 vec 2
> 		wm0: PCI-Express bus
> 		wm0: 64 words iNVM, version 0.4
> 		wm0: Ethernet address xx:xx:xx:xx:xx:xx
> 		wm0: Copper
> fails		wm0: 0xc614420<INVM,IOH_VALID,PCIE,NEWQUEUE,WOL,EEE,PLLWA,CLSEMWA>
>
> > How-To-Repeat:
> 	boot a kernel with if_wm.c,v 1.601 and see I211 perform WOL
> 	if_wm.c,v 1.620 and possibly some versions below fail to perform WOL.
> 	the issue still exists with $NetBSD: if_wm.c,v 1.623 2019/01/31 15:30:23 msaitoh Exp $.
>
> > Fix:
> 	n/a
>
> > Unformatted:

 I have only one machine which has I211 (Shuttle DS57U).
When doing "sysctl -w hw.acpi.sleep.state=3", it doesn't enter
S3 but completely do power down... I can't test with this machine...

 I verified that my own ICH8 and PCH2 machine back from suspend, so
not all chips have this problem.

So, please

 0) could you show me the full dmesg?

 1) Is the link LED up or down when the machine is suspended?

 3) Does your machine recover from suspend when power or sleep button
    pressed?

I'll try to test on some other machines.

Thanks in advance.

--
-----------------------------------------------
                SAITOH Masanobu (msaitoh%execsw.org@localhost
                                 msaitoh%netbsd.org@localhost)