Description of problem: SEGFAULT during boot in libdevmapper.so.1.0.2 Problem occurs on the first (and all subsequent) boot attempts after a successful Fedora 9 installation onto a clean hard disk. Version-Release number of selected component (if applicable): libdevmapper.so.1.0.2 How reproducible: 100% on a hand-full of attempts. Steps to Reproduce: 1. Install Fedora 9; pick a PATA drive to fresh-install to with complete formatting and default system suggested partition layout. Encryption is enabled on the system partition according to the anaconda checkbox for that. 2. Customize package selection somewhat adding in many of the optional packages. 3. System installs packages, ejects DVD, displays installation complete dialog; reboot, get the SEGV error every time. Actual results: SEGV crash a few seconds into the boot process. Expected results: Successful boot. Additional info: System is: * P5K Deluxe motherboard with P35 chipset + ICH9R with an added JMicron SATA/IDE motherboard controller chip ; * sde is 120GB PATA WD1200 boot drive with default layout with encryption enabled. The BIOS has this listed as the first/primary boot hard disc, and there is no problem with the BIOS booting to GRUB and GRUB working to select the GRUB configured kernel/initrd etc. The crash occurs after GRUB proceeds to boot the only / default kernel system which was configured by the just completed Fedora 9 install. At no point between GRUB and the CRASH has it asked for the encryption password which was specified during Fedora Install using Anaconda. * sdc has a pre-existing data partition on a 500GB drive not selected for Fedora9 installation / mounting, though it did show up in the anaconda list of detected drives/partitions. * mapper/mpath0 is gnu knows what; anaconda said it had an unreadable partition table; this was NOT selected for labeling/initialization or use during install. * There are a total of four 500GB Maxtor SATA drives attached to motherboard SATA ports between the ICH9R's four SATA ports and the couple of ports the JMicron chip adds. One of these is presumably the sdc listed above, the rest may be lumped into mapper/mpath0 or whatever; they weren't explicitly listed in anaconda during install. * The following bugzilla bugs seem to show similar weaknesses / crashes on boot, though I am posting this distinctly since my system varies somewhat from theirs and I expect my backtrace et. al. data is potentially unique / distinct. https://bugzilla.redhat.com/show_bug.cgi?id=446669 https://bugzilla.redhat.com/show_bug.cgi?id=431778
Created attachment 306237 [details] screen shot of crash console log + backtrace
Created attachment 306238 [details] screen shot of grub kernel / initrd parameters which subsequently crash on boot
Created attachment 306239 [details] screen shot of crash console log + backtrace (2nd distinct crash)
Created attachment 306240 [details] screen shot of crash console log + backtrace (3rd distinct crash)
*** This bug has been marked as a duplicate of 446669 ***