[Bug 279798] Re: [intrepid] cannot suspend with module rtl8187 loaded

[Hélio Nunes]

The elegant solution is create a new config file like
/etc/pm/config.d/01suspend_modules with SUSPEND_MODULES="rtl8187" in it.

But here (Semp Toshiba IS 1454, jaunty, 2.6.28-*-generic)  I suffer with
some kernel oops using this solution. I think the problem is the order
of unloading. So I still use the script I posted long time ago, but now
renamed it to /etc/pm/sleep.d/54_rtl8187_workaround, 54_ because, in
jaunty, we have /usr/lib/pm-utils/sleep.d/55NetworkManager (55).

To check the order of unload/reload, look /var/log/pm-suspend.log. You
will see that it works in an numeric order. Ascendant order when
suspending, descendant order when waking up:

[...]
Fri Aug 28 13:25:35 BRT 2009: Running hooks for suspend.
[...]
/usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend: not applicable.
/etc/pm/sleep.d/54_rtl8187_workaround suspend suspend: success. <---
/usr/lib/pm-utils/sleep.d/55NetworkManager suspend suspend: success.
/usr/lib/pm-utils/sleep.d/75modules suspend suspend: success.
[...]
Fri Aug 28 13:25:39 BRT 2009: performing suspend
Fri Aug 28 19:13:40 BRT 2009: Awake.
Fri Aug 28 19:13:40 BRT 2009: Running hooks for resume
[...]
/usr/lib/pm-utils/sleep.d/75modules resume suspend: success.
/usr/lib/pm-utils/sleep.d/55NetworkManager resume suspend: success.
/etc/pm/sleep.d/54_rtl8187_workaround resume suspend: success. <---
/usr/lib/pm-utils/sleep.d/49bluetooth resume suspend: not applicable.
[...]

As you can see, the difference between my 54_rlt8187_workaround and
SUSPEND_MODULES="rtl8187" (ie. 75modules) is just that: unload rtl8187
before 55NetworkManager, so I have a disconnection, and NetworkManager
goes sleep disconnected.

You should try the elegant solution and see if it works for you. If not,
try the order I propose (54). A note: do it all inside /etc/pm/ since
updates overwrite /usr/lib/pm-utils/.

-- 
[intrepid] cannot suspend with module rtl8187 loaded
https://bugs.launchpad.net/bugs/279798
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.