linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Debugging spurious wakeup
@ 2015-05-13  6:58 Gianluca Anzolin
  2015-05-13  7:46 ` Zhang, Rui
                   ` (3 more replies)
  0 siblings, 4 replies; 19+ messages in thread
From: Gianluca Anzolin @ 2015-05-13  6:58 UTC (permalink / raw)
  To: linux-acpi

Hello,

I have a curious problem with my system: whenever I wake up the PC with a WOL
magic packet and then power it off the systems comes back to life after a
couple of seconds, by itself.

I can reproduce the problem 100% of the times.

I've been having this problems for years. I remember this same issue occurred
also with my previous computer, with a different mainboard. My current system
has an ASUS P8B-WS mb with a Xeon 1275v2 CPU.

I've ruled out in the time many factors: traffic on the net (by disconnecting
the cable), RTC alarms (by disabling them)... long story short: I'm stuck.

While I'm not the only one with this issue (see[1]), some people have reported
mixed success by blacklisting some components (xhci-pci) or by setting
unrelated BIOS options. Unfortunately these workarounds never worked for me.

So I'm here to ask if there is a way to get the source/cause of the last wakeup
by setting some ACPI debug option. This way I could at least pinpoint the
device/interface that caused the spontaneous wakeup and then debug further or
at least disable it.

I've tried to enable the ACPI hardware-related messages with the kernel
arguments: acpi.debug_layer=0x2 acpi.debug_level=0xffffffff

Unfortunately I can't see the information I'm looking for in the resulting
output. Should I enable some other debug_layer? Could anybody point me in the
right direction?

Thank you and best regards,

Gianluca

[1] https://bbs.archlinux.org/viewtopic.php?id=173648

^ permalink raw reply	[flat|nested] 19+ messages in thread

* RE: Debugging spurious wakeup
  2015-05-13  6:58 Debugging spurious wakeup Gianluca Anzolin
@ 2015-05-13  7:46 ` Zhang, Rui
  2015-05-13  8:12   ` Gianluca Anzolin
  2015-05-14 12:51 ` Gianluca Anzolin
                   ` (2 subsequent siblings)
  3 siblings, 1 reply; 19+ messages in thread
From: Zhang, Rui @ 2015-05-13  7:46 UTC (permalink / raw)
  To: Gianluca Anzolin, linux-acpi@vger.kernel.org

Please attach the output of "cat /proc/acpi/wakeup".

Thanks,
rui

> -----Original Message-----
> From: linux-acpi-owner@vger.kernel.org [mailto:linux-acpi-
> owner@vger.kernel.org] On Behalf Of Gianluca Anzolin
> Sent: Wednesday, May 13, 2015 2:58 PM
> To: linux-acpi@vger.kernel.org
> Subject: Debugging spurious wakeup
> 
> Hello,
> 
> I have a curious problem with my system: whenever I wake up the PC with a
> WOL magic packet and then power it off the systems comes back to life after
> a couple of seconds, by itself.
> 
> I can reproduce the problem 100% of the times.
> 
> I've been having this problems for years. I remember this same issue
> occurred also with my previous computer, with a different mainboard. My
> current system has an ASUS P8B-WS mb with a Xeon 1275v2 CPU.
> 
> I've ruled out in the time many factors: traffic on the net (by disconnecting
> the cable), RTC alarms (by disabling them)... long story short: I'm stuck.
> 
> While I'm not the only one with this issue (see[1]), some people have
> reported mixed success by blacklisting some components (xhci-pci) or by
> setting unrelated BIOS options. Unfortunately these workarounds never
> worked for me.
> 
> So I'm here to ask if there is a way to get the source/cause of the last wakeup
> by setting some ACPI debug option. This way I could at least pinpoint the
> device/interface that caused the spontaneous wakeup and then debug
> further or at least disable it.
> 
> I've tried to enable the ACPI hardware-related messages with the kernel
> arguments: acpi.debug_layer=0x2 acpi.debug_level=0xffffffff
> 
> Unfortunately I can't see the information I'm looking for in the resulting
> output. Should I enable some other debug_layer? Could anybody point me in
> the right direction?
> 
> Thank you and best regards,
> 
> Gianluca
> 
> [1] https://bbs.archlinux.org/viewtopic.php?id=173648
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the
> body of a message to majordomo@vger.kernel.org More majordomo info at
> http://vger.kernel.org/majordomo-info.html

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Debugging spurious wakeup
  2015-05-13  7:46 ` Zhang, Rui
@ 2015-05-13  8:12   ` Gianluca Anzolin
  2015-05-13  8:13     ` Zhang, Rui
  0 siblings, 1 reply; 19+ messages in thread
From: Gianluca Anzolin @ 2015-05-13  8:12 UTC (permalink / raw)
  To: Zhang, Rui; +Cc: linux-acpi@vger.kernel.org

[-- Attachment #1: Type: text/plain, Size: 172 bytes --]

On Wed, May 13, 2015 at 07:46:09AM +0000, Zhang, Rui wrote:
> Please attach the output of "cat /proc/acpi/wakeup".
> 
> Thanks,
> rui

File attached.

Thank you,

Gianluca

[-- Attachment #2: wakeup.txt --]
[-- Type: text/plain, Size: 884 bytes --]

Device	S-state	  Status   Sysfs node
PS2K	  S4	*disabled
PS2M	  S4	*disabled
UAR1	  S4	*disabled  pnp:00:06
P0P1	  S4	*disabled  pci:0000:00:1e.0
RP01	  S4	*disabled  pci:0000:00:1c.0
PXSX	  S4	*disabled
RP02	  S4	*disabled
PXSX	  S4	*disabled
RP03	  S4	*disabled
PXSX	  S4	*disabled
RP04	  S4	*disabled
PXSX	  S4	*disabled
RP05	  S4	*disabled
PXSX	  S4	*disabled
RP06	  S4	*disabled  pci:0000:00:1c.5
PXSX	  S4	*enabled   pci:0000:04:00.0
RP08	  S4	*disabled  pci:0000:00:1c.7
PXSX	  S4	*enabled   pci:0000:06:00.0
PEG0	  S4	*disabled  pci:0000:00:01.0
PEGP	  S4	*disabled
PEG1	  S4	*disabled
PEG2	  S4	*disabled
PEG3	  S4	*disabled  pci:0000:00:06.0
RP07	  S4	*disabled  pci:0000:00:1c.6
GLAN	  S4	*disabled
EHC1	  S4	*enabled   pci:0000:00:1d.0
EHC2	  S4	*disabled  pci:0000:00:1a.0
XHC	  S4	*disabled
HDEF	  S4	*disabled  pci:0000:00:1b.0
PWRB	  S4	*enabled   platform:PNP0C0C:00

^ permalink raw reply	[flat|nested] 19+ messages in thread

* RE: Debugging spurious wakeup
  2015-05-13  8:12   ` Gianluca Anzolin
@ 2015-05-13  8:13     ` Zhang, Rui
  2015-05-13  8:26       ` Gianluca Anzolin
  0 siblings, 1 reply; 19+ messages in thread
From: Zhang, Rui @ 2015-05-13  8:13 UTC (permalink / raw)
  To: Gianluca Anzolin; +Cc: linux-acpi@vger.kernel.org

Hmm, none of them seems to be NIC related, can you please attach the output of lspci -vvxx as well?

