Bug 13261 - rtl8187 and associated modules prevent machine from suspend/hybernate
Summary: rtl8187 and associated modules prevent machine from suspend/hybernate
Status: CLOSED DUPLICATE of bug 11887
Alias: None
Product: Drivers
Classification: Unclassified
Component: network-wireless (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_network-wireless@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-07 04:43 UTC by Gian Paolo Mureddu
Modified: 2010-03-05 18:39 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.27.21-170.2.56.fc10
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Gian Paolo Mureddu 2009-05-07 04:43:26 UTC
I currently seeing this problem with my laptop (Toshiba Satellite A215-S7437), which has the RTL8187B USB dongle chip for the internal wireless. In turn the rtl8187 driver is used for it, and the mac80211 module (and cfg80211). I ran a few tests with the machine and it appears that while the driver module (and associated modules) are loaded, this prevents the machine from properly suspending/hybernate. The only way I have tested this is by stopping the wireless connection and deactivating wireless entirely from within NetworkManager, and then manually unloading the modules (rmmod {rtl8187,mac80211,cfg80211}) in that order. If I then suspend/hybernate the machine it does without any issues, however if I fail to unload the modules (or so I would think) the machine does not suspend. I lack the knowledge to exactly know what is preventing the machine from properly suspending/hybernatin while the driver is loaded, all I know is that when I try to suspend/hybernate the machine with the driver loaded the process starts (shuts down the monitor, but never fully goes into suspension, gets unresponsive and I have to power-cycle the machine).

If there is any further information I could provide, I'd love to do so, I only need to know how to obtain said information.
Comment 1 John W. Linville 2010-03-05 18:39:09 UTC

*** This bug has been marked as a duplicate of bug 11887 ***

Note You need to log in before you can comment on or make changes to this bug.