Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: When attempting to install F12, the installation always hangs on my PC. The place where the installation stops proceeding varies with each attempt. It seems to occur during a drive access and the drive light stays on after the hang. The computer that I am installing onto has an existing BIOS RAID 1 array. This array is detected properly by anaconda. After the installation stops proceeding, I am able to switch to other virtual consoles. After a few minutes, messages like the following appear in output of the dmesg command: INFO: task pdflush:29 blocked for more than 120 seconds. INFO: task anaconda:333 blocked for more than 120 seconds. INFO: task kjournald:1819 blocked for more than 120 seconds. Each INFO message is followed by four lines with a lot of hex numbers and then a call trace. Version-Release number of selected component (if applicable): kernel-2.6.31.5-127.fc12.x86_64 How reproducible: happens every time Steps to Reproduce: 1. Attempt to install F12 from the x86_64 DVD. 2. 3. Actual results: The OS installation process hangs at a different time each attempt. Expected results: The OS installation should complete. Additional info: The computer is a Dell Optiplex 960. The chipset is Intel Q45 Express. The same situation occurs with both the regular installation and the installation with the basic video driver. When the installation hangs, you have to force the computer to turn off by holding down the power button for several seconds.
I generated a re-spin of F12 with kernel-2.6.32.9-70.fc12.x86_64. Alas, the problem persists.
When installing F13, I recognized the same symptoms as described in this bug. I looked at /proc/mdstat and was able to determine that a resync was going on. When the resync finished, the installation completed normally. *** This bug has been marked as a duplicate of bug 576749 ***