> -----Original Message-----
> From: Gianluca Anzolin [mailto:gianluca@sottospazio.it]
> Sent: Wednesday, May 13, 2015 4:12 PM
> To: Zhang, Rui
> Cc: linux-acpi@vger.kernel.org
> Subject: Re: Debugging spurious wakeup
> Importance: High
> 
> On Wed, May 13, 2015 at 07:46:09AM +0000, Zhang, Rui wrote:
> > Please attach the output of "cat /proc/acpi/wakeup".
> >
> > Thanks,
> > rui
> 
> File attached.
> 
> Thank you,
> 
> Gianluca

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Debugging spurious wakeup
  2015-05-13  8:13     ` Zhang, Rui
@ 2015-05-13  8:26       ` Gianluca Anzolin
  2015-05-13  8:30         ` Zhang, Rui
  0 siblings, 1 reply; 19+ messages in thread
From: Gianluca Anzolin @ 2015-05-13  8:26 UTC (permalink / raw)
  To: Zhang, Rui; +Cc: linux-acpi@vger.kernel.org

[-- Attachment #1: Type: text/plain, Size: 223 bytes --]

On Wed, May 13, 2015 at 08:13:46AM +0000, Zhang, Rui wrote:
> Hmm, none of them seems to be NIC related, can you please attach the output of lspci -vvxx as well?
> 

file attached (with I blanked the mac address)

Gianluca

[-- Attachment #2: lspci.txt --]
[-- Type: text/plain, Size: 56610 bytes --]

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 Processor Family DRAM Controller (rev 09)
	Subsystem: ASUSTeK Computer Inc. Device 844d
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
	Latency: 0
	Capabilities: [e0] Vendor Specific Information: Len=0c <?>
00: 86 80 08 01 06 00 90 20 09 00 00 06 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 4d 84
30: 00 00 00 00 e0 00 00 00 00 00 00 00 00 00 00 00
40: 01 90 d1 fe 00 00 00 00 01 00 d1 fe 00 00 00 00
50: 03 00 00 00 09 20 00 00 00 00 00 00 01 00 80 df
60: 05 00 00 f8 00 00 00 00 01 80 d1 fe 00 00 00 00
70: 00 00 00 ff 03 00 00 00 00 0c 00 ff 7f 00 00 00
80: 10 11 11 00 00 00 11 00 1a 00 00 00 00 00 00 00
90: 01 00 00 ff 03 00 00 00 01 00 f0 1e 04 00 00 00
a0: 01 00 00 00 04 00 00 00 01 00 00 1f 04 00 00 00
b0: 01 00 00 e0 01 00 00 e0 01 00 80 df 01 00 00 e0
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 09 00 0c 01 96 a2 00 60 90 00 00 16 00 00 00 00
f0: 00 00 00 00 00 00 00 00 b8 0f 06 00 00 00 00 00

00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 25
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: 0000e000-0000efff
	Memory behind bridge: f4000000-f60fffff
	Prefetchable memory behind bridge: 00000000e8000000-00000000f3ffffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [88] Subsystem: ASUSTeK Computer Inc. Device 844d
	Capabilities: [80] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
		Address: fee002d8  Data: 0000
	Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0
			ExtTag- RBE+
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
		LnkCap:	Port #2, Speed 5GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <256ns, L1 <4us
			ClockPM- Surprise- LLActRep- BwNot+ ASPMOptComp-
		LnkCtl:	ASPM Disabled; RCB 64 bytes Disabled- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt+ ABWMgmt-
		SltCap:	AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise-
			Slot #1, PowerLimit 75.000W; Interlock- NoCompl+
		SltCtl:	Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
			Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
		SltSta:	Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock-
			Changed: MRL- PresDet- LinkState-
		RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible-
		RootCap: CRSVisible-
		RootSta: PME ReqID 0000, PMEStatus- PMEPending-
		DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, OBFF Not Supported ARIFwd-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled ARIFwd-
		LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
			 EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
	Capabilities: [100 v1] Virtual Channel
		Caps:	LPEVC=0 RefClk=100ns PATEntryBits=1
		Arb:	Fixed- WRR32- WRR64- WRR128-
		Ctrl:	ArbSelect=Fixed
		Status:	InProgress-
		VC0:	Caps:	PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
			Arb:	Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256-
			Ctrl:	Enable+ ID=0 ArbSelect=Fixed TC/VC=01
			Status:	NegoPending- InProgress-
	Capabilities: [140 v1] Root Complex Link
		Desc:	PortNumber=02 ComponentID=01 EltType=Config
		Link0:	Desc:	TargetPort=00 TargetComponent=01 AssocRCRB- LinkType=MemMapped LinkValid+
			Addr:	00000000fed19000
	Kernel driver in use: pcieport
00: 86 80 01 01 07 04 10 00 09 00 04 06 10 00 81 00
10: 00 00 00 00 00 00 00 00 00 01 01 00 e0 e0 00 20
20: 00 f4 00 f6 01 e8 f1 f3 00 00 00 00 00 00 00 00
30: 00 00 00 00 88 00 00 00 00 00 00 00 0b 01 18 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0a
80: 01 90 03 c8 08 00 00 00 0d 80 00 00 43 10 4d 84
90: 05 a0 01 00 d8 02 e0 fe 00 00 00 00 00 00 00 00
a0: 10 00 42 01 00 80 00 00 00 00 00 00 02 2d 21 02
b0: 40 00 01 51 80 25 0c 00 00 00 40 00 00 00 00 00
c0: 00 00 00 00 00 08 00 00 00 00 00 00 00 00 00 00
d0: 42 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 01 00 00 00 00 00 00 00 10 00

00:06.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 26
	Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [88] Subsystem: ASUSTeK Computer Inc. Device 844d
	Capabilities: [80] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
		Address: fee002f8  Data: 0000
	Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0
			ExtTag- RBE+
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
		LnkCap:	Port #5, Speed 5GT/s, Width x4, ASPM L0s L1, Exit Latency L0s <1us, L1 <4us
			ClockPM- Surprise- LLActRep- BwNot+ ASPMOptComp-
		LnkCtl:	ASPM Disabled; RCB 64 bytes Disabled- CommClk-
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x0, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		SltCap:	AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise-
			Slot #4, PowerLimit 75.000W; Interlock- NoCompl+
		SltCtl:	Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
			Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
		SltSta:	Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- Interlock-
			Changed: MRL- PresDet- LinkState-
		RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible-
		RootCap: CRSVisible-
		RootSta: PME ReqID 0000, PMEStatus- PMEPending-
		DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, OBFF Not Supported ARIFwd-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled ARIFwd-
		LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
			 EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
	Capabilities: [100 v1] Virtual Channel
		Caps:	LPEVC=0 RefClk=100ns PATEntryBits=1
		Arb:	Fixed- WRR32- WRR64- WRR128-
		Ctrl:	ArbSelect=Fixed
		Status:	InProgress-
		VC0:	Caps:	PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
			Arb:	Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256-
			Ctrl:	Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
			Status:	NegoPending+ InProgress-
	Capabilities: [140 v1] Root Complex Link
		Desc:	PortNumber=05 ComponentID=01 EltType=Config
		Link0:	Desc:	TargetPort=00 TargetComponent=01 AssocRCRB- LinkType=MemMapped LinkValid+
			Addr:	00000000fed19000
	Kernel driver in use: pcieport
00: 86 80 0d 01 07 04 10 00 09 00 04 06 10 00 01 00
10: 00 00 00 00 00 00 00 00 00 02 02 00 f0 00 00 00
20: f0 ff 00 00 f1 ff 01 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 88 00 00 00 00 00 00 00 05 01 10 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0a
80: 01 90 03 c8 08 00 00 00 0d 80 00 00 43 10 4d 84
90: 05 a0 01 00 f8 02 e0 fe 00 00 00 00 00 00 00 00
a0: 10 00 42 01 00 80 00 00 00 00 00 00 42 4c 21 05
b0: 00 00 01 10 80 25 24 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 08 00 00 00 00 00 00 00 00 00 00
d0: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 01 00 00 00 00 00 00 00 10 00

00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
	Subsystem: ASUSTeK Computer Inc. P8 series motherboard
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at f650b000 (64-bit, non-prefetchable) [size=16]
	Capabilities: [50] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [8c] MSI: Enable- Count=1/1 Maskable- 64bit+
		Address: 0000000000000000  Data: 0000
00: 86 80 3a 1c 06 00 10 00 04 00 80 07 00 00 80 00
10: 04 b0 50 f6 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 4d 84
30: 00 00 00 00 50 00 00 00 00 00 00 00 0b 01 00 00
40: 55 02 00 1e 10 00 01 80 06 01 00 60 f0 3f 00 10
50: 01 8c 03 c8 08 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 05 00 80 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 c0
c0: b1 67 f8 fc a5 c9 99 25 e6 1e 66 9e c2 a9 0f c2
d0: 0a 9e 5b 2b 17 b2 3b 51 9b c4 ce 91 e5 0c 57 33
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) (prog-if 20 [EHCI])
	Subsystem: ASUSTeK Computer Inc. P8 series motherboard
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at f6508000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [58] Debug port: BAR=1 offset=00a0
	Capabilities: [98] PCI Advanced Features
		AFCap: TP+ FLR+
		AFCtrl: FLR-
		AFStatus: TP-
	Kernel driver in use: ehci-pci
	Kernel modules: ehci_pci
00: 86 80 2d 1c 06 00 90 02 05 20 03 0c 00 00 00 00
10: 00 80 50 f6 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 4d 84
30: 00 00 00 00 50 00 00 00 00 00 00 00 0b 01 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 01 58 c2 c9 00 00 00 00 0a 98 a0 20 00 00 00 00
60: 20 20 ff 07 00 00 00 00 01 00 00 01 00 00 00 40
70: 00 00 df 3f 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 80 00 11 88 0c 93 30 0d 00 24 00 00 00 00
90: 00 00 00 00 00 00 00 00 13 00 06 03 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 aa ff 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 04 00 28 40 01 00 00 00 04 f0 ff ff
f0: 00 00 00 00 88 85 80 00 87 0f 05 08 08 17 5b 20

00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
	Subsystem: ASUSTeK Computer Inc. Device 8469
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 36
	Region 0: Memory at f6500000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
		Address: 00000000fee003b8  Data: 0000
	Capabilities: [70] Express (v1) Root Complex Integrated Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0
			ExtTag- RBE-
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
	Capabilities: [100 v1] Virtual Channel
		Caps:	LPEVC=0 RefClk=100ns PATEntryBits=1
		Arb:	Fixed- WRR32- WRR64- WRR128-
		Ctrl:	ArbSelect=Fixed
		Status:	InProgress-
		VC0:	Caps:	PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
			Arb:	Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
			Ctrl:	Enable+ ID=0 ArbSelect=Fixed TC/VC=01
			Status:	NegoPending- InProgress-
		VC1:	Caps:	PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
			Arb:	Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
			Ctrl:	Enable+ ID=2 ArbSelect=Fixed TC/VC=44
			Status:	NegoPending- InProgress-
	Capabilities: [130 v1] Root Complex Link
		Desc:	PortNumber=0f ComponentID=00 EltType=Config
		Link0:	Desc:	TargetPort=00 TargetComponent=00 AssocRCRB- LinkType=MemMapped LinkValid+
			Addr:	00000000fed1c000
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
00: 86 80 20 1c 06 04 10 00 05 00 03 04 10 00 00 00
10: 04 00 50 f6 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 69 84
30: 00 00 00 00 50 00 00 00 00 00 00 00 03 01 00 00
40: 01 00 00 05 00 00 00 00 00 00 00 00 00 00 00 00
50: 01 60 42 c8 00 00 00 00 00 00 00 00 00 00 00 00
60: 05 70 81 00 b8 03 e0 fe 00 00 00 00 00 00 00 00
70: 10 00 91 00 00 00 00 10 00 00 10 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 04 02 01 00 24 00 40 00 0c a3 82 10 00 33 02
d0: 00 0c a3 02 10 00 33 02 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 87 0f 05 08 00 00 00 00

00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 16
	Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
	I/O behind bridge: 00002000-00002fff
	Memory behind bridge: e0100000-e02fffff
	Prefetchable memory behind bridge: 00000000e0300000-00000000e04fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0
			ExtTag- RBE+
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
		LnkCap:	Port #1, Speed 5GT/s, Width x4, ASPM L0s L1, Exit Latency L0s <1us, L1 <4us
			ClockPM- Surprise- LLActRep+ BwNot- ASPMOptComp-
		LnkCtl:	ASPM Disabled; RCB 64 bytes Disabled- CommClk-
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x0, TrErr- Train+ SlotClk+ DLActive- BWMgmt- ABWMgmt-
		SltCap:	AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+
			Slot #0, PowerLimit 0.000W; Interlock- NoCompl+
		SltCtl:	Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
			Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
		SltSta:	Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- Interlock-
			Changed: MRL- PresDet- LinkState-
		RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible-
		RootCap: CRSVisible-
		RootSta: PME ReqID 0000, PMEStatus- PMEPending-
		DevCap2: Completion Timeout: Range BC, TimeoutDis+, LTR-, OBFF Not Supported ARIFwd-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled ARIFwd-
		LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1-
			 EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
	Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
		Address: 00000000  Data: 0000
	Capabilities: [90] Subsystem: ASUSTeK Computer Inc. P8 series motherboard
	Capabilities: [a0] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: pcieport
00: 86 80 10 1c 07 00 10 00 b5 00 04 06 10 00 81 00
10: 00 00 00 00 00 00 00 00 00 03 03 00 20 20 00 20
20: 10 e0 20 e0 31 e0 41 e0 00 00 00 00 00 00 00 00
30: 00 00 00 00 40 00 00 00 00 00 00 00 0b 01 10 00
40: 10 80 42 01 00 80 00 00 00 00 10 00 42 4c 11 01
50: 00 00 01 18 60 00 04 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 16 00 00 00 00 00 00 00 00 00 00 00
70: 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 05 90 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 0d a0 00 00 43 10 4d 84 00 00 00 00 00 00 00 00
a0: 01 00 02 c8 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 01 02 0b 00 00 02 00 11 01 00 00 00 00
e0: 00 3f 00 00 00 00 00 00 01 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 87 0f 05 08 00 00 00 00

00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin B routed to IRQ 17
	Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
	I/O behind bridge: 0000d000-0000dfff
	Memory behind bridge: f6400000-f64fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0
			ExtTag- RBE+
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
		LnkCap:	Port #6, Speed 5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <512ns, L1 <4us
			ClockPM- Surprise- LLActRep+ BwNot- ASPMOptComp-
		LnkCtl:	ASPM Disabled; RCB 64 bytes Disabled- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ BWMgmt+ ABWMgmt-
		SltCap:	AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise-
			Slot #5, PowerLimit 10.000W; Interlock- NoCompl+
		SltCtl:	Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
			Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
		SltSta:	Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock-
			Changed: MRL- PresDet- LinkState-
		RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible-
		RootCap: CRSVisible-
		RootSta: PME ReqID 0400, PMEStatus- PMEPending-
		DevCap2: Completion Timeout: Range BC, TimeoutDis+, LTR-, OBFF Not Supported ARIFwd-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled ARIFwd-
		LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1-
			 EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
	Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
		Address: 00000000  Data: 0000
	Capabilities: [90] Subsystem: ASUSTeK Computer Inc. P8 series motherboard
	Capabilities: [a0] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: pcieport
00: 86 80 1a 1c 07 00 10 00 b5 00 04 06 10 00 81 00
10: 00 00 00 00 00 00 00 00 00 04 04 00 d0 d0 00 20
20: 40 f6 40 f6 f1 ff 01 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 40 00 00 00 00 00 00 00 0a 02 10 00
40: 10 80 42 01 00 80 00 00 00 00 10 00 12 3c 11 06
50: 40 00 11 70 00 b2 2c 00 00 00 40 00 00 00 00 00
60: 00 04 03 00 16 00 00 00 00 00 00 00 00 00 00 00
70: 02 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 05 90 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 0d a0 00 00 43 10 4d 84 00 00 00 00 00 00 00 00
a0: 01 00 02 c8 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 01 02 0b 00 00 00 80 11 81 00 00 00 80
e0: 00 03 00 00 00 00 00 00 01 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 87 0f 05 08 00 00 00 00

00:1c.6 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 7 (rev b5) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin C routed to IRQ 18
	Bus: primary=00, secondary=05, subordinate=05, sec-latency=0
	I/O behind bridge: 0000c000-0000cfff
	Memory behind bridge: f6300000-f63fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0
			ExtTag- RBE+
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
		LnkCap:	Port #7, Speed 5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <512ns, L1 <4us
			ClockPM- Surprise- LLActRep+ BwNot- ASPMOptComp-
		LnkCtl:	ASPM Disabled; RCB 64 bytes Disabled- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ BWMgmt+ ABWMgmt-
		SltCap:	AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise-
			Slot #6, PowerLimit 10.000W; Interlock- NoCompl+
		SltCtl:	Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
			Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
		SltSta:	Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock-
			Changed: MRL- PresDet- LinkState-
		RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible-
		RootCap: CRSVisible-
		RootSta: PME ReqID 0000, PMEStatus- PMEPending-
		DevCap2: Completion Timeout: Range BC, TimeoutDis+, LTR-, OBFF Not Supported ARIFwd-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled ARIFwd-
		LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1-
			 EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
	Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
		Address: 00000000  Data: 0000
	Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Device 844d
	Capabilities: [a0] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: pcieport
00: 86 80 1c 1c 07 00 10 00 b5 00 04 06 10 00 81 00
10: 00 00 00 00 00 00 00 00 00 05 05 00 c0 c0 00 20
20: 30 f6 30 f6 f1 ff 01 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 40 00 00 00 00 00 00 00 0b 03 10 00
40: 10 80 42 01 00 80 00 00 00 00 10 00 12 3c 11 07
50: 40 00 11 70 00 b2 34 00 00 00 40 00 00 00 00 00
60: 00 00 00 00 16 00 00 00 00 00 00 00 00 00 00 00
70: 02 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 05 90 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 0d a0 00 00 43 10 4d 84 00 00 00 00 00 00 00 00
a0: 01 00 02 c8 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 01 02 0b 00 00 00 80 11 81 00 00 00 00
e0: 00 03 00 00 00 00 00 00 01 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 87 0f 05 08 00 00 00 00

00:1c.7 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 8 (rev b5) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin D routed to IRQ 19
	Bus: primary=00, secondary=06, subordinate=06, sec-latency=0
	Memory behind bridge: f6200000-f62fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0
			ExtTag- RBE+
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
		LnkCap:	Port #8, Speed 5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <512ns, L1 <4us
			ClockPM- Surprise- LLActRep+ BwNot- ASPMOptComp-
		LnkCtl:	ASPM Disabled; RCB 64 bytes Disabled- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ BWMgmt+ ABWMgmt-
		SltCap:	AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise-
			Slot #7, PowerLimit 10.000W; Interlock- NoCompl+
		SltCtl:	Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
			Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
		SltSta:	Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock-
			Changed: MRL- PresDet- LinkState-
		RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible-
		RootCap: CRSVisible-
		RootSta: PME ReqID 0000, PMEStatus- PMEPending-
		DevCap2: Completion Timeout: Range BC, TimeoutDis+, LTR-, OBFF Not Supported ARIFwd-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled ARIFwd-
		LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
			 EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
	Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
		Address: 00000000  Data: 0000
	Capabilities: [90] Subsystem: ASUSTeK Computer Inc. P8 series motherboard
	Capabilities: [a0] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: pcieport
00: 86 80 1e 1c 07 00 10 00 b5 00 04 06 10 00 81 00
10: 00 00 00 00 00 00 00 00 00 06 06 00 f0 00 00 20
20: 20 f6 20 f6 f1 ff 01 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 40 00 00 00 00 00 00 00 05 04 10 00
40: 10 80 42 01 00 80 00 00 00 00 10 00 12 3c 11 08
50: 40 00 12 70 00 b2 3c 00 00 00 40 00 00 00 00 00
60: 00 00 00 00 16 00 00 00 00 00 00 00 00 00 00 00
70: 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 05 90 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 0d a0 00 00 43 10 4d 84 00 00 00 00 00 00 00 00
a0: 01 00 02 c8 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 01 02 0b 00 00 00 80 11 81 00 00 00 00
e0: 00 03 00 00 00 00 00 00 01 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 87 0f 05 08 00 00 00 00

00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) (prog-if 20 [EHCI])
	Subsystem: ASUSTeK Computer Inc. P8 series motherboard
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 23
	Region 0: Memory at f6507000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [58] Debug port: BAR=1 offset=00a0
	Capabilities: [98] PCI Advanced Features
		AFCap: TP+ FLR+
		AFCtrl: FLR-
		AFStatus: TP-
	Kernel driver in use: ehci-pci
	Kernel modules: ehci_pci
00: 86 80 26 1c 06 00 90 02 05 20 03 0c 00 00 00 00
10: 00 70 50 f6 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 4d 84
30: 00 00 00 00 50 00 00 00 00 00 00 00 0a 01 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 01 58 c2 c9 00 00 00 00 0a 98 a0 20 00 00 00 00
60: 20 20 ff 07 00 00 00 00 01 00 00 01 00 00 08 40
70: 00 00 df 3f 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 80 00 11 88 0c 93 30 0d 00 24 00 00 00 00
90: 00 00 00 00 00 00 00 00 13 00 06 03 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 aa ff 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 04 f0 ff ff
f0: 00 00 00 00 88 85 80 00 87 0f 05 08 08 17 5b 20

00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a5) (prog-if 01 [Subtractive decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Bus: primary=00, secondary=07, subordinate=07, sec-latency=32
	I/O behind bridge: 0000b000-0000bfff
	Memory behind bridge: f6100000-f61fffff
	Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [50] Subsystem: ASUSTeK Computer Inc. P8 series motherboard
00: 86 80 4e 24 07 00 10 00 a5 01 04 06 00 00 01 00
10: 00 00 00 00 00 00 00 00 00 07 07 20 b0 b0 80 22
20: 10 f6 10 f6 f1 ff 01 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 00 10 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 12 00 10
50: 0d 00 00 00 43 10 4d 84 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 87 0f 05 08 00 00 00 00

00:1f.0 ISA bridge: Intel Corporation C206 Chipset Family LPC Controller (rev 05)
	Subsystem: ASUSTeK Computer Inc. P8B WS Motherboard
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Capabilities: [e0] Vendor Specific Information: Len=0c <?>
	Kernel driver in use: lpc_ich
00: 86 80 56 1c 07 00 10 02 05 00 01 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 4d 84
30: 00 00 00 00 e0 00 00 00 00 00 00 00 00 00 00 00
40: 01 04 00 00 80 00 00 00 01 05 00 00 10 00 00 00
50: f8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 8b 8a 8b 85 d0 00 00 00 80 80 83 8a f8 f0 00 00
70: 78 f0 78 f0 78 f0 78 f0 78 f0 78 f0 78 f0 78 f0
80: 10 00 01 3c 91 02 0c 00 01 0a fc 00 00 00 00 00
90: 00 00 00 00 00 0f 00 00 00 00 00 00 00 00 00 00
a0: 08 0e 80 00 49 18 06 00 00 47 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 10 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 33 22 11 00 67 45 00 00 cf ff 00 00 08 00 00 00
e0: 09 00 0c 10 00 00 00 00 91 02 64 0c 00 00 00 00
f0: 01 c0 d1 fe 00 00 00 00 87 0f 05 08 00 00 00 00

00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05) (prog-if 01 [AHCI 1.0])
	Subsystem: ASUSTeK Computer Inc. P8 series motherboard
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin B routed to IRQ 27
	Region 0: I/O ports at f070 [size=8]
	Region 1: I/O ports at f060 [size=4]
	Region 2: I/O ports at f050 [size=8]
	Region 3: I/O ports at f040 [size=4]
	Region 4: I/O ports at f020 [size=32]
	Region 5: Memory at f6506000 (32-bit, non-prefetchable) [size=2K]
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
		Address: fee00358  Data: 0000
	Capabilities: [70] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [a8] SATA HBA v1.0 BAR4 Offset=00000004
	Capabilities: [b0] PCI Advanced Features
		AFCap: TP+ FLR+
		AFCtrl: FLR-
		AFStatus: TP-
	Kernel driver in use: ahci
	Kernel modules: ahci
00: 86 80 02 1c 07 04 b0 02 05 01 06 01 00 00 00 00
10: 71 f0 00 00 61 f0 00 00 51 f0 00 00 41 f0 00 00
20: 21 f0 00 00 00 60 50 f6 00 00 00 00 43 10 4d 84
30: 00 00 00 00 80 00 00 00 00 00 00 00 05 02 00 00
40: 00 80 00 80 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 01 a8 03 40 08 00 00 00 00 00 00 00 00 00 00 00
80: 05 70 01 00 58 03 e0 fe 00 00 00 00 00 00 00 00
90: 60 08 37 93 83 01 00 08 08 42 1c 01 00 00 00 00
a0: e0 00 00 00 39 00 39 00 12 b0 10 00 48 00 00 00
b0: 13 00 06 03 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 87 0f 05 08 00 00 00 00

00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
	Subsystem: ASUSTeK Computer Inc. P8 series motherboard
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin C routed to IRQ 18
	Region 0: Memory at f6505000 (64-bit, non-prefetchable) [size=256]
	Region 4: I/O ports at f000 [size=32]
	Kernel modules: i2c_i801
00: 86 80 22 1c 03 00 80 02 05 00 05 0c 00 00 00 00
10: 04 50 50 f6 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 f0 00 00 00 00 00 00 00 00 00 00 43 10 4d 84
30: 00 00 00 00 00 00 00 00 00 00 00 00 0b 03 00 00
40: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 03 04 04 00 00 00 08 08 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 87 0f 05 08 00 00 00 00

01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560] (rev a1) (prog-if 00 [VGA controller])
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 2326
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 44
	Region 0: Memory at f4000000 (32-bit, non-prefetchable) [size=32M]
	Region 1: Memory at e8000000 (64-bit, prefetchable) [size=128M]
	Region 3: Memory at f0000000 (64-bit, prefetchable) [size=64M]
	Region 5: I/O ports at e000 [size=128]
	[virtual] Expansion ROM at f6000000 [disabled] [size=512K]
	Capabilities: [60] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+
		Address: 00000000fee003f8  Data: 0000
	Capabilities: [78] Express (v2) Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 <64us
			ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
			MaxPayload 128 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
		LnkCap:	Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <256ns, L1 <4us
			ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp-
		LnkCtl:	ASPM Disabled; RCB 64 bytes Disabled- CommClk+
			ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Not Supported, TimeoutDis+, LTR-, OBFF Not Supported
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
		LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
			 EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
	Capabilities: [b4] Vendor Specific Information: Len=14 <?>
	Capabilities: [100 v1] Virtual Channel
		Caps:	LPEVC=0 RefClk=100ns PATEntryBits=1
		Arb:	Fixed- WRR32- WRR64- WRR128-
		Ctrl:	ArbSelect=Fixed
		Status:	InProgress-
		VC0:	Caps:	PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
			Arb:	Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
			Ctrl:	Enable+ ID=0 ArbSelect=Fixed TC/VC=01
			Status:	NegoPending- InProgress-
	Capabilities: [128 v1] Power Budgeting <?>
	Capabilities: [600 v1] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?>
	Kernel driver in use: nvidia
	Kernel modules: nvidia
00: de 10 01 12 07 00 10 00 a1 00 00 03 00 00 80 00
10: 00 00 00 f4 0c 00 00 e8 00 00 00 00 0c 00 00 f0
20: 00 00 00 00 01 e0 00 00 00 00 00 00 62 14 26 23
30: 00 00 00 00 60 00 00 00 00 00 00 00 0b 01 00 00
40: 62 14 26 23 00 00 00 00 00 00 00 00 00 00 00 00
50: 01 00 00 00 01 00 00 00 ce d6 23 00 00 00 00 00
60: 01 68 03 00 08 00 00 00 05 78 81 00 f8 03 e0 fe
70: 00 00 00 00 00 00 00 00 10 b4 02 00 a0 8d 2c 01
80: 10 29 00 00 01 2d 05 00 40 01 01 11 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 10 00 00 00
a0: 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00
b0: 00 00 00 00 09 00 14 01 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

01:00.1 Audio device: NVIDIA Corporation GF114 HDMI Audio Controller (rev a1)
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 2326
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin B routed to IRQ 40
	Region 0: Memory at f6080000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: [60] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+
		Address: 00000000fee003d8  Data: 0000
	Capabilities: [78] Express (v2) Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 <64us
			ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
			MaxPayload 128 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
		LnkCap:	Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <256ns, L1 <4us
			ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp-
		LnkCtl:	ASPM Disabled; RCB 128 bytes Disabled- CommClk+
			ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Not Supported, TimeoutDis+, LTR-, OBFF Not Supported
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
		LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
			 EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
00: de 10 0c 0e 06 04 10 00 a1 00 03 04 10 00 80 00
10: 00 00 08 f6 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 62 14 26 23
30: 00 00 00 00 60 00 00 00 00 00 00 00 0a 02 00 00
40: 62 14 26 23 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 ce d6 23 00 00 00 00 00
60: 01 68 03 00 08 00 00 00 05 78 81 00 d8 03 e0 fe
70: 00 00 00 00 00 00 00 00 10 00 02 00 a0 8d 2c 01
80: 00 28 00 00 01 2d 05 00 48 01 01 11 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 10 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

04:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
	Subsystem: ASUSTeK Computer Inc. Motherboard
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 17
	Region 0: Memory at f6400000 (32-bit, non-prefetchable) [size=128K]
	Region 2: I/O ports at d000 [size=32]
	Region 3: Memory at f6420000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: [c8] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
	Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
		Address: 0000000000000000  Data: 0000
	Capabilities: [e0] Express (v1) Endpoint, MSI 00
		DevCap:	MaxPayload 256 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us
			ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
		DevCtl:	Report errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
			MaxPayload 128 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
		LnkCap:	Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <128ns, L1 <64us
			ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp-
		LnkCtl:	ASPM Disabled; RCB 64 bytes Disabled- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
	Capabilities: [a0] MSI-X: Enable+ Count=5 Masked-
		Vector table: BAR=3 offset=00000000
		PBA: BAR=3 offset=00002000
	Capabilities: [100 v1] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
		AERCap:	First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn-
	Capabilities: [140 v1] Device Serial Number <BLANKED>
	Kernel driver in use: e1000e
	Kernel modules: e1000e
00: 86 80 d3 10 07 04 10 00 00 00 00 02 10 00 00 00
10: 00 00 40 f6 00 00 00 00 01 d0 00 00 00 00 42 f6
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 69 83
30: 00 00 00 00 c8 00 00 00 00 00 00 00 0a 01 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 11 00 04 80 03 00 00 00 03 20 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 01 d0 22 c8 00 20 00 0f
d0: 05 e0 80 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 10 a0 01 00 c1 8c 00 00 0f 28 19 00 11 1c 03 00
f0: 40 00 11 10 00 00 00 00 00 00 00 00 00 00 00 00

05:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
	Subsystem: ASUSTeK Computer Inc. Motherboard
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 18
	Region 0: Memory at f6300000 (32-bit, non-prefetchable) [size=128K]
	Region 2: I/O ports at c000 [size=32]
	Region 3: Memory at f6320000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: [c8] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
	Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
		Address: 0000000000000000  Data: 0000
	Capabilities: [e0] Express (v1) Endpoint, MSI 00
		DevCap:	MaxPayload 256 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us
			ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
		DevCtl:	Report errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
			MaxPayload 128 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
		LnkCap:	Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <128ns, L1 <64us
			ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp-
		LnkCtl:	ASPM Disabled; RCB 64 bytes Disabled- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
	Capabilities: [a0] MSI-X: Enable+ Count=5 Masked-
		Vector table: BAR=3 offset=00000000
		PBA: BAR=3 offset=00002000
	Capabilities: [100 v1] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
		AERCap:	First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn-
	Capabilities: [140 v1] Device Serial Number f4-6d-04-ff-ff-e0-fc-22
	Kernel driver in use: e1000e
	Kernel modules: e1000e
00: 86 80 d3 10 07 04 10 00 00 00 00 02 10 00 00 00
10: 00 00 30 f6 00 00 00 00 01 c0 00 00 00 00 32 f6
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 69 83
30: 00 00 00 00 c8 00 00 00 00 00 00 00 0b 01 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 11 00 04 80 03 00 00 00 03 20 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 01 d0 22 c8 00 20 00 0f
d0: 05 e0 80 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 10 a0 01 00 c1 8c 00 00 0f 28 19 00 11 1c 03 00
f0: 40 00 11 10 00 00 00 00 00 00 00 00 00 00 00 00

06:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller (prog-if 30 [XHCI])
	Subsystem: ASUSTeK Computer Inc. P8B WS Motherboard
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 19
	Region 0: Memory at f6200000 (64-bit, non-prefetchable) [size=32K]
	Capabilities: [50] MSI: Enable- Count=1/8 Maskable- 64bit+
		Address: 0000000000000000  Data: 0000
	Capabilities: [68] MSI-X: Enable+ Count=8 Masked-
		Vector table: BAR=0 offset=00002000
		PBA: BAR=0 offset=00002080
	Capabilities: [78] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [80] Express (v2) Legacy Endpoint, MSI 00
		DevCap:	MaxPayload 512 bytes, PhantFunc 0, Latency L0s <64ns, L1 <2us
			ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
			MaxPayload 128 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr+ UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
		LnkCap:	Port #1, Speed 5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s unlimited, L1 unlimited
			ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp-
		LnkCtl:	ASPM Disabled; RCB 64 bytes Disabled- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
		LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
			 EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
	Capabilities: [100 v1] Virtual Channel
		Caps:	LPEVC=0 RefClk=100ns PATEntryBits=1
		Arb:	Fixed- WRR32- WRR64- WRR128-
		Ctrl:	ArbSelect=Fixed
		Status:	InProgress-
		VC0:	Caps:	PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
			Arb:	Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
			Ctrl:	Enable+ ID=0 ArbSelect=Fixed TC/VC=01
			Status:	NegoPending- InProgress-
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci
00: 21 1b 42 10 06 04 10 00 00 30 03 0c 10 00 00 00
10: 04 00 20 f6 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 88 84
30: 00 00 00 00 50 00 00 00 00 00 00 00 05 01 00 00
40: 00 00 00 00 60 61 11 02 00 00 00 00 00 00 00 00
50: 05 68 86 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 30 20 00 00 00 00 00 00 11 78 07 80 00 20 00 00
70: 80 20 00 00 00 00 00 00 01 80 43 c0 00 00 00 00
80: 10 00 12 00 02 82 90 05 00 28 01 00 12 fc 03 01
90: 40 00 12 10 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 62 00 00 00 00 00 00 00

07:03.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev c0) (prog-if 10 [OHCI])
	Subsystem: ASUSTeK Computer Inc. Device 82eb
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32 (8000ns max), Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 19
	Region 0: Memory at f6100000 (32-bit, non-prefetchable) [size=2K]
	Region 1: I/O ports at b000 [size=128]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1- D2+ AuxCurrent=0mA PME(D0-,D1-,D2+,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: firewire_ohci
	Kernel modules: firewire_ohci
00: 06 11 44 30 07 00 10 02 c0 10 00 0c 10 20 00 00
10: 00 00 10 f6 01 b0 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 eb 82
30: 00 00 00 00 50 00 00 00 00 00 00 00 05 01 00 20
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 01 00 02 e4 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00


^ permalink raw reply	[flat|nested] 19+ messages in thread

* RE: Debugging spurious wakeup
  2015-05-13  8:26       ` Gianluca Anzolin
