Red Hat Bugzilla – Bug 88960
creating custom boot disk with e1000 module included causes segfault in /sbin/loader
Last modified: 2007-04-18 12:53:05 EDT
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225 Description of problem: when including the intel e1000 kernel module in a custom boot disk (i.e. not using a driver disk, but placing the e1000 driver directly into the modules.cgz in the initrd, etc), install runs, delegating to /sbin/loader, and loader crashes immediately with a signal 11 (segmentation fault). removing the e1000 module from the boot disk resolves the issue. having an e1000 card physically installed is entirely unnecessary in order to reproduce this bug. this methodology works perfectly for any other network card module we have tried (tg3, 3c59x, etc), only the e1000 seems to cause a problem. Version-Release number of selected component (if applicable): shipped boot disks How reproducible: Always Steps to Reproduce: 1. start with the default boot disk 2. place the e1000 kernel module into the modules.cgz inside the initrd 3. update the pcitable, modules.dep, module-info accordingly. 4. boot 5. cry Actual Results: /sbin/loader crashes with signal 11 (segmentation fault) Expected Results: it should work. Additional info: description is sufficient.
Did you use spaces or tabs in the module-info file?
all the boot disks i've examined that we've created have tabs, identically the same formatting to the original module-info text.
The code all works fine for me here with our disks. If you put your disk somewhere that I can pull it down and take a look at it, I'll try to take a look at it.
Closing due to inactivity - please reopen if you have additional information to add.