No suspend after PCIe USB3.0 card installation

Please reproduce your error on a second machine before posting, and check the error by running without saved changes or extra modules (See FAQ No. 13, "How to report a bug"). For unstable Porteus versions (alpha, beta, rc) please use the relevant thread in our "Development" section.
User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

No suspend after PCIe USB3.0 card installation

Post#1 by Rava » 19 Sep 2013, 10:37

" My system: x86-64 port 2.1, XFCe.

No longer the suspend works after PCI-express USB3.0 card DeLock "89297" installation. The company info says it works from Linux kernel 2.6.*
Screen goes blank for a second, and PC immediately wakes up after that. The only change in the system was the installation of said PCIe card.

This is the info from /var/log/messages after failed suspend:

Code: Select all

Sep 19 11:59:57 porteus -- MARK --
Sep 19 12:19:57 porteus -- MARK --
Sep 19 12:32:06 porteus kernel: [12732.469225] PM: Syncing filesystems ... done.
Sep 19 12:32:06 porteus kernel: [12732.504376] i8042 kbd 00:0b: System wakeup enabled by ACPI
Sep 19 12:32:06 porteus kernel: [12732.504401] i8042 aux 00:0a: System wakeup disabled by ACPI
Sep 19 12:32:06 porteus kernel: [12732.504616] parport_pc 00:09: disabled
Sep 19 12:32:06 porteus kernel: [12732.504777] serial 00:08: disabled
Sep 19 12:32:06 porteus kernel: [12732.504782] serial 00:08: System wakeup disabled by ACPI
Sep 19 12:32:06 porteus kernel: [12732.667350] PM: suspend of devices complete after 174.811 msecs
Sep 19 12:32:06 porteus kernel: [12732.667563] PM: late suspend of devices complete after 0.209 msecs
Sep 19 12:32:06 porteus kernel: [12732.667719] pcieport 0000:00:0d.0: System wakeup enabled by ACPI
Sep 19 12:32:06 porteus kernel: [12732.678409] forcedeth 0000:00:08.0: System wakeup enabled by ACPI
Sep 19 12:32:06 porteus kernel: [12732.689379] ehci-pci 0000:00:02.1: System wakeup enabled by ACPI
Sep 19 12:32:06 porteus kernel: [12732.700352] ohci_hcd 0000:00:02.0: System wakeup enabled by ACPI
Sep 19 12:32:06 porteus kernel: [12732.711417] PM: noirq suspend of devices complete after 43.846 msecs
Sep 19 12:32:06 porteus kernel: [12732.711467] ACPI: Preparing to enter system sleep state S3
Sep 19 12:32:06 porteus kernel: [12732.711870] PM: Saving platform NVS memory
Sep 19 12:32:06 porteus kernel: [12732.713262] smpboot: CPU 1 is now offline
Sep 19 12:32:06 porteus kernel: [12732.713444] ACPI: Low-level resume complete
Sep 19 12:32:06 porteus kernel: [12732.713444] PM: Restoring platform NVS memory
Sep 19 12:32:06 porteus kernel: [12732.713444] Enabling non-boot CPUs ...
Sep 19 12:32:06 porteus kernel: [12732.713444] smpboot: Booting Node 0 Processor 1 APIC 0x1
Sep 19 12:32:06 porteus kernel: [12732.713014] process: Switch to broadcast mode on CPU1
Sep 19 12:32:06 porteus kernel: [12732.724988] CPU1 is up
Sep 19 12:32:06 porteus kernel: [12732.725305] ACPI: Waking up from system sleep state S3
Sep 19 12:32:06 porteus kernel: [12732.736333] ohci_hcd 0000:00:02.0: System wakeup disabled by ACPI
Sep 19 12:32:06 porteus kernel: [12732.747371] ehci-pci 0000:00:02.1: System wakeup disabled by ACPI
Sep 19 12:32:06 porteus kernel: [12732.769368] sata_nv 0000:00:05.0: Enabling HT MSI Mapping
Sep 19 12:32:06 porteus kernel: [12732.780369] sata_nv 0000:00:05.1: Enabling HT MSI Mapping
Sep 19 12:32:06 porteus kernel: [12732.791368] sata_nv 0000:00:05.2: Enabling HT MSI Mapping
Sep 19 12:32:06 porteus kernel: [12732.802374] snd_hda_intel 0000:00:06.1: Enabling HT MSI Mapping
Sep 19 12:32:06 porteus kernel: [12732.813388] forcedeth 0000:00:08.0: Enabling HT MSI Mapping
Sep 19 12:32:06 porteus kernel: [12732.813464] pcieport 0000:00:0d.0: Enabling HT MSI Mapping
Sep 19 12:32:06 porteus kernel: [12732.813540] pcieport 0000:00:0f.0: Enabling HT MSI Mapping
Sep 19 12:32:06 porteus kernel: [12732.824371] pcieport 0000:00:0d.0: System wakeup disabled by ACPI
Sep 19 12:32:06 porteus kernel: [12732.824511] PM: noirq resume of devices complete after 99.053 msecs
Sep 19 12:32:06 porteus kernel: [12732.824690] PM: early resume of devices complete after 0.132 msecs
Sep 19 12:32:06 porteus kernel: [12732.825570] forcedeth 0000:00:08.0: System wakeup disabled by ACPI
Sep 19 12:32:06 porteus kernel: [12732.827254] serial 00:08: activated
Sep 19 12:32:06 porteus kernel: [12732.827739] parport_pc 00:09: activated
Sep 19 12:32:06 porteus kernel: [12732.827762] i8042 kbd 00:0b: System wakeup disabled by ACPI
Sep 19 12:32:06 porteus kernel: [12732.982548] ata7.01: ACPI cmd ef/03:42:00:00:00:b0 (SET FEATURES) filtered out
Sep 19 12:32:06 porteus kernel: [12732.982551] ata7.01: ACPI cmd ef/03:0c:00:00:00:b0 (SET FEATURES) filtered out
Sep 19 12:32:06 porteus kernel: [12732.985529] ata7.00: ACPI cmd ef/03:42:00:00:00:a0 (SET FEATURES) filtered out
Sep 19 12:32:06 porteus kernel: [12732.985532] ata7.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
Sep 19 12:32:06 porteus kernel: [12732.991461] ata7.00: configured for UDMA/33
Sep 19 12:32:06 porteus kernel: [12732.997473] ata7.01: configured for UDMA/33
Sep 19 12:32:06 porteus kernel: [12733.133549] usb 3-1: reset high-speed USB device number 2 using xhci_hcd
Sep 19 12:32:06 porteus kernel: [12733.348401] forcedeth 0000:00:08.0 eth0: MSI enabled
Sep 19 12:32:06 porteus kernel: [12733.348618] forcedeth 0000:00:08.0 eth0: no link during initialization
Sep 19 12:32:06 porteus kernel: [12733.549263] ata2: SATA link down (SStatus 0 SControl 300)
Sep 19 12:32:06 porteus kernel: [12733.550266] ata1: SATA link down (SStatus 0 SControl 300)
Sep 19 12:32:06 porteus kernel: [12733.550297] ata4: SATA link down (SStatus 0 SControl 300)
Sep 19 12:32:06 porteus kernel: [12733.551258] ata6: SATA link down (SStatus 0 SControl 300)
Sep 19 12:32:06 porteus kernel: [12733.553274] ata3: SATA link down (SStatus 0 SControl 300)
Sep 19 12:32:06 porteus kernel: [12733.553288] ata5: SATA link down (SStatus 0 SControl 300)
Sep 19 12:32:06 porteus kernel: [12736.560293] 
Sep 19 12:32:06 porteus kernel: [12736.560294] floppy driver state
Sep 19 12:32:06 porteus kernel: [12736.560294] -------------------
Sep 19 12:32:06 porteus kernel: [12736.560305] now=4307403856 last interrupt=4294678770 diff=12725086 last called handler=0xffffffffa006aac6
Sep 19 12:32:06 porteus kernel: [12736.560306] timeout_message=lock fdc
Sep 19 12:32:06 porteus kernel: [12736.560306] last output bytes:
Sep 19 12:32:06 porteus kernel: [12736.560308]  8 90 4294678754
Sep 19 12:32:06 porteus kernel: [12736.560308]  8 90 4294678755
Sep 19 12:32:06 porteus kernel: [12736.560309]  8 90 4294678755
Sep 19 12:32:06 porteus kernel: [12736.560310]  8 80 4294678768
Sep 19 12:32:06 porteus kernel: [12736.560311]  8 90 4294678768
Sep 19 12:32:06 porteus kernel: [12736.560312]  8 90 4294678768
Sep 19 12:32:06 porteus kernel: [12736.560313]  8 90 4294678768
Sep 19 12:32:06 porteus kernel: [12736.560313]  e 80 4294678769
Sep 19 12:32:06 porteus kernel: [12736.560314] 13 90 4294678769
Sep 19 12:32:06 porteus kernel: [12736.560315]  0 90 4294678769
Sep 19 12:32:06 porteus kernel: [12736.560316] 1a 90 4294678769
Sep 19 12:32:06 porteus kernel: [12736.560316]  0 90 4294678769
Sep 19 12:32:06 porteus kernel: [12736.560317] 12 90 4294678769
Sep 19 12:32:06 porteus kernel: [12736.560318]  0 90 4294678769
Sep 19 12:32:06 porteus kernel: [12736.560319] 14 90 4294678769
Sep 19 12:32:06 porteus kernel: [12736.560320] 18 90 4294678769
Sep 19 12:32:06 porteus kernel: [12736.560320]  8 80 4294678770
Sep 19 12:32:06 porteus kernel: [12736.560321]  8 80 4294678770
Sep 19 12:32:06 porteus kernel: [12736.560322]  8 80 4294678770
Sep 19 12:32:06 porteus kernel: [12736.560323]  8 80 4294678770
Sep 19 12:32:06 porteus kernel: [12736.560323] last result at 4294678770
Sep 19 12:32:06 porteus kernel: [12736.560324] last redo_fd_request at 4298486848
Sep 19 12:32:06 porteus kernel: [12736.560329] status=0
Sep 19 12:32:06 porteus kernel: [12736.560329] fdc_busy=1
Sep 19 12:32:06 porteus kernel: [12736.560331] do_floppy=0xffffffffa006aac6
Sep 19 12:32:06 porteus kernel: [12736.560331] cont=ffffffffa0070850
Sep 19 12:32:06 porteus kernel: [12736.560332] current_req=          (null)
Sep 19 12:32:06 porteus kernel: [12736.560333] command_status=-1
Sep 19 12:32:06 porteus kernel: [12736.560333] 
Sep 19 12:32:06 porteus kernel: [12736.560337] floppy0: floppy timeout called
Sep 19 12:32:06 porteus kernel: [12736.560390] PM: resume of devices complete after 3735.696 msecs
Sep 19 12:32:07 porteus kernel: [12737.216185] forcedeth 0000:00:08.0 eth0: link down
Sep 19 12:32:26 porteus gpm[2439]: *** info [client.c(137)]: 
Sep 19 12:32:26 porteus gpm[2439]: Connecting at fd 6
I did mount a USB 3.0 external HD just OK, but I had to force umount...
The HD is now unplugged. Nothing else in plugged into the USB 3.0 ports.
Last edited by Rava on 19 Sep 2013, 21:47, edited 2 times in total.
Cheers!
Yours Rava

