Instant USB after suspend-resume/hibernate-resume

Hello all,
I've got a decently old laptop, Acer 2310 if you want to search up the specs. No built-in wireless, though.
I also have a Sitecom USB Wireless N 300 key with Ralink RT3070 chipset, for which I've also installed the rt3070sta module directly from the manufacturer.
The setup works great with the WICD installed, but it's taken me a lot of work simply to make it compatible with the suspend/hibernate/resume functions.
It turns out that either the ehci-hcd or ohci-hcd module (I forget which one) had to be shut off before entering the sleep mode and restarted on resume in order to have all my usb functionality work after resuming. Otherwise, I'd be running without my USB hardware, or worse, I'd just have a black screen to greet me on wakeup. This module restart also means that it has to reconnect to the wireless network (...or does it?).
Well, it works, but here's my problem. We have a business laptop with Vista Home, with a PCI wireless device that works INSTANTLY on resume. No need to wait. Just one second to resume from standby and the thing is still connected to the network, easily verified by doing a quick new Google search on Internet Explorer.
I WANT THAT FUNCTIONALITY.
Now, if anyone's willing to just give me a little info:
1) Who of you are able to resume from standby on Arch and still have INSTANT wireless network access? By instant, I mean you don't have to wait for the thing to reconnect to the network, and WICD or network manager doesn't even tell you it's authenticating or anything. Heck, it probably hasn't even disconnected. If you have this kind of instant access, please let me know if the network adapter is USB, PCI or any other bus.
2) Who of you have that trouble with your usb ehci-hcd/ohci-hcd modules that need restarting after resume from standby in order to work? Have you found any other method of getting them to work coming out of standby, but WITHOUT doing some full module reload?

