kmod-maint December 2013

kmod-maint@lists.fedoraproject.org

1 participants
6 discussions

[Bug 922201] New: rmmod confused by built-ins
by Red Hat Bugzilla 16 Jun '14

16 Jun '14

Product: Red Hat Enterprise Linux 7 https://bugzilla.redhat.com/show_bug.cgi?id=922201 Bug ID: 922201 Summary: rmmod confused by built-ins Product: Red Hat Enterprise Linux 7 Version: 7.0 Component: kmod Severity: medium Priority: medium Assignee: kay(a)redhat.com Reporter: bmr(a)redhat.com CC: gansalmon(a)Gmail.com, itamar(a)ispbrasil.com.br, jonathan(a)jonmasters.org, kernel-maint(a)redhat.com, kmod-maint(a)lists.fedoraproject.org, madhu.chinakonda(a)gmail.com, msivak(a)redhat.com Depends On: 922187 +++ This bug was initially created as a clone of Bug #922187 +++ Description of problem: Attempting to rmmod something that's not actually built as a module now gives a slightly confusing error: # rmmod loop libkmod: kmod_module_get_holders: could not open '/sys/module/loop/holders': No such file or directory Error: Module loop is in use Previously rmmod from module-init-tools gave a still vague but better "not found" message: # rmmod ext2 ERROR: Module ext2 does not exist in /proc/modules Version-Release number of selected component (if applicable): kmod-* How reproducible: 100% Steps to Reproduce: 1. compile something that can be built as a module as a built-in 2. rmmod $thing Actual results: # rmmod loop libkmod: kmod_module_get_holders: could not open '/sys/module/loop/holders': No such file or directory Error: Module loop is in use Which isn't really true: it's not in use, it's simply built in to vmlinuz so unloading makes no sense. Expected results: modprobe does the right thing: # modprobe -r loop FATAL: Module loop is builtin. Additional info: I know rmmod is the low-level tool and users should be using modprobe -r (or just not messing with this in the first place.. :) but knowledge of modprobe to load and rmmod to unload seems much more widespread among admins and the current behaviour looks at first like a kernel bug (if you didn't realise that there are paths directories missing in /sys/modules/$thing and the module name isn't present in /proc/modules you might think some refcount was broken etc.). --- Additional comment from Bryn M. Reeves on 2013-03-15 13:12:04 EDT --- Error is slightly different from 0:12-1.fc18 but same basic problem: # rmmod loop rmmod: ERROR: could not open '/sys/module/loop/holders': No such file or directory rmmod: ERROR: Module loop is in use -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=NR8Odg50eP&a=cc_unsubscribe

1 9

[Bug 958340] New: mlx4_en module not being loaded automatically
by Red Hat Bugzilla 16 Mar '14

16 Mar '14

Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=958340 Bug ID: 958340 Summary: mlx4_en module not being loaded automatically Product: Fedora Version: 18 Component: kmod Severity: unspecified Priority: unspecified Assignee: kmod-maint(a)lists.fedoraproject.org Reporter: jdy(a)cryregarder.com QA Contact: extras-qa(a)fedoraproject.org CC: jonathan(a)jonmasters.org, kmod-maint(a)lists.fedoraproject.org, msivak(a)redhat.com, vpavlin(a)redhat.com Category: --- This may be related to: http://www.novell.com/support/kb/doc.php?id=7010836 and https://bugs.launchpad.net/maas/+bug/1115710 For a MT26448 dual port 10gb ethernet card: 03:00.0 Ethernet controller: Mellanox Technologies MT26448 [ConnectX EN 10GigE, PCIe 2.0 5GT/s] (rev b0) the driver, mlx4_en, is not being loaded automatically. The mlx4_core module is being loaded. after doing a manual modprobe mlx4_en, the devices come up perfectly. Suggestion on novell site is to force the load in /etc/modprobe.d. Software: kmod-12-3.fc18.x86_64 kmod-libs-12-3.fc18.x86_64 Linux r3 3.8.8-202.fc18.x86_64 #1 SMP Wed Apr 17 23:25:17 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 10

[Bug 907581] New: [abrt] kmod-10-1.fc18: elf_get_mem: Process /usr/bin/kmod was killed by signal 6 (SIGABRT)
by Red Hat Bugzilla 05 Feb '14

05 Feb '14

Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=907581 Bug ID: 907581 Summary: [abrt] kmod-10-1.fc18: elf_get_mem: Process /usr/bin/kmod was killed by signal 6 (SIGABRT) Product: Fedora Version: 18 Component: kmod Severity: unspecified Priority: unspecified Reporter: bug-zilla(a)o2.pl Version-Release number of selected component: kmod-10-1.fc18 Additional info: backtrace_rating: 4 cmdline: /sbin/depmod -a 3.7.4-204.fc18.x86_64 crash_function: elf_get_mem executable: /usr/bin/kmod kernel: 3.7.2-204.fc18.x86_64 remote_result: NOTFOUND uid: 0 var_log_messages: Feb 4 19:30:56 localhost abrt[12775]: Saved core dump of pid 12774 (/usr/bin/kmod) to /var/spool/abrt/ccpp-2013-02-04-19:30:56-12774 (3887104 bytes) Truncated backtrace: Thread no. 1 (7 frames) #4 elf_get_mem at libkmod/libkmod-elf.c:207 #5 elf_get_uint at libkmod/libkmod-elf.c:142 #6 kmod_elf_new at libkmod/libkmod-elf.c:315 #7 kmod_module_get_symbols at libkmod/libkmod-module.c:2458 #8 depmod_load_symbols at tools/depmod.c:1543 #9 depmod_load at tools/depmod.c:1733 #10 do_depmod at tools/depmod.c:2751 -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 3