User avatar
brokenman
Site Admin
Site Admin
Posts: 5575
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: No suspend after PCIe USB3.0 card installation

Post#2 by brokenman » 19 Sep 2013, 13:16

Code: Select all

System wakeup disabled by ACPI
Please pass this cheat code to kernel, reboot and test.
acpi=force
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: No suspend after PCIe USB3.0 card installation

Post#3 by Rava » 19 Sep 2013, 15:50

I did. Snippet from psinfo.txt:
Bootparam: quiet initrd=initrd.xz zram=20% fsck timezone=Europe/Berlin kmap=de acpi=force BOOT_IMAGE=vmlinuz
Still the same:

Code: Select all

Sep 19 15:50:03 porteus NetworkManager[2321]: <info> sleep requested (sleeping: no  enabled: yes)
Sep 19 15:50:03 porteus NetworkManager[2321]: <info> sleeping or disabling...
Sep 19 15:50:03 porteus NetworkManager[2321]: <info> (eth0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37]
Sep 19 15:50:03 porteus NetworkManager[2321]: <info> (eth0): deactivating device (reason 'sleeping') [37]
Sep 19 15:50:03 porteus dhcpcd[3889]: received SIGTERM, stopping
Sep 19 15:50:03 porteus dhcpcd[3889]: eth0: removing interface
Sep 19 15:50:03 porteus NetworkManager[2321]: <info> (eth0): canceled DHCP transaction, DHCP client pid 3889
Sep 19 15:50:03 porteus NetworkManager[2321]: <info> (eth0): cleaning up...
Sep 19 15:50:03 porteus NetworkManager[2321]: <info> (eth0): taking down device.
Sep 19 15:50:03 porteus dbus[1237]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Sep 19 15:50:03 porteus dbus[1237]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Sep 19 15:50:11 porteus kernel: [  423.344432] PM: Syncing filesystems ... done.
Sep 19 15:50:11 porteus kernel: [  423.384402] i8042 kbd 00:0b: System wakeup enabled by ACPI
Sep 19 15:50:11 porteus kernel: [  423.384426] i8042 aux 00:0a: System wakeup disabled by ACPI
Sep 19 15:50:11 porteus kernel: [  423.384531] parport_pc 00:09: disabled
Sep 19 15:50:11 porteus kernel: [  423.384636] serial 00:08: disabled
Sep 19 15:50:11 porteus kernel: [  423.384640] serial 00:08: System wakeup disabled by ACPI
Sep 19 15:50:11 porteus kernel: [  423.548335] PM: suspend of devices complete after 180.787 msecs
Sep 19 15:50:11 porteus kernel: [  423.548547] PM: late suspend of devices complete after 0.208 msecs
Sep 19 15:50:11 porteus kernel: [  423.548707] pcieport 0000:00:0d.0: System wakeup enabled by ACPI
Sep 19 15:50:11 porteus kernel: [  423.559344] forcedeth 0000:00:08.0: System wakeup enabled by ACPI
Sep 19 15:50:11 porteus acpid: client 2668[0:1000] has disconnected
Sep 19 15:50:11 porteus kernel: [  423.570314] ehci-pci 0000:00:02.1: System wakeup enabled by ACPI
Sep 19 15:50:11 porteus kernel: [  423.581289] ohci_hcd 0000:00:02.0: System wakeup enabled by ACPI
Sep 19 15:50:11 porteus acpid: client 2668[0:1000] has disconnected
Sep 19 15:50:11 porteus kernel: [  423.592360] PM: noirq suspend of devices complete after 43.809 msecs
Sep 19 15:50:11 porteus kernel: [  423.592420] ACPI: Preparing to enter system sleep state S3
Sep 19 15:50:11 porteus kernel: [  423.592822] PM: Saving platform NVS memory
Sep 19 15:50:11 porteus kernel: [  423.594014] smpboot: CPU 1 is now offline
Sep 19 15:50:11 porteus kernel: [  423.594014] ACPI: Low-level resume complete
Sep 19 15:50:11 porteus kernel: [  423.594014] PM: Restoring platform NVS memory
Sep 19 15:50:11 porteus kernel: [  423.594014] Enabling non-boot CPUs ...
Sep 19 15:50:11 porteus kernel: [  423.594014] smpboot: Booting Node 0 Processor 1 APIC 0x1
Sep 19 15:50:11 porteus kernel: [  423.594014] process: Switch to broadcast mode on CPU1
Sep 19 15:50:11 porteus kernel: [  423.605936] CPU1 is up
Sep 19 15:50:11 porteus kernel: [  423.606246] ACPI: Waking up from system sleep state S3
Sep 19 15:50:11 porteus kernel: [  423.617338] ohci_hcd 0000:00:02.0: System wakeup disabled by ACPI
Sep 19 15:50:11 porteus kernel: [  423.628373] ehci-pci 0000:00:02.1: System wakeup disabled by ACPI
Sep 19 15:50:11 porteus kernel: [  423.650369] sata_nv 0000:00:05.0: Enabling HT MSI Mapping
Sep 19 15:50:11 porteus kernel: [  423.661369] sata_nv 0000:00:05.1: Enabling HT MSI Mapping
Sep 19 15:50:11 porteus kernel: [  423.672369] sata_nv 0000:00:05.2: Enabling HT MSI Mapping
Sep 19 15:50:11 porteus kernel: [  423.683375] snd_hda_intel 0000:00:06.1: Enabling HT MSI Mapping
Sep 19 15:50:11 porteus kernel: [  423.694389] forcedeth 0000:00:08.0: Enabling HT MSI Mapping
Sep 19 15:50:11 porteus kernel: [  423.694465] pcieport 0000:00:0d.0: Enabling HT MSI Mapping
Sep 19 15:50:11 porteus kernel: [  423.694540] pcieport 0000:00:0f.0: Enabling HT MSI Mapping
Sep 19 15:50:11 porteus kernel: [  423.705373] pcieport 0000:00:0d.0: System wakeup disabled by ACPI
Sep 19 15:50:11 porteus kernel: [  423.705512] PM: noirq resume of devices complete after 99.113 msecs
Sep 19 15:50:11 porteus kernel: [  423.705693] PM: early resume of devices complete after 0.134 msecs
Sep 19 15:50:11 porteus kernel: [  423.705821] forcedeth 0000:00:08.0: System wakeup disabled by ACPI
Sep 19 15:50:11 porteus kernel: [  423.707764] serial 00:08: activated
Sep 19 15:50:11 porteus kernel: [  423.708231] parport_pc 00:09: activated
Sep 19 15:50:11 porteus kernel: [  423.708254] i8042 kbd 00:0b: System wakeup disabled by ACPI
Sep 19 15:50:11 porteus kernel: [  423.863540] ata7.01: ACPI cmd ef/03:42:00:00:00:b0 (SET FEATURES) filtered out
Sep 19 15:50:11 porteus kernel: [  423.863543] ata7.01: ACPI cmd ef/03:0c:00:00:00:b0 (SET FEATURES) filtered out
Sep 19 15:50:11 porteus kernel: [  423.866540] ata7.00: ACPI cmd ef/03:42:00:00:00:a0 (SET FEATURES) filtered out
Sep 19 15:50:11 porteus kernel: [  423.866543] ata7.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
Sep 19 15:50:11 porteus kernel: [  423.872465] ata7.00: configured for UDMA/33
Sep 19 15:50:11 porteus kernel: [  423.878473] ata7.01: configured for UDMA/33
Sep 19 15:50:11 porteus kernel: [  424.014557] usb 3-1: reset high-speed USB device number 2 using xhci_hcd
Sep 19 15:50:11 porteus kernel: [  424.430275] ata1: SATA link down (SStatus 0 SControl 300)
Sep 19 15:50:11 porteus kernel: [  424.430297] ata2: SATA link down (SStatus 0 SControl 300)
Sep 19 15:50:11 porteus kernel: [  424.431273] ata6: SATA link down (SStatus 0 SControl 300)
Sep 19 15:50:11 porteus kernel: [  424.431285] ata3: SATA link down (SStatus 0 SControl 300)
Sep 19 15:50:11 porteus kernel: [  424.431296] ata5: SATA link down (SStatus 0 SControl 300)
Sep 19 15:50:11 porteus kernel: [  424.431330] ata4: SATA link down (SStatus 0 SControl 300)
Sep 19 15:50:11 porteus kernel: [  427.440294] 
Sep 19 15:50:11 porteus kernel: [  427.440295] floppy driver state
Sep 19 15:50:11 porteus kernel: [  427.440296] -------------------
Sep 19 15:50:11 porteus kernel: [  427.440306] now=4295094736 last interrupt=4294678926 diff=415810 last called handler=0xffffffffa0077ac6
Sep 19 15:50:11 porteus kernel: [  427.440307] timeout_message=lock fdc
Sep 19 15:50:11 porteus kernel: [  427.440307] last output bytes:
Sep 19 15:50:11 porteus kernel: [  427.440309]  8 90 4294678910
Sep 19 15:50:11 porteus kernel: [  427.440310]  8 90 4294678910
Sep 19 15:50:11 porteus kernel: [  427.440311]  8 90 4294678910
Sep 19 15:50:11 porteus kernel: [  427.440311]  8 80 4294678924
Sep 19 15:50:11 porteus kernel: [  427.440312]  8 90 4294678924
Sep 19 15:50:11 porteus kernel: [  427.440313]  8 90 4294678924
Sep 19 15:50:11 porteus kernel: [  427.440314]  8 90 4294678924
Sep 19 15:50:11 porteus kernel: [  427.440314]  e 80 4294678925
Sep 19 15:50:11 porteus kernel: [  427.440315] 13 90 4294678925
Sep 19 15:50:11 porteus kernel: [  427.440316]  0 90 4294678925
Sep 19 15:50:11 porteus kernel: [  427.440317] 1a 90 4294678925
Sep 19 15:50:11 porteus kernel: [  427.440318]  0 90 4294678925
Sep 19 15:50:11 porteus kernel: [  427.440318] 12 90 4294678925
Sep 19 15:50:11 porteus kernel: [  427.440319]  0 90 4294678925
Sep 19 15:50:11 porteus kernel: [  427.440320] 14 90 4294678925
Sep 19 15:50:11 porteus kernel: [  427.440321] 18 90 4294678925
Sep 19 15:50:11 porteus kernel: [  427.440322]  8 80 4294678926
Sep 19 15:50:11 porteus kernel: [  427.440322]  8 80 4294678926
Sep 19 15:50:11 porteus kernel: [  427.440323]  8 80 4294678926
Sep 19 15:50:11 porteus kernel: [  427.440324]  8 80 4294678926
Sep 19 15:50:11 porteus kernel: [  427.440325] last result at 4294678926
Sep 19 15:50:11 porteus kernel: [  427.440325] last redo_fd_request at 4294769848
Sep 19 15:50:11 porteus kernel: [  427.440330] status=0
Sep 19 15:50:11 porteus kernel: [  427.440330] fdc_busy=1
Sep 19 15:50:11 porteus kernel: [  427.440332] do_floppy=0xffffffffa0077ac6
Sep 19 15:50:11 porteus kernel: [  427.440332] cont=ffffffffa007d850
Sep 19 15:50:11 porteus kernel: [  427.440333] current_req=          (null)
Sep 19 15:50:11 porteus kernel: [  427.440334] command_status=-1
Sep 19 15:50:11 porteus kernel: [  427.440334] 
Sep 19 15:50:11 porteus kernel: [  427.440338] floppy0: floppy timeout called
Sep 19 15:50:11 porteus kernel: [  427.440383] PM: resume of devices complete after 3734.686 msecs
Sep 19 15:50:11 porteus acpid: client connected from 2668[0:1000]
Sep 19 15:50:11 porteus acpid: 1 client rule loaded
Sep 19 15:50:12 porteus acpid: client connected from 2668[0:1000]
Sep 19 15:50:12 porteus acpid: 1 client rule loaded
Sep 19 15:50:12 porteus NetworkManager[2321]: <info> wake requested (sleeping: yes  enabled: yes)
Sep 19 15:50:12 porteus NetworkManager[2321]: <info> waking up and re-enabling...
Sep 19 15:50:12 porteus NetworkManager[2321]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Sep 19 15:50:12 porteus NetworkManager[2321]: <info> (eth0): bringing up device.
Sep 19 15:50:12 porteus NetworkManager[2321]: <info> (eth0): carrier now ON (device state 20)
Sep 19 15:50:12 porteus NetworkManager[2321]: <info> (eth0): preparing device.
Sep 19 15:50:12 porteus NetworkManager[2321]: <info> (eth0): deactivating device (reason 'managed') [2]
Sep 19 15:50:12 porteus NetworkManager[2321]: <info> (eth0): device state change: unavailable -> disconnected (reason 'none') [20 30 0]
Sep 19 15:50:12 porteus NetworkManager[2321]: <info> Auto-activating connection 'Wired connection 2'.
Sep 19 15:50:12 porteus NetworkManager[2321]: <info> Activation (eth0) starting connection 'Wired connection 2'
Sep 19 15:50:12 porteus NetworkManager[2321]: <info> (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Sep 19 15:50:12 porteus kernel: [  427.964549] forcedeth 0000:00:08.0 eth0: MSI enabled
Sep 19 15:50:12 porteus NetworkManager[2321]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Sep 19 15:50:12 porteus NetworkManager[2321]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Sep 19 15:50:12 porteus NetworkManager[2321]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Sep 19 15:50:12 porteus NetworkManager[2321]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Sep 19 15:50:12 porteus NetworkManager[2321]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Sep 19 15:50:12 porteus NetworkManager[2321]: <info> (eth0): device state change: prepare -> config (reason 'none') [40 50 0]
Sep 19 15:50:12 porteus NetworkManager[2321]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Sep 19 15:50:12 porteus NetworkManager[2321]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Sep 19 15:50:12 porteus NetworkManager[2321]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Sep 19 15:50:12 porteus NetworkManager[2321]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Sep 19 15:50:12 porteus NetworkManager[2321]: <info> (eth0): device state change: config -> ip-config (reason 'none') [50 70 0]
Sep 19 15:50:12 porteus NetworkManager[2321]: <info> Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Sep 19 15:50:12 porteus dhcpcd[4451]: version 5.6.6 starting
Sep 19 15:50:12 porteus NetworkManager[2321]: <info> dhcpcd started with pid 4451
Sep 19 15:50:12 porteus NetworkManager[2321]: <info> Activation (eth0) Beginning IP6 addrconf.
Sep 19 15:50:12 porteus NetworkManager[2321]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Sep 19 15:50:12 porteus NetworkManager[2321]: <info> (eth0): DHCPv4 state changed nbi -> preinit
Sep 19 15:50:12 porteus dhcpcd[4451]: eth0: sending IPv6 Router Solicitation
Sep 19 15:50:12 porteus dhcpcd[4451]: eth0: rebinding lease of 192.168.7.235
Sep 19 15:50:12 porteus dhcpcd[4451]: eth0: acknowledged 192.168.7.235 from 192.168.7.1
Sep 19 15:50:12 porteus dhcpcd[4451]: eth0: checking for 192.168.7.235
Sep 19 15:50:16 porteus dhcpcd[4451]: eth0: sending IPv6 Router Solicitation
Sep 19 15:50:17 porteus dhcpcd[4451]: eth0: leased 192.168.7.235 for 46666620 seconds
Sep 19 15:50:17 porteus NetworkManager[2321]: <info> (eth0): DHCPv4 state changed preinit -> bound
Sep 19 15:50:17 porteus NetworkManager[2321]: <info>   address 192.168.7.235
Sep 19 15:50:17 porteus NetworkManager[2321]: <info>   prefix 24 (255.255.255.0)
Sep 19 15:50:17 porteus NetworkManager[2321]: <info>   gateway 192.168.7.1
Sep 19 15:50:17 porteus NetworkManager[2321]: <info>   hostname 'porteus'
Sep 19 15:50:17 porteus NetworkManager[2321]: <info>   nameserver '192.168.7.1'
Sep 19 15:50:17 porteus NetworkManager[2321]: <info>   domain name 'ravadomain'
Sep 19 15:50:17 porteus NetworkManager[2321]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Sep 19 15:50:17 porteus NetworkManager[2321]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) started...
Sep 19 15:50:18 porteus NetworkManager[2321]: <info> (eth0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
Sep 19 15:50:18 porteus NetworkManager[2321]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) complete.
Sep 19 15:50:18 porteus NetworkManager[2321]: <info> (eth0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Sep 19 15:50:18 porteus NetworkManager[2321]: <info> Policy set 'Wired connection 2' (eth0) as default for IPv4 routing and DNS.
Sep 19 15:50:18 porteus NetworkManager[2321]: <info> Activation (eth0) successful, device activated.
Sep 19 15:50:18 porteus dbus[1237]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Sep 19 15:50:18 porteus dbus[1237]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Sep 19 15:50:20 porteus dhcpcd[4451]: eth0: sending IPv6 Router Solicitation
Sep 19 15:50:24 porteus dhcpcd[4451]: eth0: sending IPv6 Router Solicitation
Sep 19 15:50:24 porteus dhcpcd[4451]: eth0: no IPv6 Routers available
Especially these lines irk me:

Code: Select all

Sep 19 15:50:11 porteus kernel: [  423.384402] i8042 kbd 00:0b: System wakeup enabled by ACPI
Sep 19 15:50:11 porteus kernel: [  423.384426] i8042 aux 00:0a: System wakeup disabled by ACPI
Sep 19 15:50:11 porteus kernel: [  423.384531] parport_pc 00:09: disabled
Sep 19 15:50:11 porteus kernel: [  423.384636] serial 00:08: disabled
Sep 19 15:50:11 porteus kernel: [  423.384640] serial 00:08: System wakeup disabled by ACPI
Sep 19 15:50:11 porteus kernel: [  423.548335] PM: suspend of devices complete after 180.787 msecs
Sep 19 15:50:11 porteus kernel: [  423.548547] PM: late suspend of devices complete after 0.208 msecs
Sep 19 15:50:11 porteus kernel: [  423.548707] pcieport 0000:00:0d.0: System wakeup enabled by ACPI
Sep 19 15:50:11 porteus kernel: [  423.559344] forcedeth 0000:00:08.0: System wakeup enabled by ACPI
Sep 19 15:50:11 porteus acpid: client 2668[0:1000] has disconnected
Sep 19 15:50:11 porteus kernel: [  423.570314] ehci-pci 0000:00:02.1: System wakeup enabled by ACPI
Sep 19 15:50:11 porteus kernel: [  423.581289] ohci_hcd 0000:00:02.0: System wakeup enabled by ACPI
Why the "System wakeup enabled by ACPI" and "System wakeup disabled by ACPI" ...
Cheers!
Yours Rava

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: No suspend after PCIe USB3.0 card installation

Post#4 by Rava » 19 Sep 2013, 20:56

Update
Strange enough, now that I did a cold boot, and not just a warm reboot like above, suspend works like a charm... :%)
Cheers!
Yours Rava

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: SOLVED - No suspend after PCIe USB3.0 card installation