Perhaps you need to disable autosuspend for the USB hub too. Try
echo -1 >/sys/module/usbcore/parameters/autosuspend
for i in /sys/bus/usb/devices/*/power/autosuspend; do echo -1 > $i; done
and see if that fixes the problem.

Similar Messages

No sound on flash videos on the internet after suspend and hibernate

I have this:
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller
Everytime I resume from suspend or hibernate with firefox open alongside with fully loaded flash videos, playing the videos doesn't produce any sound anymore. I need to restart firefox in order to make it work again..:(
Any ideas?
Thanks for the help in advance

I'm also having this problem. Xfmedia plays audio just fine before and after suspend/resume, but pandora.com and hulu.com in firefox do not. Also noticed that CPU usage skyrockets when trying to restart audio/video after resume in pandora/hulu. In hulu, video restarts, but audio does not.
Interestingly, CPU usage also spikes if I restart audio in Xfmedia after resume, but the CPU hog is firefox not Xfmedia and Xfmedia audio plays just fine. Have to close the hulu or pandora tab to get the CPU usage back to normal. Wondering if it's just a bug in flash for linux.
My hardware/software:
MSI PR201 laptop
Linux jims_laptop 2.6.30-ARCH #1 SMP PREEMPT Mon Jul 20 11:20:32 UTC 2009 i686 Intel(R) Core(TM)2 Duo CPU P7350 @ 2.00GHz GenuineIntel GNU/Linux
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
local/alsa-lib 1.0.20-1
An alternative implementation of Linux sound support
local/alsa-oss 1.0.17-1
OSS compatibility library
local/alsa-utils 1.0.20-2
An alternative implementation of Linux sound support
local/gstreamer0.10-bad-plugins 0.10.12-1 (gstreamer0.10-plugins)
GStreamer Multimedia Framework Bad Plugins (gst-plugins-bad)
local/flashplugin 10.0.22.87-1
Adobe Flash Player
local/firefox 3.5.1-1
Standalone web browser from mozilla.org

No more logging to access.log after suspend/resume

Hi.
After suspending (forced) and resuming a Managed Server in Weblogic (10.3.6), no more entries are added to access.log in the logs directory of said server. This happens when I use the Admin Console, and when I use WLST:
for serverRT in domainRuntimeService.getServerRuntimes():
      print 'Current status for '+ serverRT.getName() +': '+ serverRT.getState()
      print 'Suspending '+ serverRT.getName() +'...'
      serverRT.forceSuspend()
      print 'Resuming '+ serverRT.getName() +'...'
      serverRT.resume()
Has anybody encountered this as well, and found a way so resolve this?
FYI, I followed MOS Note 1113583.1 to disable buffering, but this doesn't help.
Regards,
Peter.

Yes, it seems to be a kernel bug. Previously, my wife used Windows for years and nothing like this happened. Now, she tells a lot about Linux systems :-)
An example of this very-ugly-workaround for somebody who'll find this topic struggling with the same problem:
$ cat /etc/pm/sleep.d/99_fix_time_shift
#!/bin/bash
# fixing https://bbs.archlinux.org/viewtopic.php?id=173487
case "$1" in
suspend)
date +%s > /tmp/suspend.log
resume)
was=`cat /tmp/suspend.log`
now=`date +%s`
# time shifts for 68 hours
if [ $now -gt `expr $was + 244800` ]; then
date -s "`date -R --date="-68 hours ago"`"
## sleep 30; ntpdate ntp.ubuntu.com
fi
esac
Last edited by shurup (2014-03-26 16:25:55)

Resume after suspend suspends again

Hi,
for the last two weeks I've been experiencing some weird ACPI behaviour. When I resume after suspending with pm-suspend my system immediately suspends again. Shortly before suspending again the screen blanks and shows a line like this
[ 98.602112] ACPI: Unable to dock!
After it suspended again, the system can be resumed normally.
The system is a X230 with a full disk encryption. The suspend is done by calling pm-suspend with acpid. For further power management I use laptop-mode-tools, but the problem persists even after disabling it. Furthermore the problem can be reproduced on battery as well as AC.
I tried looking around, but have only found people having similar problems on hibernate and never any satisfying solutions. Has anyone ever experienced this problem and found a solution?
The relevant dmesg output is
[ 98.139750] ACPI: Low-level resume complete
[ 98.139785] PM: Restoring platform NVS memory
[ 98.140189] Extended CMOS year: 2000
[ 98.140208] Enabling non-boot CPUs ...
[ 98.146952] Booting Node 0 Processor 1 APIC 0x1
[ 98.226464] CPU1 is up
[ 98.229850] Booting Node 0 Processor 2 APIC 0x2
[ 98.309586] CPU2 is up
[ 98.309636] Booting Node 0 Processor 3 APIC 0x3
[ 98.389393] CPU3 is up
[ 98.392736] ACPI: Waking up from system sleep state S3
[ 98.578985] ACPI: \_SB_.PCI0.LPC_.EC__.BAT1 - docking
[ 98.602112] ACPI: Unable to dock!
[ 98.695344] xhci_hcd 0000:00:14.0: >wake-up capability disabled by ACPI
[ 98.695354] xhci_hcd 0000:00:14.0: >power state changed by ACPI to D0
[ 98.695357] xhci_hcd 0000:00:14.0: >power state changed by ACPI to D0
[ 98.695504] ehci_hcd 0000:00:1a.0: >wake-up capability disabled by ACPI
[ 98.695511] ehci_hcd 0000:00:1a.0: >power state changed by ACPI to D0
[ 98.695514] ehci_hcd 0000:00:1a.0: >power state changed by ACPI to D0
[ 98.695835] ehci_hcd 0000:00:1d.0: >wake-up capability disabled by ACPI
[ 98.695842] ehci_hcd 0000:00:1d.0: >power state changed by ACPI to D0
[ 98.695845] ehci_hcd 0000:00:1d.0: >power state changed by ACPI to D0
[ 98.696233] sdhci-pci 0000:02:00.0: >MMC controller base frequency changed to 50Mhz.
[ 98.696841] PM: noirq resume of devices complete after 1.637 msecs
[ 98.696952] PM: early resume of devices complete after 0.084 msecs
[ 98.697001] xhci_hcd 0000:00:14.0: >power state changed by ACPI to D0
[ 98.697162] ehci_hcd 0000:00:1a.0: >power state changed by ACPI to D0
[ 98.697164] e1000e 0000:00:19.0: >irq 44 for MSI/MSI-X
[ 98.697168] ehci_hcd 0000:00:1d.0: >power state changed by ACPI to D0
[ 98.697177] xhci_hcd 0000:00:14.0: >power state changed by ACPI to D0
[ 98.697187] xhci_hcd 0000:00:14.0: >setting latency timer to 64
[ 98.697227] snd_hda_intel 0000:00:1b.0: >irq 47 for MSI/MSI-X
[ 98.697242] ahci 0000:00:1f.2: >setting latency timer to 64
[ 98.697433] ehci_hcd 0000:00:1a.0: >power state changed by ACPI to D0
[ 98.697442] ehci_hcd 0000:00:1a.0: >setting latency timer to 64
[ 98.697461] ehci_hcd 0000:00:1d.0: >power state changed by ACPI to D0
[ 98.697470] ehci_hcd 0000:00:1d.0: >setting latency timer to 64
[ 98.697511] i915 0000:00:02.0: >power state changed by ACPI to D0
[ 98.697514] i915 0000:00:02.0: >power state changed by ACPI to D0
[ 98.697520] i915 0000:00:02.0: >setting latency timer to 64
[ 98.724116] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off
[ 98.934829] usb 3-1.6: >reset high-speed USB device number 4 using ehci_hcd
[ 99.034359] ata2: SATA link down (SStatus 0 SControl 300)
[ 99.034447] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 99.035035] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 99.035039] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 99.035774] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 99.035777] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 99.036070] ata1.00: configured for UDMA/133
[ 99.041012] ata5: SATA link down (SStatus 0 SControl 300)
[ 99.061091] sd 0:0:0:0: >[sda] Starting disk
[ 99.231087] PM: resume of devices complete after 535.501 msecs
[ 99.231683] PM: Finishing wakeup.

Everyone is talking about systemd, but on RHEL 6 there is no systemd installed and also it is not supported. But I am still seeing the exact problem as described in the original question. This is on x230 lenovo.
Linux OS ver
Linux xxxxxxxxxxxxxxxxx 2.6.32-358.11.1.el6.x86_64 #1 SMP Wed May 15 10:48:38 EDT 2013 x86_64 x86_64 x86_64 GNU/Linux
But currently the os is using pm_utils to do shutdown, suspend and hibernate etc.,
I couldn't suspend, hibernate nor shutdown. system wakes up in all three modes.
Any help would be much appreciated.
Last edited by yru (2013-07-28 14:20:01)

[Solved] "cannot open display" after suspend/resume, possibly broadcom

Hey peoples,
[EDIT: I think my initial assumptions are incorrect, this issue seems to be occurring independently of whatever wifi driver I have loaded]
I'm finding that after suspend/resume my machine will not open any new windows. The windows that were already open continue to function. If I've left a terminal open, and attempt to open a new window I get the message:
[framps@localhost ~]$ firefox
Invalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyError: cannot open display: :0.0
I've found that removing the broadcom-wl driver from my system seems to fix the issue. I can't see anything particularly obvious in my dmesg. I think I need the broadcom-wl driver as I have not been able to get b43 or bcma to work for my machine.
[ 948.814261] cfg80211: World regulatory domain updated:
[ 948.814266] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 948.814269] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 948.814272] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 948.814275] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 948.814277] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 948.814280] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 949.404722] r8169 0000:0c:00.0 eth0: link down
[ 949.404741] r8169 0000:0c:00.0 eth0: link down
[ 949.404773] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 949.355635] PM: Syncing filesystems ... done.
[ 949.717960] PM: Preparing system for mem sleep
[ 949.851316] Freezing user space processes ... (elapsed 0.01 seconds) done.
[ 949.862059] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
[ 949.875377] PM: Entering mem sleep
[ 949.875472] Suspending console(s) (use no_console_suspend to debug)
[ 950.064255] xhci_hcd 0000:00:14.0: WARN Event TRB for slot 1 ep 0 with no TDs queued?
[ 950.064507] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 950.075138] sd 0:0:0:0: [sda] Stopping disk
[ 950.165918] ERROR @wl_notify_scan_status : Scan complete while device not scanning
[ 950.477845] i915 0000:00:02.0: power state changed by ACPI to D3hot
[ 950.551140] PM: suspend of devices complete after 676.056 msecs
[ 950.551485] PM: late suspend of devices complete after 0.342 msecs
[ 950.567669] r8169 0000:0c:00.0: wake-up capability enabled by ACPI
[ 950.581418] ehci_hcd 0000:00:1d.0: wake-up capability enabled by ACPI
[ 950.594384] ehci_hcd 0000:00:1a.0: wake-up capability enabled by ACPI
[ 950.620974] xhci_hcd 0000:00:14.0: wake-up capability enabled by ACPI
[ 950.634321] PM: noirq suspend of devices complete after 82.939 msecs
[ 950.634762] ACPI: Preparing to enter system sleep state S3
[ 950.730816] PM: Saving platform NVS memory
[ 950.736910] Disabling non-boot CPUs ...
[ 950.738461] smpboot: CPU 1 is now offline
[ 950.840631] smpboot: CPU 2 is now offline
[ 950.943831] smpboot: CPU 3 is now offline
[ 950.944231] Extended CMOS year: 2000
[ 950.945389] ACPI: Low-level resume complete
[ 950.945427] PM: Restoring platform NVS memory
[ 950.945811] Extended CMOS year: 2000
[ 950.945864] Enabling non-boot CPUs ...
[ 950.949268] smpboot: Booting Node 0 Processor 1 APIC 0x1
[ 950.963117] CPU1 is up
[ 950.966520] smpboot: Booting Node 0 Processor 2 APIC 0x2
[ 950.980330] CPU2 is up
[ 950.980386] smpboot: Booting Node 0 Processor 3 APIC 0x3
[ 950.994238] CPU3 is up
[ 950.997398] ACPI: Waking up from system sleep state S3
[ 951.471580] i915 0000:00:02.0: power state changed by ACPI to D0
[ 951.498111] xhci_hcd 0000:00:14.0: wake-up capability disabled by ACPI
[ 951.524753] ehci_hcd 0000:00:1a.0: wake-up capability disabled by ACPI
[ 951.551380] ehci_hcd 0000:00:1d.0: wake-up capability disabled by ACPI
[ 951.564744] nvidia 0000:01:00.0: power state changed by ACPI to D0
[ 951.591567] PM: noirq resume of devices complete after 120.295 msecs
[ 951.591837] PM: early resume of devices complete after 0.236 msecs
[ 951.591891] i915 0000:00:02.0: setting latency timer to 64
[ 951.591894] xhci_hcd 0000:00:14.0: setting latency timer to 64
[ 951.591968] mei 0000:00:16.0: irq 43 for MSI/MSI-X
[ 951.591983] ehci_hcd 0000:00:1a.0: setting latency timer to 64
[ 951.592037] ehci_hcd 0000:00:1d.0: setting latency timer to 64
[ 951.592108] ahci 0000:00:1f.2: setting latency timer to 64
[ 951.592119] snd_hda_intel 0000:00:1b.0: irq 46 for MSI/MSI-X
[ 951.594182] r8169 0000:0c:00.0: wake-up capability disabled by ACPI
[ 951.634511] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
[ 951.636110] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off
[ 951.796066] r8169 0000:0c:00.0 eth0: link down
[ 951.824070] Extended CMOS year: 2000
[ 951.831119] usb 3-1.3: reset full-speed USB device number 3 using ehci_hcd
[ 951.910921] ata5: SATA link down (SStatus 0 SControl 300)
[ 951.916168] btusb 3-1.3:1.0: no reset_resume for driver btusb?
[ 951.916171] btusb 3-1.3:1.1: no reset_resume for driver btusb?
[ 951.924226] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 951.926030] ata2.00: configured for UDMA/100
[ 951.981369] usb 4-1.6: reset high-speed USB device number 3 using ehci_hcd
[ 952.876326] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 952.877743] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 952.877747] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 952.877750] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[ 952.880489] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 952.880493] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 952.880496] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[ 952.881600] ata1.00: configured for UDMA/100
[ 952.893105] sd 0:0:0:0: [sda] Starting disk
[ 952.911681] PM: resume of devices complete after 1321.544 msecs
[ 952.912745] PM: Finishing wakeup.
[ 952.912748] Restarting tasks ... done.
[ 953.018321] video LNXVIDEO:00: Restoring backlight state
[ 953.018862] video LNXVIDEO:01: Restoring backlight state
[ 953.376503] r8169 0000:0c:00.0 eth0: link up
[ 953.376515] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Any help would be greatly appreciated. Thanks.
Last edited by frampy (2013-03-16 01:20:57)

It seems that the only option for my wifi card, BCM43228 is the proprietary broadcom-wl.
Can anyone suggest how I might be able to get any debugging information for this module? Maybe this driver is conflicting with something else on my system, as I can't find anyone else that is seeing this same issue.
Very frustrating, my machine is a Thinkpad Edge E530. Because I ordered from New Zealand there was no option to include the alternative Intel card and I was stuck with the broadcom. Apparently there's a whitelist on the BIOS aswell which will prevent me from installing another card.

[Solved]no sound after suspend/resume after kernel 3.9.2 upgrade

I don't know what to provide to help solve this problem. Leave me messages.Thank you!
Last edited by chu887 (2013-06-06 08:54:16)

johni wrote:
I got mine working!
First I commented out the module parameter from my /etc/modprobe.d//intel-hda-audio.conf:
#options snd-hda-intel model=dell-eq
Since it works without that now, I will probably remove the file.
Next, I went into alsamixer, and noticed a couple items not there before, turned down low:
"Speaker", and two "HeadPhone" mixers, both turned down almost off. I turned up the volume on the speaker, and was able to get sound from the speakers. The same worked for the headphone entries (I have two headphone jacks).
After I did this, it works better than before because I used to only have one working headphone jack.
Also, I confirmed sound is still working after suspend/resume for me.
Hopefully this will help one of you.
Thanks,the problem has been resolved by downgrade.
Sound is absolutely normal before I suspend/resume my system, volume is normal, not too large,not too little. But there's no sound at all after resume it . I guess it's probably to have something to do with our audio card - HDA intel, my computer is also a dell laptop( dell 1420 , 2007/2008, really old ).
My advice is : don't upgrade to kernel 3.9.2 ,it's an odd version( odd version is not stable).

Resume after suspend / upgrades

Hi all, I've been using arch for about half a year and I'm very satisfied with it. There is, however, one thing that I can't change/find in arch, that is "after which event my laptop resumes after suspend". Suspend (s2ram or default scripts, that were in the system) / resume work fine, but after every (almost every) kernel upgrade somehow "resume event trigger" changes. It becomes or "resume after lid is open" or "resume after lid is open _and_ any key is pressed". I want it to resume just after lid is open without pressing key, but I can't find where I can set it. Could someone help me, please? Thanks.
Sorry for my English, it's my third language.
About the system:
laptop is Sony Vaio vpcea3s1e;
Latest upgrades (kde 4.6.2/kernel 2.6.38);
Suspend is done by s2ram.
here is my /proc/acpi/wakeup:
Device S-state Status Sysfs node
P0PF S4 *disabled pci:0000:00:1e.0
USB1 S3 *disabled
USB2 S3 *disabled
USB3 S3 *disabled
USB4 S3 *disabled
USB5 S3 *disabled
USB6 S3 *disabled
USB7 S3 *disabled
HDEF S4 *disabled pci:0000:00:1b.0
RP01 S3 *disabled pci:0000:00:1c.0
PXSX S3 *disabled pci:0000:02:00.0
RP03 S3 *disabled pci:0000:00:1c.2
PXSX S3 *disabled pci:0000:04:00.0
EHC1 S3 *disabled pci:0000:00:1d.0
EHC2 S3 *disabled pci:0000:00:1a.0
RP06 S3 *disabled pci:0000:00:1c.5
PXSX S3 *disabled
PWRB S4 *enabled
It works exactly the same whether apcid is started, though.
and /etc/mkinitcpio.conf (HOOKS) :
HOOKS="base udev v86d autodetect pata scsi sata uresume filesystems "

Hi all, I've been using arch for about half a year and I'm very satisfied with it. There is, however, one thing that I can't change/find in arch, that is "after which event my laptop resumes after suspend". Suspend (s2ram or default scripts, that were in the system) / resume work fine, but after every (almost every) kernel upgrade somehow "resume event trigger" changes. It becomes or "resume after lid is open" or "resume after lid is open _and_ any key is pressed". I want it to resume just after lid is open without pressing key, but I can't find where I can set it. Could someone help me, please? Thanks.
Sorry for my English, it's my third language.
About the system:
laptop is Sony Vaio vpcea3s1e;
Latest upgrades (kde 4.6.2/kernel 2.6.38);
Suspend is done by s2ram.
here is my /proc/acpi/wakeup:
Device S-state Status Sysfs node
P0PF S4 *disabled pci:0000:00:1e.0
USB1 S3 *disabled
USB2 S3 *disabled
USB3 S3 *disabled
USB4 S3 *disabled
USB5 S3 *disabled
USB6 S3 *disabled
USB7 S3 *disabled
HDEF S4 *disabled pci:0000:00:1b.0
RP01 S3 *disabled pci:0000:00:1c.0
PXSX S3 *disabled pci:0000:02:00.0
RP03 S3 *disabled pci:0000:00:1c.2
PXSX S3 *disabled pci:0000:04:00.0
EHC1 S3 *disabled pci:0000:00:1d.0
EHC2 S3 *disabled pci:0000:00:1a.0
RP06 S3 *disabled pci:0000:00:1c.5
PXSX S3 *disabled
PWRB S4 *enabled
It works exactly the same whether apcid is started, though.
and /etc/mkinitcpio.conf (HOOKS) :
HOOKS="base udev v86d autodetect pata scsi sata uresume filesystems "

Resume after suspend with uvesafb

Hello. I have an install with lxde on my acer one. It did resume after suspend before I did install v86d and set the framebuffer. No with uvesafb and v86d I do have a nice-looking framebuffer but I'm not able to resume after suspend. All I get is a black screen. I suppose it doesn't load proper modules. What to do?
Jan

I'll post my /var/log/pm-suspend.log:
Initial commandline parameters: --quirk-none
Sat Jan 24 18:02:52 CET 2009: Running hooks for suspend.
/usr/lib/pm-utils/sleep.d/00auto-quirk suspend suspend: success.
/usr/lib/pm-utils/sleep.d/00logging suspend suspend: Linux acerone 2.6.28-ARCH #1 SMP PREEMPT Sun Jan 18 20:17:17 UTC 2009 i686 Intel(R) Atom(TM) CPU N270 @ 1.60GHz GenuineIntel GNU/Linux
Module Size Used by
i915 58500 2
drm 83752 3 i915
joydev 11712 0
uvcvideo 57736 0
compat_ioctl32 3072 1 uvcvideo
videodev 34176 1 uvcvideo
v4l1_compat 15364 2 uvcvideo,videodev
mmc_block 11012 0
psmouse 55828 0
iTCO_wdt 12836 0
iTCO_vendor_support 4996 1 iTCO_wdt
serio_raw 7172 0
sg 26804 0
i2c_i801 10896 0
i2c_core 22804 1 i2c_i801
pcspkr 4352 0
video 18576 0
output 4608 1 video
uhci_hcd 24592 0
ehci_hcd 36876 0
jmb38x_ms 11396 0
intel_agp 27580 1
agpgart 31572 3 drm,intel_agp
usbcore 136976 4 uvcvideo,uhci_hcd,ehci_hcd
sdhci_pci 9088 0
sdhci 17028 1 sdhci_pci
memstick 10652 1 jmb38x_ms
mmc_core 46876 2 mmc_block,sdhci
acer_wmi 16320 0
rfkill 11724 2 acer_wmi
wmi 7848 1 acer_wmi
evdev 11296 8
thermal 17180 0
processor 41388 3 thermal
fan 6276 0
snd_seq_oss 31872 0
snd_seq_midi_event 8192 1 snd_seq_oss
button 7824 0
battery 12036 0
snd_seq 49968 4 snd_seq_oss,snd_seq_midi_event
snd_seq_device 8332 2 snd_seq_oss,snd_seq
ac 6020 0
snd_hda_intel 411956 0
snd_hwdep 9092 1 snd_hda_intel
snd_pcm_oss 40320 0
snd_pcm 70020 2 snd_hda_intel,snd_pcm_oss
snd_timer 21384 2 snd_seq,snd_pcm
snd_page_alloc 10120 2 snd_hda_intel,snd_pcm
snd_mixer_oss 16512 1 snd_pcm_oss
snd 50852 9 snd_seq_oss,snd_seq,snd_seq_device,snd_hda_intel,snd_hwdep,snd_pcm_oss,snd_pcm,snd_timer,snd_mixer_oss
soundcore 8160 1 snd
arc4 3712 2
ecb 4608 2
ath5k 100864 0
mac80211 161184 1 ath5k
led_class 5508 2 acer_wmi,ath5k
cfg80211 31760 2 ath5k,mac80211
r8169 33924 0
mii 6528 1 r8169
rtc_cmos 12332 0
rtc_core 17564 1 rtc_cmos
rtc_lib 4480 1 rtc_core
ext2 66184 1
mbcache 8708 1 ext2
uvesafb 28388 1
cn 9120 2 uvesafb
sd_mod 26904 2
ata_piix 23300 1
ata_generic 6788 0
pata_acpi 6016 0
libata 158240 3 ata_piix,ata_generic,pata_acpi
scsi_mod 102036 3 sg,sd_mod,libata
total used free shared buffers cached
Mem: 1543124 250256 1292868 0 2712 44088
-/+ buffers/cache: 203456 1339668
Swap: 0 0 0
success.
/usr/lib/pm-utils/sleep.d/00powersave suspend suspend: success.
/usr/lib/pm-utils/sleep.d/01grub suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/11netcfg suspend suspend: /bin/stty: standard input: Invalid argument
success.
/usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/55NetworkManager suspend suspend: success.
/usr/lib/pm-utils/sleep.d/75modules suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/90chvt suspend suspend: success.
/usr/lib/pm-utils/sleep.d/90clock suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend: success.
/usr/lib/pm-utils/sleep.d/95led suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/98smart-kernel-video suspend suspend: success.
/usr/lib/pm-utils/sleep.d/99video suspend suspend: kernel.acpi_video_flags = 0
success.
Sat Jan 24 18:02:54 CET 2009: performing suspend
Sat Jan 24 18:03:20 CET 2009: Awake.
Sat Jan 24 18:03:20 CET 2009: Running hooks for resume
/usr/lib/pm-utils/sleep.d/99video resume suspend: success.
/usr/lib/pm-utils/sleep.d/98smart-kernel-video resume suspend: success.
/usr/lib/pm-utils/sleep.d/95led resume suspend: not applicable.
/usr/lib/pm-utils/sleep.d/94cpufreq resume suspend: success.
/usr/lib/pm-utils/sleep.d/90clock resume suspend: not applicable.
/usr/lib/pm-utils/sleep.d/90chvt resume suspend: success.
/usr/lib/pm-utils/sleep.d/75modules resume suspend: success.
/usr/lib/pm-utils/sleep.d/55NetworkManager resume suspend: success.
/usr/lib/pm-utils/sleep.d/49bluetooth resume suspend: not applicable.
/usr/lib/pm-utils/sleep.d/11netcfg resume suspend: /bin/stty: standard input: Invalid argument
success.
/usr/lib/pm-utils/sleep.d/01grub resume suspend: not applicable.
/usr/lib/pm-utils/sleep.d/00powersave resume suspend: success.
/usr/lib/pm-utils/sleep.d/00logging resume suspend: success.
/usr/lib/pm-utils/sleep.d/00auto-quirk resume suspend: success.
Sat Jan 24 18:03:20 CET 2009: Finished.

[XFCE]Keyboard layout config sometimes gets reset after suspend/resume

After I got suspend/resume working thanks to the help here, I have still another little problem with it: After suspend/resume the keyboard layout configuration in the corresponding xfce-panel plugin is sometimes reset to US. The keyboard layout should be Russian/German with switching the layouts with LCtrl+LShift. In the xorg.conf everything is fine, but it seems to be disregarded:
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "de,ru"
Option "XkbVariant" ",winkeys"
Option "XkbOptions" "grp:ctrl_shift_toggle"
EndSection
The settings that I make in the panel-applet via its configuration dialogue work though, but they sometimes get reset after a suspend/resume.
The XFCE session is started via following command in ~/.xinitrc:
exec ck-launch-session dbus-launch xfce4-session
Thanks for any hint,
PhotonX

I see. Then you should maybe add debug output to check whether the script is run at all and if yes, where it fails. Like
button/lid)
echo "lid action caught" >> /home/lid.log
case "$3" in
close)
logger 'LID closed'
# Suspend and lock the screen
/usr/sbin/pm-suspend &
DISPLAY=:0.0 su -c - miki /usr/bin/slimlock
echo "lid closed" >> /home/lid.log
open)
logger 'LID opened'
# Set the keyboard layout again on IT
setxkbmap it
echo "lid opened" >> /home/lid.log
logger "ACPI action undefined: $3"
echo "something wrong happened" >> /home/lid.log
esac
and then check /home/lid.log after lid close&open.

OS X - Fix for wifi disconnect after suspend/resume

OS X - Fix for wifi disconnect after suspend/resume
I've purchased a Mac recently and since upgrading to Maverick have been having some problem with wifi after suspend/resume. Looking into the issue, I've found this thread: https://discussions.apple.com/thread/5495375 and some people have reported that turning off bluetooth did fix the issue.
For my case, this was not possible, so I've tried to make a little fix, that disable bluetooth on suspend and enable it on wake, but with a 10 seconds delay, in order to let the wifi connect successfully.
Here is my github repo for anyone to look at the code: https://github.com/Setsuna666/osx-wifibtfix
Here is the latest version of the fix, which include an uninstall script: https://github.com/Setsuna666/osx-wifibtfix/archive/v1.0.2.zip
If you have any questions or issues, please post it here so it can be easier for me to keep track of.

Installed properly this time:
It appears to work, when I resume from sleep the Bluetooth icon is off (gray) and wifi connects, after 10s Bluetooth icon comes on again.
Here is the correct output:
Antzcrashing-MacBook-Air:osx-wifibtfix-1.0.3 Antzcrashing$ sudo bash install.sh
Password:
Installing Wifi/BT fix by Setsuna666...
Downloading SleepWatcher...
Downloading file from http://www.bernhard-baehr.de/sleepwatcher_2.2.tgz...
% Total    % Received % Xferd Average Speed   Time Time     Time Current
                                 Dload Upload Total   Spent    Left Speed
100 43385 100 43385 0     0 28567 0 0:00:01 0:00:01 --:--:-- 28580
Extracting SleepWatcher...
x ./sleepwatcher_2.2/
x ./sleepwatcher_2.2/config/
x ./sleepwatcher_2.2/ReadMe.rtf
x ./sleepwatcher_2.2/sleepwatcher
x ./sleepwatcher_2.2/._sleepwatcher.8
x ./sleepwatcher_2.2/sleepwatcher.8
x ./sleepwatcher_2.2/sources/
x ./sleepwatcher_2.2/sources/Makefile
x ./sleepwatcher_2.2/sources/._sleepwatcher.c
x ./sleepwatcher_2.2/sources/sleepwatcher.c
x ./sleepwatcher_2.2/sources/sleepwatcher.xcodeproj/
x ./sleepwatcher_2.2/sources/sleepwatcher.xcodeproj/bb.pbxuser
x ./sleepwatcher_2.2/sources/sleepwatcher.xcodeproj/bb.perspectivev3
x ./sleepwatcher_2.2/sources/sleepwatcher.xcodeproj/project.pbxproj
x ./sleepwatcher_2.2/config/de.bernhard-baehr.sleepwatcher-20compatibility-localu ser.plist
x ./sleepwatcher_2.2/config/de.bernhard-baehr.sleepwatcher-20compatibility.plist
x ./sleepwatcher_2.2/config/rc.sleep
x ./sleepwatcher_2.2/config/rc.wakeup
Creating dependencies for SleepWatcher...
Installing SleepWatcher...
Copying SleepWatcher configuration...
cp: /Users/Jeffrey/Documents/OS: No such file or directory
cp: Stuff/MAC/osx-wifibtfix-1.0.3/extra//rc.sleep: No such file or directory
cp: /Users/Jeffrey/Documents/OS: No such file or directory
cp: Stuff/MAC/osx-wifibtfix-1.0.3/extra//rc.wakeup: No such file or directory
Starting SleepWatcher...
Downloading blueutil...
Downloading file from http://www.frederikseiffert.de/blueutil/download/blueutil.dmg...
% Total    % Received % Xferd Average Speed   Time Time     Time Current
                                 Dload Upload Total   Spent    Left Speed
100 33343 100 33343 0     0 11945 0 0:00:02 0:00:02 --:--:-- 11942
Mounting blueutil disk image...
Checksumming Driver Descriptor Map (DDM : 0)…
Driver Descriptor Map (DDM : 0): verified   CRC32 $0275F970
Checksumming Apple (Apple_partition_map : 1)…
Apple (Apple_partition_map : 1): verified   CRC32 $1779B6BD
Checksumming disk image (Apple_HFS : 2)…
          disk image (Apple_HFS : 2): verified   CRC32 $920D4FD8
Checksumming (Apple_Free : 3)…
                    (Apple_Free : 3): verified   CRC32 $00000000
verified   CRC32 $AFAB3FAE
/dev/disk2              Apple_partition_scheme
/dev/disk2s1            Apple_partition_map
/dev/disk2s2            Apple_HFS                        /Volumes/blueutil
Installing blueutil...
Finished installing Wifi/BT fix
Now try to suspend and resume your Mac, your wifi should connect without issue

[BUG] Jumbo frames issues after suspend/resume

I have a 2.66Ghz MacBookPro5,1 which I recently upgraded to Snow Leopard. It's connected to a gigabit LAN and makes use of jumbo frames (MTU 9000).
Everything was working flawlessly under Leopard, but since the upgrade to 10.6, I've noticed some very strange networking behavior. Essentially, networking goes AWOL as soon as it tries to transfer big data chunks *after a suspend/resume*. Remote sessions (ssh), file tranfers (ftp/afp) are affected.
AFAICT, small packets work (eg, the output of "uptime" in a ssh session works just fine), but anything "big" (copying a large file over ftp or afp) hangs the connection. It seems that reducing the jumbo frame max size (using "ifconfig en0 mtu <whatever smaller than the previous setting>") temporarily fixes the issue, until the next hang.
This problem only happens after suspend/resume. Upon cold boot, everything works just fine, so I'm suspecting a driver issue.
The only difference between previously "working just fine" situation and the current issue is the upgrade from 10.5 to 10.6. I should mention I'm running in 64bit mode.
HTH
Message was edited by: thibaut

If you have found a verified and reproducible bug then report it here: Feedback. The Discussions is not a bug reporting venue. Apple engineers do not read the Discussions.
If you want help resolving a problem that is the purpose of the Discussions, but you need to post a question.

X or GDM dies after suspend/resume (Nvidia card)

For a while now (about a month, I think), X seems to crash after suspend/resume and I end up back on the GDM login screen.
The problem is intermittent, but I'd say it happens about 50% of the time. As can be seen in the log below, after a while a new gdm-x-session replaces the one that was running before suspend.
Any ideas? I'm stuck.
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: got pause for 13:77
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: got pause for 13:78
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: got pause for 226:0
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: got pause for 13:68
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: got pause for 13:64
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: got pause for 13:79
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: got pause for 13:67
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: got pause for 13:65
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: got pause for 13:66
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) config/udev: removing device X10 WTI RF receiver mouse
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) evdev: X10 WTI RF receiver mouse: Close
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) UnloadModule: "evdev"
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: releasing fd for 13:78
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (EE) systemd-logind: failed to release device: Did not receive a reply. Possible causes include: the remote application did not send a reply, the messag
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: got resume for 13:77
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: Failed to close file descriptor: Could not close fd 23
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: got resume for 226:0
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) NVIDIA(0): Setting mode "nvidia-auto-select+0+0"
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) NVIDIA(0): configuration option may not be set correctly. When the
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) NVIDIA(0): Config Options in the README.
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) NVIDIA(GPU-0): Display (Medion MD30422PV (DFP-0)) does not support NVIDIA 3D
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) NVIDIA(GPU-0): Vision stereo.
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: got resume for 13:68
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: got resume for 13:64
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: got resume for 13:79
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: got resume for 13:67
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: got resume for 13:65
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: got resume for 13:66
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) config/udev: removing device X10 WTI RF receiver
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) evdev: X10 WTI RF receiver: Close
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (II) config/udev: removing device X10 WTI RF receiver mouse
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (II) evdev: X10 WTI RF receiver mouse: Close
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (II) UnloadModule: "evdev"
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (II) config/udev: removing device X10 WTI RF receiver
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (II) evdev: X10 WTI RF receiver: Close
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (II) UnloadModule: "evdev"
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (II) config/udev: Adding input device X10 WTI RF receiver mouse (/dev/input/mouse2)
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (II) No input driver specified, ignoring this device.
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (II) This device may have been added with another device file.
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (II) config/udev: Adding input device X10 WTI RF receiver mouse (/dev/input/event14)
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (**) X10 WTI RF receiver mouse: Applying InputClass "evdev pointer catchall"
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (II) systemd-logind: returning pre-existing fd for /dev/input/event14 13:78
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (II) Using input driver 'evdev' for 'X10 WTI RF receiver mouse'
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (**) X10 WTI RF receiver mouse: always reports core events
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (**) evdev: X10 WTI RF receiver mouse: Device: "/dev/input/event14"
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (--) evdev: X10 WTI RF receiver mouse: Vendor 0xbc7 Product 0x6
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (--) evdev: X10 WTI RF receiver mouse: Found 9 mouse buttons
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (--) evdev: X10 WTI RF receiver mouse: Found relative axes
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (--) evdev: X10 WTI RF receiver mouse: Found x and y relative axes
May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (II) evdev: X10 WTI RF receiver mouse: Configuring as mouse

I waited a couple of days, tried suspending again and now things work as they should, or at least they appear to.
I have no idea what has changed.

Gigabit NIC reverts to 100mbs after suspend/resume

My motherboard has an integrated Realtek Gigabit ethernet controller, using the r8169 driver. See lspci output below.
It works fine, except after a suspend-resume cycle, it reverts to 100Mb/s rather than 1000Mb/s. It still works in 100mbs mode, just significantly slower. I can manually fix it back to GigE via "ethtool -s eth0 speed 1000". But I'd prefer to not have to do this.
Is there somewhere I should hard-code the ethtool settings, or should I modify a resume pm script? Or is there another solution?
Thanks!
Matt
ethtool output after suspend/resume:
ethtool eth0
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000033 (51)
Link detected: yes
lspsi output:
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)
Subsystem: Giga-byte Technology GA-EP45-DS5 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: 32 bytes
Interrupt: pin A routed to IRQ 45
Region 0: I/O ports at d000 [size=256]
Region 2: Memory at e9110000 (64-bit, prefetchable) [size=4K]
Region 4: Memory at e9100000 (64-bit, prefetchable) [size=64K]
[virtual] Expansion ROM at e9120000 [disabled] [size=64K]
Capabilities: <access denied>
Kernel driver in use: r8169
Kernel modules: r8169

Hi Matt,
same problem here. I've had this for several months now. Usually I don't even notice, because I don't transfer large files all that regularly.
A quick look on the kernel.org bug tracker turned this up: https://bugzilla.kernel.org/show_bug.cgi?id=10130 Seems like this is a fairly old issue.
ethtool gives me the exact same output as you've posted. I'm using the same chip and driver, but different motherboard:
# lspci -s 02:00.0 -v
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)
Subsystem: ASUSTeK Computer Inc. Device 82c6
Flags: bus master, fast devsel, latency 0, IRQ 42
I/O ports at e800 [size=256]
Memory at fbfff000 (64-bit, non-prefetchable) [size=4K]
Memory at faff0000 (64-bit, prefetchable) [size=64K]
Expansion ROM at fbfc0000 [disabled] [size=128K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 01
Capabilities: [b0] MSI-X: Enable- Count=2 Masked-
Capabilities: [d0] Vital Product Data
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Virtual Channel
Capabilities: [160] Device Serial Number 00-00-00-00-ec-10-68-81
Kernel driver in use: r8169
Kernel modules: r8169

[SOLVED] X dies after suspend+resume, dropping me into LXDM

If I do a sudo systemctl suspend and then resume, the computer comes back to life with LXDM, suggesting to me that it failed to bring up X properly and everything in that session died with it.
I'm not quite sure where to start looking with this one, any ideas?
Last edited by linduxed (2015-04-12 12:58:46)

I waited a couple of days, tried suspending again and now things work as they should, or at least they appear to.
I have no idea what has changed.

Losing (closed) wifi network informations after suspend/resume.

I get some trouble with MacOS X airport support and suspend/resume on my WIFI network (non airport access point based : I have a linksys wifi/modem/router).
For security reason my network is closed (no ESSID diffusion). Each time my computer (MacBookPro3,1 - Mac OS X 10.5.1 up-to-date) resume from suspend I am no more connected, and worse the system do not use anymore the information I registered in the network settings apps (ESSID, WEP key) : the network is no more visible, and even if the network is remembered in the list of previously visited network, I am forced to retype everything (ESSID, WEP key) to be able to be connected again.
When I change my network setup to get an open one (with ESSID diffusion) then it works : I can suspend the computer, resume it an I am connected again without doing anything.
This is very annoying, since I am not the main user of the computer (main one do not understand anything about network settings) and that I need my network to be closed (no ESSID diffusion).
With other 4 others different computers (PowerBook Titanium using Max OS X 10.4 / PowerBook Aluminium using Mac OS X 10.3 or 10.4 / MacBookPro using Linux / Dell Latitude using Linux) everything work as expected.
Any ideas where I can find information on how to fix this (stupid) behavior ?
BTW, I tested the following with my base configured for 802.11b, 802.11g and automatic detection.

I am not offering a fix other than to say don't use a closed network.
I asy this because having a closed network does not offer any network security. A hacker can easily see your network using tools that anyone can download from the internet. Having a closed network can interfere with the efficiency of all wifi network in your area. As your neighbours may be unaware of your network and start broadcasting on the same channel as you. Then you would both have issues.
WEP encrypton offers no real security either as this too can be cracked sometimes in minutes using tools that anyone can download from the internet.
The only network security you should consider using is WPA/WPA2.

Instant USB after suspend-resume/hibernate-resume

Similar Messages

Maybe you are looking for