After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 555269 - should respect blacklisted modules on reload
should respect blacklisted modules on reload
Status: RESOLVED NOTGNOME
Product: gnome-power-manager
Classification: Deprecated
Component: general
2.24.x
Other All
: Normal normal
: ---
Assigned To: GNOME Power Manager Maintainer(s)
GNOME Power Manager Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2008-10-06 17:45 UTC by Oliver Grawert
Modified: 2008-11-25 17:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description Oliver Grawert 2008-10-06 17:45:20 UTC
Please describe the problem:
currently the modreload() function in pm-utils ignores blacklisted modules, that exposes problems with hardware where two valid modules exist for the same device and only one is blacklisted.

Steps to reproduce:
1. have hardware that can be drive by two different modules, i.e. a madwifi driven wlan card that can use ath5k (new free driver) or ath_pci, assume ath_pci (madwifi) provides features needed that ath5k doesnt provide yet.
2. blacklist ath5k to not be used for the device in an /etc/modprobe.d/blacklist-ath file
3. note that everything works fine on boot with this setup, suspend and resume, notice that ath5k suddenly got loaded on resume, superseding ath_pci


Actual results:
the wrong module gets used on resume

Expected results:
expected would be the blacklist being respected and thus the module that's blacklisted not being used

Does this happen every time?
it happens every suspend/resume cycle

Other information:
adding -b to the modprobe command in modreload() fixes this problem (see man modprobe)
Comment 1 Martin Pitt 2008-11-25 17:36:32 UTC
Please report this in bugzilla.freedesktop.org against pm-utils, together with the patch. Thanks!