@ 2015-05-13  8:30         ` Zhang, Rui
  2015-05-13  9:03           ` Gianluca Anzolin
  0 siblings, 1 reply; 19+ messages in thread
From: Zhang, Rui @ 2015-05-13  8:30 UTC (permalink / raw)
  To: Gianluca Anzolin; +Cc: linux-acpi@vger.kernel.org

04:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
	Kernel driver in use: e1000e
	Kernel modules: e1000e
PXSX	  S4	*enabled   pci:0000:04:00.0

Please run "echo PXSX > /proc/acpi/wakeup" before shutdown and then checks if the problem still exists.

Thanks,
Rui

> -----Original Message-----
> From: Gianluca Anzolin [mailto:gianluca@sottospazio.it]
> Sent: Wednesday, May 13, 2015 4:26 PM
> To: Zhang, Rui
> Cc: linux-acpi@vger.kernel.org
> Subject: Re: Debugging spurious wakeup
> Importance: High
> 
> On Wed, May 13, 2015 at 08:13:46AM +0000, Zhang, Rui wrote:
> > Hmm, none of them seems to be NIC related, can you please attach the
> output of lspci -vvxx as well?
> >
> 
> file attached (with I blanked the mac address)
> 
> Gianluca

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Debugging spurious wakeup
  2015-05-13  8:30         ` Zhang, Rui
@ 2015-05-13  9:03           ` Gianluca Anzolin
  2015-05-13  9:42             ` Zhang, Rui
  0 siblings, 1 reply; 19+ messages in thread
From: Gianluca Anzolin @ 2015-05-13  9:03 UTC (permalink / raw)
  To: Zhang, Rui; +Cc: linux-acpi@vger.kernel.org

On Wed, May 13, 2015 at 08:30:41AM +0000, Zhang, Rui wrote:
> 04:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
> 	Kernel driver in use: e1000e
> 	Kernel modules: e1000e
> PXSX	  S4	*enabled   pci:0000:04:00.0
> 
> Please run "echo PXSX > /proc/acpi/wakeup" before shutdown and then checks if
> the problem still exists.

Thank you for directions. Here follows what I did:

root@zanac:~$ echo PXSX > /proc/acpi/wakeup
root@zanac:~$ cat /proc/acpi/wakeup | grep PX
PXSX      S4    *disabled
PXSX      S4    *disabled
PXSX      S4    *disabled
PXSX      S4    *disabled
PXSX      S4    *disabled
PXSX      S4    *enabled   pci:0000:04:00.0
PXSX      S4    *enabled   pci:0000:06:00.0
root@zanac:$ poweroff

Then after 2-3 seconds the system turns on.

The echo command didn't work: infact I double checked, it didn't change the
wakeup status.

But if I disabled the wakeup would WOL packets still work?

I ask because if I disable 'Wake-up by PCIe' in the BIOS the system stays off,
but I need the WOL functionality.

Currently ethtool eth0 says:

        Supports Wake-on: pumbg
        Wake-on: g
        Current message level: 0x00000007 (7)
                               drv probe link

This should only allow magic-packets to wake up the system. To be sure I even
disconnected the cable from the NIC. Unfortunately it still turns on by itself.

Thanks,

Gianluca

> 
> Thanks,
> Rui
> 
> > -----Original Message-----
> > From: Gianluca Anzolin [mailto:gianluca@sottospazio.it]
> > Sent: Wednesday, May 13, 2015 4:26 PM
> > To: Zhang, Rui
> > Cc: linux-acpi@vger.kernel.org
> > Subject: Re: Debugging spurious wakeup
> > Importance: High
> > 
> > On Wed, May 13, 2015 at 08:13:46AM +0000, Zhang, Rui wrote:
> > > Hmm, none of them seems to be NIC related, can you please attach the
> > output of lspci -vvxx as well?
> > >
> > 
> > file attached (with I blanked the mac address)
> > 
> > Gianluca

^ permalink raw reply	[flat|nested] 19+ messages in thread

* RE: Debugging spurious wakeup
  2015-05-13  9:03           ` Gianluca Anzolin