[Bug 1046654] New: kmod-16 is available
by Red Hat Bugzilla 03 Jan '14

03 Jan '14

https://bugzilla.redhat.com/show_bug.cgi?id=1046654 Bug ID: 1046654 Summary: kmod-16 is available Product: Fedora Version: rawhide Component: kmod Keywords: FutureFeature, Triaged Assignee: kmod-maint(a)lists.fedoraproject.org Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: jonathan(a)jonmasters.org, kmod-maint(a)lists.fedoraproject.org, msivak(a)redhat.com, vpavlin(a)redhat.com Latest upstream release: 16 Current version/release in Fedora Rawhide: 15-1.fc21 URL: http://kernel.org/pub/linux/utils/kernel/kmod/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 1

[Bug 1045545] New: fedora 20 does not detect rts5139 sd card reader
by Red Hat Bugzilla 20 Dec '13

20 Dec '13

https://bugzilla.redhat.com/show_bug.cgi?id=1045545 Bug ID: 1045545 Summary: fedora 20 does not detect rts5139 sd card reader Product: Fedora Version: 20 Component: kmod Severity: medium Assignee: kmod-maint(a)lists.fedoraproject.org Reporter: singhprook(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: jonathan(a)jonmasters.org, kmod-maint(a)lists.fedoraproject.org, msivak(a)redhat.com, vpavlin(a)redhat.com Description of problem:Fedora 20 does not detect rts5139 sdcard driver Version-Release number of selected component (if applicable):realtek rts5139 How reproducible:easy Steps to Reproduce: 1.lsusb detects card 2.modprobe rts5139 gives fatal error, module not found 3.kmod-staging not available for fedora 20. worked fine in fedora 19 Actual results:Bus 002 Device 005: ID 0bda:0139 Realtek Semiconductor Corp. RTS5139 Card Reader Controller modprobe: FATAL: Module rts5139 not found. Expected results: should work as in fedora 19 Additional info:lenovo corei5 laptop 64bit -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 1

[Bug 1040105] New: rtl8187se not compiled
by Red Hat Bugzilla 10 Dec '13

10 Dec '13

https://bugzilla.redhat.com/show_bug.cgi?id=1040105 Bug ID: 1040105 Summary: rtl8187se not compiled Product: Fedora Version: 19 Component: kmod Severity: medium Assignee: kmod-maint(a)lists.fedoraproject.org Reporter: ggkraemer(a)cox.net QA Contact: extras-qa(a)fedoraproject.org CC: jonathan(a)jonmasters.org, kmod-maint(a)lists.fedoraproject.org, msivak(a)redhat.com, vpavlin(a)redhat.com Description of problem: '/sbin/modprobe r8187se' fails in FC19 (r8187se not found). r8187se source is not being compiled; however, the kmod staging source is contained in 'linux-3.11/drivers/staging/rtl8187se' Version-Release number of selected component (if applicable): kernel 3.11.7-200.fc19.x86_64 kernel 3.11.8-200.fc19.x86_64 kernel 3.11.9-200.fc19.x86_64 kernel 3.11.10-200.fc19.x86_64 How reproducible: Update kernel from 3.11.9-200.fc19.x86_64 to 3.11.10-200.fc19.x86_64. Steps to Reproduce: 1. Use a laptop that has the following WIFI hardware operating properly with FC19, kernel 3.11.9-200.fc19.x86_64: lspci | grep Realtek 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8187SE Wireless LAN Controller (rev 22) 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02) 2. Update kernel from 3.11.9-200.fc19.x86_64 to 3.11.10-200.fc19.x86_64. 3. Reboot laptop. 4. Wifi is now inoperative. '/sbin/modprobe r8187se' fails (r8187se can not be found). Actual results: '/sbin/modprobe r8187se' fails (r8187se is not found). Expected results: r8187se.ko should be built, installed in proper location, and available to detect the WIFI using the following command (as root): /sbin/modprobe r8187se Additional info: If I download the kernel source and compile the rtl8187se source code and perform the following steps (as root), the WIFI works : mkdir /lib/modules/$(uname -r)/kernel/drivers/staging/rtl8187se cp r8187se.ko /lib/modules/$(uname -r)/kernel/drivers/staging/rtl8187se/ /sbin/depmod -a /sbin/modprobe r8187se -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

kmod-maint December 2013