Description of problem: Installation of Fedora 8 crashes with "loader received SIGSEGV!" immediately after the media check. Version-Release number of selected component (if applicable): Fedora 8. Works with Fedora 8 Test 3. How reproducible: Every time on affected hardware. My hardware is a new HP laptop. Steps to Reproduce: 1. Launch installer with known good media 2. Select default/standard options 3. Skip media check Actual results: Crashes, allowing reboot with "loader received SIGSEGV!" Expected results: Continues with install, launching X Windows. Additional info: Work around by installing from Fedora 8 Test 3 and then upgrading. This seems significant because the problem was introduced between F8T3 and F8. However, since the crash is a complete install show stopper, I propose "high" severity. A coworkers with similar hardware (new HP laptop) had the same experience, but didn't save the backtrace. This problem is similar to Bug 385281, Bug 375171, Bug 352861 with the same loader SIGSEGV message at the same point of the install. These may or may not be duplicates as the backtrace is quite different. Here's the backtrace and last output from the virtual terminals: -------------------------------------------------------------- loader received SIGSEGV! Backtrace: [0x401ace] [0x527fc0] [0x54b2c4] [0x41177b] [0x4120a7] [0x402a19] [0x519b09] [0x4001e9] ------------- VT3 ------------- 21:18:42 INFO : Loading SELInux policy 21:18:43 INFO : getting ready to spawn shell now 21:18:43 INFO : modules to insert ide-cd 21:18:43 INFO : load module set done 21:18:43 INFO : modules to insert 21:18:43 INFO : load module set done 21:18:43 INFO : modules to insert 21:18:43 INFO : load module set done -------------- VT4 -------------- <7>SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts <5>audit(1196889523.415:2) policy loaded auid=4294967295
Does booting with 'linux nopcmcia' help?
It worked. At the Welcome to Fedora 8 screen, I hit tab and entered: > vmlinux initrd=initrd.img nopcmcia when it got to the media test, I skipped it and unlike before it came back with Running anaconda... and then X started. Care to illuminate me on how you knew/guessed this would work? Is there somewhere to read up on how to use the backtrace?
*** This bug has been marked as a duplicate of 374311 ***