@ 2015-05-13  9:42             ` Zhang, Rui
  2015-05-13 10:17               ` Gianluca Anzolin
  0 siblings, 1 reply; 19+ messages in thread
From: Zhang, Rui @ 2015-05-13  9:42 UTC (permalink / raw)
  To: Gianluca Anzolin; +Cc: linux-acpi@vger.kernel.org



> -----Original Message-----
> From: linux-acpi-owner@vger.kernel.org [mailto:linux-acpi-
> owner@vger.kernel.org] On Behalf Of Gianluca Anzolin
> Sent: Wednesday, May 13, 2015 5:04 PM
> To: Zhang, Rui
> Cc: linux-acpi@vger.kernel.org
> Subject: Re: Debugging spurious wakeup
> Importance: High
> 
> On Wed, May 13, 2015 at 08:30:41AM +0000, Zhang, Rui wrote:
> > 04:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network
> Connection
> > 	Kernel driver in use: e1000e
> > 	Kernel modules: e1000e
> > PXSX	  S4	*enabled   pci:0000:04:00.0
> >
> > Please run "echo PXSX > /proc/acpi/wakeup" before shutdown and then
> > checks if the problem still exists.
> 
> Thank you for directions. Here follows what I did:
> 
> root@zanac:~$ echo PXSX > /proc/acpi/wakeup root@zanac:~$ cat
> /proc/acpi/wakeup | grep PX
> PXSX      S4    *disabled
> PXSX      S4    *disabled
> PXSX      S4    *disabled
> PXSX      S4    *disabled
> PXSX      S4    *disabled
> PXSX      S4    *enabled   pci:0000:04:00.0
> PXSX      S4    *enabled   pci:0000:06:00.0
> root@zanac:$ poweroff
> 
> Then after 2-3 seconds the system turns on.
> 
> The echo command didn't work: infact I double checked, it didn't change the
> wakeup status.
> 
then please try
"echo disabled > /sys/bus/pci/0000:04:00.0/power/wakeup" instead.

