lose sleep/suspend after {Update Pack=3, kernel=3.0.0}?

[TomRoche]

Just thought I'd post this to help anyone else who might be debugging this problem, and in hope that I'll get a ping from someone after this is resolved:

My box

Code: Select all

$ inxi -F -n -Nx
System:    Kernel: 3.0.0-1-amd64 x86_64 (64 bit, gcc: 4.5.3) 
           Desktop Gnome 2.30.2 Distro: Linux Mint Debian Edition
Machine:   Mobo: System76 model: Pangolin Performance version: panp5 Bios: Phoenix version: 1.02.22 date: 04/06/2009
CPU:       Dual core Intel Core2 Duo CPU T6500 (-MCP-) cache: 2048 KB flags: (lm nx sse sse2 sse3 sse4_1 ssse3) bmips: 8377.36 
           Clock Speeds: 1: 1200.00 MHz 2: 1200.00 MHz
Graphics:  Card: nVidia G98M [GeForce G 105M] bus-ID: 01:00.0 
           X.Org: 1.10.4 drivers: nouveau (unloaded: vesa,fbdev) Resolution: 1280x800@60.0hz 
           GLX Renderer: Rasterizer GLX Version: 2.1 Mesa 7.10.3 Direct Rendering: Yes
Network:   Card-1: Realtek RTL8111/8168B PCI Express Gigabit Ethernet controller 
           driver: r8169 ver: 2.3LK-NAPI port: 4000 bus-ID: 06:00.0
           IF: eth1 state: down speed: 10 Mbps duplex: half 
           Card-2: Intel WiFi Link 5100 driver: iwlagn ver: in-tree: bus-ID: 02:00.0
           IF: wlan0 state: up 

formerly had no problems either going to or returning from sleep or suspend. This failed after applying LMDE Update Pack 3, which moved me from kernel=2.6.39-2 to kernel=3.0.0. This appears to be due to a bug in Intel wireless code (tracked in debian here).

Workaround:

• boot to kernel=2.6.39-2 (in GRUB)
• wait for a fix in a kernel version > 3.0.0

If anyone has a better workaround, please let me know. Similarly, when a kernel is available via LMDE that has a fix for this, please let me know.

[ej64]

The bug reports says:

When iwlagn is not loaded, or is configured(I means select enable
wireless in network manager), suspend to memory works as
expected; when iwlagn is loaded but not configured, suspend
to memory will fail.

So if it's disabled anyway in network manager (not configured) so why don't you blacklist iwlagn (or now iwlwifi) in /etc/modprobe.d/blacklist.conf ? Or take out the card or disable wifi within your bios (if it's onboard) ...

[TomRoche]

Code: Select all

http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2316#c0
> When iwlagn is not loaded, or is configured(I means select enable
> wireless in network manager), suspend to memory works as
> expected; when iwlagn is loaded but not configured, suspend
> to memory will fail.

So if it's disabled anyway in network manager (not configured) so why don't you blacklist iwlagn (or now iwlwifi) in /etc/modprobe.d/blacklist.conf ? Or take out the card or disable wifi within your bios (if it's onboard)

The problem is that, while I always want to be able to suspend, currently, I regularly move between wired and wireless ethernet. At home (in a dense urban neighborhood) I'm currently only using wired; I disable wireless because otherwise NM keeps asking me to enter credentials for OP's wireless. I have a long bus commute; fortunately the transit system provides wireless, so I enable it there. At work (this is, to me, the weird part) where I'm a contractor, I have wired access but not wireless, so, again, I disable wireless.

I haven't tested to see if suspend works when wireless is enabled (I should). My point is that, I'd prefer not to hafta think about it: my Fn-F4-pressing muscles are much quicker than my brain :-(