Description of problem: In my logs, and at boot, I can see a lot of error messages procuded by visor* modules (see below). In /etc/modprobe.d, I have a file "visor.conf" with: blacklist visor blacklist visorchannel So, it seems that the blacklist command is not honoured on our current Cauldron :-/ the logs: ------> visorutil: module is from the staging directory, the quality is unknown, you have been Dec 09 19:33:44 brenva.mountains.net kernel: visorutil: module is from the staging directory, the quality is unknown, you have been Dec 09 19:33:44 brenva.mountains.net kernel: visorutil: module is from the staging directory, the quality is unknown, you have been Dec 09 19:33:44 brenva.mountains.net kernel: visorutil: module is from the staging directory, the quality is unknown, you have been Dec 09 19:33:44 brenva.mountains.net kernel: visorutil: module is from the staging directory, the quality is unknown, you have been Dec 09 19:33:44 brenva.mountains.net kernel: visorutil: module is from the staging directory, the quality is unknown, you have been Dec 09 19:33:44 brenva.mountains.net kernel: visorutil: module is from the staging directory, the quality is unknown, you have been Dec 09 19:33:44 brenva.mountains.net kernel: visorutil: module is from the staging directory, the quality is unknown, you have been Dec 09 19:33:44 brenva.mountains.net kernel: visorutil: module is from the staging directory, the quality is unknown, you have been Dec 09 19:33:44 brenva.mountains.net kernel: visorutil: module is from the staging directory, the quality is unknown, you have been Dec 09 19:33:44 brenva.mountains.net kernel: visorutil: module is from the staging directory, the quality is unknown, you have been Dec 09 19:33:44 brenva.mountains.net kernel: visorutil: module is from the staging directory, the quality is unknown, you have been Dec 09 19:33:44 brenva.mountains.net kernel: visorchannel: module is from the staging directory, the quality is unknown, you have b Dec 09 19:33:44 brenva.mountains.net kernel: visorchannel: Unknown symbol visor_memregion_create (err -2) Dec 09 19:33:44 brenva.mountains.net kernel: visorchannel: Unknown symbol visor_memregion_destroy (err -2) Dec 09 19:33:44 brenva.mountains.net kernel: visorchannel: Unknown symbol visor_memregion_get_nbytes (err -2) Dec 09 19:33:44 brenva.mountains.net kernel: visorchannel: Unknown symbol visor_memregion_write (err -2) Dec 09 19:33:44 brenva.mountains.net kernel: visorchannel: Unknown symbol visor_memregion_resize (err -2) Dec 09 19:33:44 brenva.mountains.net kernel: visorchannel: Unknown symbol visor_memregion_get_physaddr (err -2) Dec 09 19:33:44 brenva.mountains.net kernel: visorchannel: Unknown symbol visor_memregion_create_overlapped (err -2) Dec 09 19:33:44 brenva.mountains.net kernel: visorchannel: Unknown symbol visor_memregion_read (err -2) Dec 09 19:33:44 brenva.mountains.net kernel: visorchannel: Unknown symbol unisys_spar_platform (err -2) Dec 09 19:33:44 brenva.mountains.net kernel: visorchannel: module is from the staging directory, the quality is unknown, you have b Dec 09 19:33:44 brenva.mountains.net kernel: visorchannel: module is from the staging directory, the quality is unknown, you have b Dec 09 19:33:44 brenva.mountains.net kernel: visorchannel: module is from the staging directory, the quality is unknown, you have b Dec 09 19:33:44 brenva.mountains.net kernel: visorchannel: module is from the staging directory, the quality is unknown, you have b Dec 09 19:33:44 brenva.mountains.net kernel: visorchannel: module is from the staging directory, the quality is unknown, you have b Dec 09 19:33:44 brenva.mountains.net kernel: visorchannel: Unknown symbol visor_memregion_create (err -2) Dec 09 19:33:44 brenva.mountains.net kernel: visorchannel: Unknown symbol visor_memregion_destroy (err -2) Dec 09 19:33:44 brenva.mountains.net kernel: visorchannel: Unknown symbol visor_memregion_get_nbytes (err -2) Dec 09 19:33:44 brenva.mountains.net kernel: visorchannel: Unknown symbol visor_memregion_write (err -2) Dec 09 19:33:44 brenva.mountains.net kernel: visorchannel: Unknown symbol visor_memregion_resize (err -2) Dec 09 19:33:44 brenva.mountains.net kernel: visorchannel: Unknown symbol visor_memregion_get_physaddr (err -2) Dec 09 19:33:44 brenva.mountains.net kernel: visorchannel: Unknown symbol visor_memregion_create_overlapped (err -2) Dec 09 19:33:44 brenva.mountains.net kernel: visorchannel: Unknown symbol visor_memregion_read (err -2) Dec 09 19:33:44 brenva.mountains.net kernel: visorchannel: Unknown symbol unisys_spar_platform (err -2) Dec 09 19:33:44 brenva.mountains.net kernel: visorchannel: Unknown symbol visor_memregion_create (err -2) Dec 09 19:33:44 brenva.mountains.net kernel: visorchannel: Unknown symbol visor_memregion_destroy (err -2) Reproducible: Steps to Reproduce:
Still there with kernel-3.19.0-desktop
Assignee: bugsquad => tmbWhiteboard: (none) => MGA5TOO
You have not blocked visorutil wich is the first module spamming... and it probably contains code that loads s the visorchannel module, something the modprobe blacklist wont prevent
Thanks, funnily enough, I only sorted this out very recently :) The visor chain of modules is triggered by visorbus and visorhba, which goes into initrd. So even a blacklist a posteriori does not work, one has to regenerate the initrd with a proper blacklist lists, or wait for the next kernel to debug the blacklist :) Here a working blacklist for visor: cat modprobe.d/visor.conf blacklist visorbus blacklist visorhba blacklist visorchipset blacklist visoruislib blacklist visor blacklist visorutil blacklist visorchannel Don't know if we need to include it though.
Mass-reassigning all bugs with "kernel" in the Source RPM field that are assigned to tmb, to the kernel packagers group, because tmb is currently MIA.
Assignee: tmb => kernel