Post#5 by Rava » 19 Sep 2013, 21:47

Update 2

And now it fails again. Seems, as far as the running system is more "virgin", suspend works, and when I have done a bit more with it, suspend will fail...
But how to examine this issue further?

I also tried searching the web, but it seems, my search fu failed for now...
Cheers!
Yours Rava

User avatar
brokenman
Site Admin
Site Admin
Posts: 5575
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: No suspend after PCIe USB3.0 card installation

Post#6 by brokenman » 19 Sep 2013, 23:47

If your output from: dmesg|grep rtm gives you a green light for S3 or S4 (acpi sleep states) then you should start looking at clock times. It could be due to the timezone if during suspend, the system writes the time to /proc/driver/rtc. I am not well versed in the suspend procedure here but you could easily test the theory by setting the system time to UTC and disabling hwclock from writing to RTC. First please double check that the installation of hardware did not alter any ACPI settings in your bios. Not likely, but always better to make preliminary checks before digging deeper.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: No suspend after PCIe USB3.0 card installation

Post#7 by Rava » 20 Sep 2013, 05:03

Code: Select all

root@porteus:/mnt# dmesg|grep rtm
root@porteus:/mnt# dmesg|grep -i rtm
root@porteus:/mnt# 
So, does that mean, I have red light for S3 or S4 (acpi sleep states)?

