On Mon, Aug 05, 2019 at 04:01:11PM +0200, Matthias Andree wrote: > Am 05.08.19 um 15:00 schrieb Mika Westerberg: > > On Mon, Aug 05, 2019 at 07:47:05AM -0500, Bjorn Helgaas wrote: > >> On Mon, Aug 05, 2019 at 03:27:51PM +0300, Mika Westerberg wrote: > >>> Are you able to get dmesg after resume or is it completely dead? It > >>> would help you we could see how long it tries to wait for the downstream > >>> link by passing "pciepordrv.dyndbg" to the kernel command line. > >> "pcieportdrv.dyndbg" (with "t"), I think. > > Right, thanks for the correction. > > Hi Mika, Bjorn, > > thanks for picking this up. I have used pcieportdrv.dyndbg=+p (not sure > if something else would have worked) and was lucky that I could transfer > dmesg to a USB stick before the machine went completely unusable. > > $ grep pcieport dmesg.txt > > [ 0.698739] pcieport 0000:00:01.3: Signaling PME with IRQ 28 > [ 0.698799] pcieport 0000:00:01.3: AER: enabled with IRQ 28 > [ 0.698966] pcieport 0000:00:03.1: Signaling PME with IRQ 29 > [ 0.699017] pcieport 0000:00:03.1: AER: enabled with IRQ 29 > [ 0.699188] pcieport 0000:00:07.1: Signaling PME with IRQ 30 > [ 0.699230] pcieport 0000:00:07.1: AER: enabled with IRQ 30 > [ 0.699816] pcieport 0000:00:08.1: Signaling PME with IRQ 31 > [ 0.699860] pcieport 0000:00:08.1: AER: enabled with IRQ 31 > [ 119.637492] pcieport 0000:00:03.1: waiting downstream link for 100 ms > [ 119.649285] pcieport 0000:00:08.1: waiting downstream link for 100 ms > [ 119.649287] pcieport 0000:00:07.1: waiting downstream link for 100 ms > [ 119.649376] pcieport 0000:00:01.3: waiting downstream link for 100 ms > [ 119.803025] pcieport 0000:16:08.0: waiting downstream link for 100 ms > [ 119.803031] pcieport 0000:16:01.0: waiting downstream link for 100 ms Can you also attach the dmesg.txt to the bugzilla entry?
