Description of problem: During boot process, it looks like modprobe abends with null pointer. This began after updates from last week. I get the message "started udev" then the last part of a stack dump. I am sometimes able to complete the boot by trying to abort (ctl-c, or ctl-x) the module. I have captured the dmesg from a boot that completed and will attach it. Version-Release number of selected component (if applicable): Linux version 2.6.19-1.2895.fc6 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 146753 [details] dmesg log
What did I do wrong here? I put this out last weekend, but no one but me has looked at it. I am not strong on Linux, so do not want to go stumping around and make the problem worse. If nothing else, just let me know how to back out the last update to modprobe, as that version works.
This is fixed in Linux 2.6.19.3 and will be in the next Fedora kernel update. Plase report back if that doesn't fix the problem.
*** Bug 226903 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 223656 ***