And how do I check the hardware altering any ACPI settings in my BIOS?
Cheers!
Yours Rava

User avatar
brokenman
Site Admin
Site Admin
Posts: 5575
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: No suspend after PCIe USB3.0 card installation

Post#8 by brokenman » 20 Sep 2013, 14:06

Try: grep rtc /var/log/messages

You would need to enter the BIOS and poke around for settings that say ACPI or APM. Usually found under a 'power' menu or something similar. Getting into the BIOS requires that you hit a certain key after the first boot post. Perhaps it flashes on the screen which key to hit. It varies with different systems but is most usually F2, DEL or ESC.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: No suspend after PCIe USB3.0 card installation

Post#9 by Rava » 20 Sep 2013, 15:17

Code: Select all

root@porteus:/mnt# grep rtc /var/log/messages
Sep 20 05:01:02 porteus kernel: [    0.426794] rtc_cmos 00:04: RTC can wake from S4
Sep 20 05:01:02 porteus kernel: [    0.427030] rtc_cmos 00:04: rtc core: registered rtc_cmos as rtc0
Sep 20 05:01:02 porteus kernel: [    0.427067] rtc_cmos 00:04: alarms up to one year, y3k, 242 bytes nvram, hpet irqs
Sep 20 05:01:02 porteus kernel: [    0.429662] rtc_cmos 00:04: setting system clock to 2013-09-20 05:00:55 UTC (1379653255)
I will look into BIOS at next reboot and tell you what I found there...
Cheers!
Yours Rava

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: No suspend after PCIe USB3.0 card installation

