[BusyBox 0001460]: module autoloading dont work

bugs at busybox.net bugs at busybox.net
Mon Aug 13 11:17:59 UTC 2007


A NOTE has been added to this issue. 
====================================================================== 
http://busybox.net/bugs/view.php?id=1460 
====================================================================== 
Reported By:                clausmuus
Assigned To:                BusyBox
====================================================================== 
Project:                    BusyBox
Issue ID:                   1460
Category:                   Kernel Module Support
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             08-12-2007 13:23 PDT
Last Modified:              08-13-2007 04:17 PDT
====================================================================== 
Summary:                    module autoloading dont work
Description: 
I have the same problem as 0001350
I Use version 1.6.0

To locate the problem, I have replaced the command modprobe by a shell
script that dump the command line parameters in a file and calls than the
modprobe command.
By this I can see that the kernel call the modprobe command as follow:
  modprobe -p -- symbol:MODULNAME_attach
where by MODULNAME will be replaced by the name of the module to load.

====================================================================== 

---------------------------------------------------------------------- 
 vda - 08-13-07 04:17  
---------------------------------------------------------------------- 
Please give more info: which kernel version, what do you do to trigger
autoload, which commandline is passed to modprobe (give exact example, not
"MODULNAME"), what busybox modprobe says with this command line, what
"standard" modprobe says (and does - do "strace -o modprobe.log modprobe
..." and attach log file to the bug report).

On my system, /bin/modprobe is a link to busybox and everything seems to
work. That's why I need more info from you. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
08-12-07 13:23  clausmuus      New Issue                                    
08-12-07 13:23  clausmuus      Status                   new => assigned     
08-12-07 13:23  clausmuus      Assigned To               => BusyBox         
08-12-07 13:24  clausmuus      Issue Monitored: clausmuus                    
08-13-07 04:17  vda            Note Added: 0002655                          
======================================================================




More information about the busybox-cvs mailing list