> But if I disabled the wakeup would WOL packets still work?
> 
> I ask because if I disable 'Wake-up by PCIe' in the BIOS the system stays off,
> but I need the WOL functionality.
> 
This is just a debug method to confirm that it is the Ethernet card that brings the system back.

Thanks,
rui
> Currently ethtool eth0 says:
> 
>         Supports Wake-on: pumbg
>         Wake-on: g
>         Current message level: 0x00000007 (7)
>                                drv probe link
> 
> This should only allow magic-packets to wake up the system. To be sure I
> even disconnected the cable from the NIC. Unfortunately it still turns on by
> itself.
> 
> Thanks,
> 
> Gianluca
> 
> >
> > Thanks,
> > Rui
> >
> > > -----Original Message-----
> > > From: Gianluca Anzolin [mailto:gianluca@sottospazio.it]
> > > Sent: Wednesday, May 13, 2015 4:26 PM
> > > To: Zhang, Rui
> > > Cc: linux-acpi@vger.kernel.org
> > > Subject: Re: Debugging spurious wakeup
> > > Importance: High
> > >
> > > On Wed, May 13, 2015 at 08:13:46AM +0000, Zhang, Rui wrote:
> > > > Hmm, none of them seems to be NIC related, can you please attach
> > > > the
> > > output of lspci -vvxx as well?
> > > >
> > >
> > > file attached (with I blanked the mac address)
> > >
> > > Gianluca
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the
> body of a message to majordomo@vger.kernel.org More majordomo info at
> http://vger.kernel.org/majordomo-info.html

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Debugging spurious wakeup
  2015-05-13  9:42             ` Zhang, Rui
@ 2015-05-13 10:17               ` Gianluca Anzolin
  2015-05-13 10:51                 ` Gianluca Anzolin
  0 siblings, 1 reply; 19+ messages in thread
From: Gianluca Anzolin @ 2015-05-13 10:17 UTC (permalink / raw)
  To: Zhang, Rui; +Cc: linux-acpi@vger.kernel.org

On Wed, May 13, 2015 at 09:42:46AM +0000, Zhang, Rui wrote:
> > The echo command didn't work: infact I double checked, it didn't change the
> > wakeup status.
> > 
> then please try
> "echo disabled > /sys/bus/pci/0000:04:00.0/power/wakeup" instead.
> 

Here follow the commands given:

root@zanac:~$ cat /sys/bus/pci/devices/0000:04:00.0/power/wakeup
enabled
root@zanac:~$ echo disabled > /sys/bus/pci/devices/0000:04:00.0/power/wakeup
root@zanac:~$ cat /sys/bus/pci/devices/0000:04:00.0/power/wakeup
disabled
root@zanac:~$ poweroff

But after a couple of seconds the system still turns on.

Gianluca

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Debugging spurious wakeup
  2015-05-13 10:17               ` Gianluca Anzolin