Post#10 by Rava » 22 Sep 2013, 03:33

Finally, the BIOS screenshots:

Image
Image

Is that all OK in my BIOS? Did I make the correct screenshots?
Cheers!
Yours Rava

User avatar
fanthom
Site Admin
Site Admin
Posts: 4620
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: No suspend after PCIe USB3.0 card installation

Post#11 by fanthom » 22 Sep 2013, 08:43

if suspend worked fine before PCIe card installation then BIOS/OS settings are probably ok. must be a driver/ACPI implementation fault so i would try to upgrade kernel (3.11.x is latest stable) and see if that helps.
also - you could boot Ubuntu and check if suspend works there.

EDIT:\\
tomorrow i'll have a look on kernel config and check if there is something related to PCIe/USB3.0 and suspend.

EDIT2:\\
please do as follows:
- edit /etc/laptop-mode/conf.d/usb-autosuspend.conf and change to:

Code: Select all

CONTROL_USB_AUTOSUSPEND="0"
- if that wont help then recompile (or upgrade) kernel and disable following option:

Code: Select all

CONFIG_USB_SUSPEND=y
Please add [Solved] to your thread title if the solution was found.

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: No suspend after PCIe USB3.0 card installation

Post#12 by Rava » 23 Sep 2013, 06:06

