Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#34598 - [vhba-module] Module gets loaded on boot for no good reason

Attached to Project: Community Packages
Opened by Philipp (hollunder) - Thursday, 04 April 2013, 10:40 GMT
Last edited by Balló György (City-busz) - Saturday, 14 December 2013, 01:05 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After boot:
$ lsmod | grep vhba
vhba 7454 0
scsi_mod 110744 5 vhba,usb_storage,libata,sd_mod,sr_mod

$ systemctl is-enabled cdemu-daemon.service
disabled

$ ls /etc/modules-load.d/


There's no good reason why this module should be loaded automatically. The above commands show that cdemu is disabled and the module is not loaded explicitely, hence it shouldn't be loaded at all.

It should be loaded explicitly by a user or on demand, not automatically on boot.


Additional info:
* package version(s)
20120422-19

* config and/or log files etc.


Steps to reproduce:
Install vhba-module, reboot.
This task depends upon

Closed by  Balló György (City-busz)
Saturday, 14 December 2013, 01:05 GMT
Reason for closing:  Works for me
Comment by Dave Reisner (falconindy) - Thursday, 04 April 2013, 12:55 GMT
I think the "loaded explicitly by a user" was fulfilled when you installed the package. Nothing should be loading this module unless it's been explicitly configured by you. It has no modaliases and it ships with no modules-load.d rule.

Why is it a bug that this module is loaded when you explicitly installed the package?
Comment by Balló György (City-busz) - Saturday, 14 December 2013, 01:04 GMT
I can't reproduce the problem.

Loading...