@ 2015-05-13 10:51                 ` Gianluca Anzolin
  0 siblings, 0 replies; 19+ messages in thread
From: Gianluca Anzolin @ 2015-05-13 10:51 UTC (permalink / raw)
  To: Zhang, Rui; +Cc: linux-acpi@vger.kernel.org

On Wed, May 13, 2015 at 12:17:26PM +0200, Gianluca Anzolin wrote:
> On Wed, May 13, 2015 at 09:42:46AM +0000, Zhang, Rui wrote:
> > > The echo command didn't work: infact I double checked, it didn't change the
> > > wakeup status.
> > > 
> > then please try
> > "echo disabled > /sys/bus/pci/0000:04:00.0/power/wakeup" instead.
> > 
> 
> Here follow the commands given:
> 
> root@zanac:~$ cat /sys/bus/pci/devices/0000:04:00.0/power/wakeup
> enabled
> root@zanac:~$ echo disabled > /sys/bus/pci/devices/0000:04:00.0/power/wakeup
> root@zanac:~$ cat /sys/bus/pci/devices/0000:04:00.0/power/wakeup
> disabled
> root@zanac:~$ poweroff
> 

A small follow-up.

I looked for the devices with wakeup = enabled and they are:

0000:00:1d.0
0000:04:00.0
0000:05:00.0
0000:05:00.0

For each of them I tried to disable the wakeup with the echo command and then
poweroff, but the system always turns on after a couple of seconds.

I even tried to disable them all to no avail.

Gianluca

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Debugging spurious wakeup
  2015-05-13  6:58 Debugging spurious wakeup Gianluca Anzolin
  2015-05-13  7:46 ` Zhang, Rui
@ 2015-05-14 12:51 ` Gianluca Anzolin
  2015-05-15  7:52   ` Gianluca Anzolin
  2015-05-15  7:54 ` Daniel Lezcano
  2015-06-20 21:54 ` Andreas Mohr
  3 siblings, 1 reply; 19+ messages in thread
From: Gianluca Anzolin @ 2015-05-14 12:51 UTC (permalink / raw)
  To: linux-acpi

On Wed, May 13, 2015 at 08:58:25AM +0200, Gianluca Anzolin wrote:
> So I'm here to ask if there is a way to get the source/cause of the last
> wakeup by setting some ACPI debug option. This way I could at least pinpoint
> the device/interface that caused the spontaneous wakeup and then debug
> further or at least disable it.
> 
> I've tried to enable the ACPI hardware-related messages with the kernel
> arguments: acpi.debug_layer=0x2 acpi.debug_level=0xffffffff
> 

Hello,

I'm sorry to bother again but since the previous debug aids didn't go anywhere
I'm here to ask again if there is a command, a debug parameter, something that
could tell me the cause of the last system wake up.

I'm aware that in Windows there is the command "powercfg -lastwake", I need
something similar for linux, since this issue is linux specific (I can't
reproduce it in Windows).

Thank you,

Gianluca


^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Debugging spurious wakeup
  2015-05-14 12:51 ` Gianluca Anzolin
@ 2015-05-15  7:52   ` Gianluca Anzolin
  0 siblings, 0 replies; 19+ messages in thread
From: Gianluca Anzolin @ 2015-05-15  7:52 UTC (permalink / raw)
  To: linux-acpi

On Thu, May 14, 2015 at 02:51:48PM +0200, Gianluca Anzolin wrote:
> I'm sorry to bother again but since the previous debug aids didn't go
> anywhere I'm here to ask again if there is a command, a debug parameter,
> something that could tell me the cause of the last system wake up.
> 
> I'm aware that in Windows there is the command "powercfg -lastwake", I need
> something similar for linux, since this issue is linux specific (I can't
> reproduce it in Windows).
> 
> Thank you,
> 
> Gianluca
> 

Hello,

since I can reproduce the issue so easily I tried to take the output of lspci
-vvvxxx when the system stays off and when it turns on by itself.

The diff between the two outputs is mainly due to changes of IRQs and
addresses but there is something else:

-               RootSta: PME ReqID 0000, PMEStatus- PMEPending-
+               RootSta: PME ReqID 0400, PMEStatus- PMEPending-

for this entry:

00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI
Express Root Port 6 (rev b5) (prog-if 00 [Normal decode])

Basically when PME ReqID is 0400 the system turn on. I don't really know what
that means but I noticed that the PCIe port is connected to the network
controller.

This is the output of lspci -t:

-[0000:00]-+-00.0
           +-01.0-[01]--+-00.0
           |            \-00.1
           +-06.0-[02]--
           +-16.0
           +-1a.0
           +-1b.0
           +-1c.0-[03]--
           +-1c.5-[04]----00.0
           +-1c.6-[05]----00.0
           +-1c.7-[06]----00.0
           +-1d.0
           +-1e.0-[07]----03.0
           +-1f.0
           +-1f.2
           \-1f.3


And this is the entry 04:00.0:

04:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network
Connection

So it's really the ethernet driver that's misbehaving?