fanthom wrote:if suspend worked fine before PCIe card installation then BIOS/OS settings are probably ok. must be a driver/ACPI implementation fault
You are right, worked like a charm prior of the installation of the PCIe card...
fanthom wrote:please do as follows:
- edit /etc/laptop-mode/conf.d/usb-autosuspend.conf and change to:

Code: Select all

CONTROL_USB_AUTOSUSPEND="0"
Do I need to reboot for it to change, or is the running system okay?

//Update 1
At least, in the running system, it failed... :(

//Update 2
I downloaded xubuntu-13.04-desktop-amd64.iso (should be XFCe, newest, for AMD x86-64...) and will try it as soon as I find a free cd-rw disk...
Why is there no version for both AMD and Intel x86-64 for Ubuntu (xUbuntu), or did I miss that? I only saw the 386 and AMD-x86-64 versions...
Cheers!
Yours Rava

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: No suspend after PCIe USB3.0 card installation

Post#13 by Rava » 23 Sep 2013, 19:21

Aaand it won't work with a new started Porteus either...

Now I need a fitting blank CD disk, cause the image is too large to fit on my CD RWs...
Cheers!
Yours Rava

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: No suspend after PCIe USB3.0 card installation

Post#14 by Rava » 24 Sep 2013, 19:45

Update

Without changing anything, something quite strange happened. I tweaked the bootup to start in virtual console, and I start X as non root user via one of the consoles.
Now, usually I get the suspend etc. stuff in XFCe's "Log Out" menu, but now, I only get [x] Log out, Restart and Shutdown is greyed out, and suspend is not there at all...

What could be the reason for that? =@
Cheers!
Yours Rava

User avatar
brokenman
Site Admin
Site Admin
Posts: 5575
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: No suspend after PCIe USB3.0 card installation

Post#15 by brokenman » 25 Sep 2013, 00:19

check: ck-list-sessions

Also what is in your /etc/X11/xinit/xinitrc file?

This sounds like ck-launch-session or dbus-lauch daemon is not active.
How do i become super user?
Wear your underpants on the outside and put on a cape.

Post Reply