Thank you,

Gianluca

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Debugging spurious wakeup
  2015-05-13  6:58 Debugging spurious wakeup Gianluca Anzolin
  2015-05-13  7:46 ` Zhang, Rui
  2015-05-14 12:51 ` Gianluca Anzolin
@ 2015-05-15  7:54 ` Daniel Lezcano
  2015-05-15  8:35   ` Gianluca Anzolin
  2015-06-20 21:54 ` Andreas Mohr
  3 siblings, 1 reply; 19+ messages in thread
From: Daniel Lezcano @ 2015-05-15  7:54 UTC (permalink / raw)
  To: Gianluca Anzolin, linux-acpi


Hi Gianluca,

do yo have the option "Remain off after power failure" in the BIOS ?

Does the issue occur if you set this option ?




On 05/13/2015 08:58 AM, Gianluca Anzolin wrote:
> Hello,
>
> I have a curious problem with my system: whenever I wake up the PC with a WOL
> magic packet and then power it off the systems comes back to life after a
> couple of seconds, by itself.
>
> I can reproduce the problem 100% of the times.
>
> I've been having this problems for years. I remember this same issue occurred
> also with my previous computer, with a different mainboard. My current system
> has an ASUS P8B-WS mb with a Xeon 1275v2 CPU.
>
> I've ruled out in the time many factors: traffic on the net (by disconnecting
> the cable), RTC alarms (by disabling them)... long story short: I'm stuck.
>
> While I'm not the only one with this issue (see[1]), some people have reported
> mixed success by blacklisting some components (xhci-pci) or by setting
> unrelated BIOS options. Unfortunately these workarounds never worked for me.
>
> So I'm here to ask if there is a way to get the source/cause of the last wakeup
> by setting some ACPI debug option. This way I could at least pinpoint the
> device/interface that caused the spontaneous wakeup and then debug further or
> at least disable it.
>
> I've tried to enable the ACPI hardware-related messages with the kernel
> arguments: acpi.debug_layer=0x2 acpi.debug_level=0xffffffff
>
> Unfortunately I can't see the information I'm looking for in the resulting
> output. Should I enable some other debug_layer? Could anybody point me in the
> right direction?
>
> Thank you and best regards,
>
> Gianluca
>
> [1] https://bbs.archlinux.org/viewtopic.php?id=173648
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


-- 
  <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Debugging spurious wakeup
  2015-05-15  7:54 ` Daniel Lezcano
@ 2015-05-15  8:35   ` Gianluca Anzolin
  2015-05-15  8:49     ` Daniel Lezcano
  0 siblings, 1 reply; 19+ messages in thread
From: Gianluca Anzolin @ 2015-05-15  8:35 UTC (permalink / raw)
  To: Daniel Lezcano; +Cc: linux-acpi

On Fri, May 15, 2015 at 09:54:53AM +0200, Daniel Lezcano wrote:
> 
> Hi Gianluca,
> 
> do yo have the option "Remain off after power failure" in the BIOS ?
> 
> Does the issue occur if you set this option ?

Hi,

The BIOS option "Restore AC Power Loss" is set to "Power Off".

The other options are "Last State" and "Power On". I could change it to "Last
State", I can do it later if needed since I've no physical access to the PC
right now.

However I'm beginning to think it's the NIC driver, even though it occurs also
with no cable attached, I sent a while ago an email with my findings.

Thank you,

Gianluca

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Debugging spurious wakeup
  2015-05-15  8:35   ` Gianluca Anzolin
@ 2015-05-15  8:49     ` Daniel Lezcano
  0 siblings, 0 replies; 19+ messages in thread
From: Daniel Lezcano @ 2015-05-15  8:49 UTC (permalink / raw)
  To: Gianluca Anzolin; +Cc: linux-acpi

On 05/15/2015 10:35 AM, Gianluca Anzolin wrote:
> On Fri, May 15, 2015 at 09:54:53AM +0200, Daniel Lezcano wrote:
>>
>> Hi Gianluca,
>>
>> do yo have the option "Remain off after power failure" in the BIOS ?
>>
>> Does the issue occur if you set this option ?
>
> Hi,
>
> The BIOS option "Restore AC Power Loss" is set to "Power Off".
>
> The other options are "Last State" and "Power On". I could change it to "Last
> State", I can do it later if needed since I've no physical access to the PC
> right now.
>
> However I'm beginning to think it's the NIC driver, even though it occurs also
> with no cable attached, I sent a while ago an email with my findings.

I suggest you Cc the linux-netdev@, too. If this is related to the 
driver or the NIC itself, someone will probably have an answer for this 
issue.


-- 
  <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Debugging spurious wakeup
  2015-05-13  6:58 Debugging spurious wakeup Gianluca Anzolin
                   ` (2 preceding siblings ...)
  2015-05-15  7:54 ` Daniel Lezcano
@ 2015-06-20 21:54 ` Andreas Mohr
  2015-06-22 19:48   ` Gianluca Anzolin
  3 siblings, 1 reply; 19+ messages in thread
From: Andreas Mohr @ 2015-06-20 21:54 UTC (permalink / raw)
  To: gianluca; +Cc: Zhang Rui, linux-acpi

Hi,

[managed to gather proper In-Reply-To from spinics.net
rather than broken lkml.org]

I'm having a very similar issue with my PCI FireWire card:
whenever shutting down or even suspending,
I'm getting immediate spurious wakeup; currently most strongly suspecting
Firewire PHY-related IRQ event wakeups.

I collected the following items so far:
- asked for help (having the system properly record / retain the actual
  reason for system-global wakeup):
    "pm: record / retain actual reason of last system wakeup??"
      https://lkml.org/lkml/2015/6/2/625
- figured out that it can be silenced with *general* (ouch)
  BIOS PCI wakeup disable, yet that if not disabled
  (which is *very* desirable, obviously, to retain WOL capability etc.)
  it's actually already in a broken state directly post-BIOS-init,
  at LILO prompt (i.e., **NOT** in Linux, NOT a Linux driver issue!
  However perhaps we *might* be able to do something about it in Linux...):
    "fw-ohci: ALi M52xx unsupported"
      https://bugzilla.kernel.org/show_bug.cgi?id=10935
    (contains reference to http://www.tonymacx86.com/general-help/65531-gigabyte-uefi-bios-startech-firewire-pcie-card-sleep-wake-shutdown-restart-issues-thread-8.html
    where tons of people have issues with various FireWire cards -
    so it seems that this is an issue that's pretty much inherent
    to / associated with FireWire hardware behaviour)
- found 074_GPE_Routing.doc which explains these GPE / PME things
  (this *is* the stuff that's broken/problematic here, right??)
  in pretty detailed form
- "Re: PME# for add-on cards"
    http://markmail.org/message/7uuzqbtrpswzrezz
  mentions that probably BIOS forgot to do PME masking
  directly prior to activating hardware shutdown
  (well, at least in my case, where wakeup happens completely instantly,
  as opposed to your case where it will wakeup after a couple seconds)

No amount of fumbling (~1 hour) with CAP_PM register range
(PME_EN etc.; "setpci -v -s ${dst} CAP_PM+4.b=XX")
or e.g. setting the "remove" sysfs attribute of PCI (sub) devices
(this would then be a nicely controlled i.e. fine-grained manner)
so far managed to disable this behaviour.
I suspect that we might be talking
of simple complete signal level mal-functioning of the card
irrespective of how it's actually configured
to generate or not generate events...
(shutdown --> power change --> floating signals on PME# --> wakeup)
I also tried to completely mask all FireWire event types in driver-side
suspend handler, with no success (but given that this is a combo card
with various USB host controllers FireWire may not be the sub device to
be blamed after all - here we are again at dearly needing
system-provided information about the *maximally precise* reason
of last wakeup - PME ReqID [not available on my Conventional PCI system]
seems to be a prime candidate). But given that the Mac forum reports issues
with many FireWire cards, faulty USB sub device seems less likely.

So, I'm still quite far from possibly(!) being able
to create a device-specific PCI quirk entry (drivers/pci/quirks.c)
or to create driver-side workarounds
for FireWire cards which have this issue.

HTH,

Andreas Mohr
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Debugging spurious wakeup
  2015-06-20 21:54 ` Andreas Mohr
@ 2015-06-22 19:48   ` Gianluca Anzolin
  2015-06-23  6:36     ` Gianluca Anzolin
  0 siblings, 1 reply; 19+ messages in thread
From: Gianluca Anzolin @ 2015-06-22 19:48 UTC (permalink / raw)
  To: Andreas Mohr; +Cc: Zhang Rui, linux-acpi

Hello,

On Sat, Jun 20, 2015 at 11:54:41PM +0200, Andreas Mohr wrote:
> Hi,
> 
> [managed to gather proper In-Reply-To from spinics.net
> rather than broken lkml.org]
> 
> I'm having a very similar issue with my PCI FireWire card:
> whenever shutting down or even suspending,
> I'm getting immediate spurious wakeup; currently most strongly suspecting
> Firewire PHY-related IRQ event wakeups.

I don't know if the issue is the same as mine. In that case it wouldn't
be driver related. As explained before, for me the spontaneous wakeups
occur after a Wake-on-Lan but not when powering up the system by other
means (i.e. power button).

As suggested I asked on netdev but got no reply at all, so I'm on my own
right now.

Thank you for sharing your experience, the document about GPE and PME
seems useful to pinpoint the issue: as explained in another email, I
found a difference in lspci when the undesired wakeup occurs and it
involves PME signals:

-		RootSta: PME ReqID 0000, PMEStatus- PMEPending-
+		RootSta: PME ReqID 0400, PMEStatus- PMEPending-

The problem is, these difference is not related to the network PCI
device but to the PCI bridge behind which the network device sits.

If I find something useful (unlikely, but never lose the hope) I'll send
an update :)

Thank you,

Gianluca

> 
> I collected the following items so far:
> - asked for help (having the system properly record / retain the actual
>   reason for system-global wakeup):
>     "pm: record / retain actual reason of last system wakeup??"
>       https://lkml.org/lkml/2015/6/2/625
> - figured out that it can be silenced with *general* (ouch)
>   BIOS PCI wakeup disable, yet that if not disabled
>   (which is *very* desirable, obviously, to retain WOL capability etc.)
>   it's actually already in a broken state directly post-BIOS-init,
>   at LILO prompt (i.e., **NOT** in Linux, NOT a Linux driver issue!
>   However perhaps we *might* be able to do something about it in Linux...):
>     "fw-ohci: ALi M52xx unsupported"
>       https://bugzilla.kernel.org/show_bug.cgi?id=10935
>     (contains reference to http://www.tonymacx86.com/general-help/65531-gigabyte-uefi-bios-startech-firewire-pcie-card-sleep-wake-shutdown-restart-issues-thread-8.html
>     where tons of people have issues with various FireWire cards -
>     so it seems that this is an issue that's pretty much inherent
>     to / associated with FireWire hardware behaviour)
> - found 074_GPE_Routing.doc which explains these GPE / PME things
>   (this *is* the stuff that's broken/problematic here, right??)
>   in pretty detailed form
> - "Re: PME# for add-on cards"
>     http://markmail.org/message/7uuzqbtrpswzrezz
>   mentions that probably BIOS forgot to do PME masking
>   directly prior to activating hardware shutdown
>   (well, at least in my case, where wakeup happens completely instantly,
>   as opposed to your case where it will wakeup after a couple seconds)
> 
> No amount of fumbling (~1 hour) with CAP_PM register range
> (PME_EN etc.; "setpci -v -s ${dst} CAP_PM+4.b=XX")
> or e.g. setting the "remove" sysfs attribute of PCI (sub) devices
> (this would then be a nicely controlled i.e. fine-grained manner)
> so far managed to disable this behaviour.
> I suspect that we might be talking
> of simple complete signal level mal-functioning of the card
> irrespective of how it's actually configured
> to generate or not generate events...
> (shutdown --> power change --> floating signals on PME# --> wakeup)
> I also tried to completely mask all FireWire event types in driver-side
> suspend handler, with no success (but given that this is a combo card
> with various USB host controllers FireWire may not be the sub device to
> be blamed after all - here we are again at dearly needing
> system-provided information about the *maximally precise* reason
> of last wakeup - PME ReqID [not available on my Conventional PCI system]
> seems to be a prime candidate). But given that the Mac forum reports issues
> with many FireWire cards, faulty USB sub device seems less likely.
> 
> So, I'm still quite far from possibly(!) being able
> to create a device-specific PCI quirk entry (drivers/pci/quirks.c)
> or to create driver-side workarounds
> for FireWire cards which have this issue.
> 
> HTH,
> 
> Andreas Mohr
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Debugging spurious wakeup
  2015-06-22 19:48   ` Gianluca Anzolin
@ 2015-06-23  6:36     ` Gianluca Anzolin
  2015-06-23  8:32       ` Daniel Lezcano
  0 siblings, 1 reply; 19+ messages in thread
From: Gianluca Anzolin @ 2015-06-23  6:36 UTC (permalink / raw)
  To: Andreas Mohr; +Cc: Zhang Rui, linux-acpi

Hello,

Yesterday I took the time to read the document about GPE / PME handling and I
compared the wakeup code of my BIOS with the examples in that document.

I noticed that some vital wakeup code was executed only when a variable (PMSX)
was set. That variable was set by a global NPME() method and that method was
called by _OSC().

And in my logs I had this message:

giu 19 18:31:06 zanac kernel: acpi PNP0A08:00: _OSC: OS supports
[ExtendedConfig ASPM ClockPM Segments MSI]
giu 19 18:31:06 zanac kernel: \_SB_.PCI0:_OSC invalid UUID
giu 19 18:31:06 zanac kernel: _OSC request data:1 1f 0
giu 19 18:31:06 zanac kernel: acpi PNP0A08:00: _OSC failed (AE_ERROR);
disabling ASPM

A googled a bit and found the following bugzilla entry, that applies to my
situation perfectly: the NEXP variable isn't set anywhere, yet in Windows it
is.

https://bugzilla.kernel.org/show_bug.cgi?id=36932

So I disassembled the DSDT, I removed any test involving the NEXP variable in
the code, I recompiled and replaced the table with GRUB.

And then the _OSC() invocation completed successfully, giving me a working WOL
without spontaneous wakeups!

What puzzles me is that the location of the NEXP variables is marked as ACPI
NVS and the kernel never touches that region of memory. What is Windows doing
differently that makes it work?

However I consider the issue solved now. I leave also the link to the Arch
forum post where I describe in detail what I did for future reference.

https://bbs.archlinux.org/viewtopic.php?pid=1538895#p1538895

The document 074_GPE_Routing.doc proved very useful and I want to thank you for
your hints and the help I got from people in this mailing list.

Gianluca

PS: the PME ReqID marks the source of the latest wakeup and was then a lead of
the device responsible for the wakeup. But the problem was elsewhere...

On Mon, Jun 22, 2015 at 09:48:55PM +0200, Gianluca Anzolin wrote:
> Thank you for sharing your experience, the document about GPE and PME
> seems useful to pinpoint the issue: as explained in another email, I
> found a difference in lspci when the undesired wakeup occurs and it
> involves PME signals:
> 
> -		RootSta: PME ReqID 0000, PMEStatus- PMEPending-
> +		RootSta: PME ReqID 0400, PMEStatus- PMEPending-
> 
> The problem is, these difference is not related to the network PCI
> device but to the PCI bridge behind which the network device sits.
> 
> If I find something useful (unlikely, but never lose the hope) I'll send
> an update :)
> 
> Thank you,
> 
> Gianluca
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Debugging spurious wakeup
  2015-06-23  6:36     ` Gianluca Anzolin
@ 2015-06-23  8:32       ` Daniel Lezcano
  0 siblings, 0 replies; 19+ messages in thread
From: Daniel Lezcano @ 2015-06-23  8:32 UTC (permalink / raw)
  To: Gianluca Anzolin, Andreas Mohr; +Cc: Zhang Rui, linux-acpi

On 06/23/2015 08:36 AM, Gianluca Anzolin wrote:
> Hello,
>
> Yesterday I took the time to read the document about GPE / PME handling and I
> compared the wakeup code of my BIOS with the examples in that document.
>
> I noticed that some vital wakeup code was executed only when a variable (PMSX)
> was set. That variable was set by a global NPME() method and that method was
> called by _OSC().
>
> And in my logs I had this message:
>
> giu 19 18:31:06 zanac kernel: acpi PNP0A08:00: _OSC: OS supports
> [ExtendedConfig ASPM ClockPM Segments MSI]
> giu 19 18:31:06 zanac kernel: \_SB_.PCI0:_OSC invalid UUID
> giu 19 18:31:06 zanac kernel: _OSC request data:1 1f 0
> giu 19 18:31:06 zanac kernel: acpi PNP0A08:00: _OSC failed (AE_ERROR);
> disabling ASPM
>
> A googled a bit and found the following bugzilla entry, that applies to my
> situation perfectly: the NEXP variable isn't set anywhere, yet in Windows it
> is.
>
> https://bugzilla.kernel.org/show_bug.cgi?id=36932
>
> So I disassembled the DSDT, I removed any test involving the NEXP variable in
> the code, I recompiled and replaced the table with GRUB.
>
> And then the _OSC() invocation completed successfully, giving me a working WOL
> without spontaneous wakeups!

Great work and thanks for sharing you results !

> What puzzles me is that the location of the NEXP variables is marked as ACPI
> NVS and the kernel never touches that region of memory. What is Windows doing
> differently that makes it work?

Perhaps it is not Windows itself but the motherboard driver fixing a 
known bug ?

   -- Daniel

-- 
  <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

^ permalink raw reply	[flat|nested] 19+ messages in thread

end of thread, other threads:[~2015-06-23  8:32 UTC | newest]

Thread overview: 19+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-05-13  6:58 Debugging spurious wakeup Gianluca Anzolin
2015-05-13  7:46 ` Zhang, Rui
2015-05-13  8:12   ` Gianluca Anzolin
2015-05-13  8:13     ` Zhang, Rui
2015-05-13  8:26       ` Gianluca Anzolin
2015-05-13  8:30         ` Zhang, Rui
2015-05-13  9:03           ` Gianluca Anzolin
2015-05-13  9:42             ` Zhang, Rui
2015-05-13 10:17               ` Gianluca Anzolin
2015-05-13 10:51                 ` Gianluca Anzolin
2015-05-14 12:51 ` Gianluca Anzolin
2015-05-15  7:52   ` Gianluca Anzolin
2015-05-15  7:54 ` Daniel Lezcano
2015-05-15  8:35   ` Gianluca Anzolin
2015-05-15  8:49     ` Daniel Lezcano
2015-06-20 21:54 ` Andreas Mohr
2015-06-22 19:48   ` Gianluca Anzolin
2015-06-23  6:36     ` Gianluca Anzolin
2015-06-23  8:32       ` Daniel Lezcano

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).