Description of problem: The behavior below began with the latest kernel versions, the ones that changed the naming convention. Fc6 to F7 Restart Hangs Both Ways When I logout and do a restart to boot from one OS to the other the computer hangs after selecting the OS in Grub. If I shut down and then start up I have no problem. This does not happen if I restart and select the older kernel versions. Version-Release number of selected component (if applicable): vmlinuz-2.6.22.1-33.fc7 vmlinuz-2.6.22.1-32.fc6 How reproducible: Every restart into these kernels. Additional info: # Relevant lines in Grub Below: #boot=/dev/hda default=0 timeout=8 splashimage=(hd0,0)/boot/grub/splash.xpm.gz # hiddenmenu title Fedora Core (2.6.22.1-32.fc6) root (hd0,0) kernel /boot/vmlinuz-2.6.22.1-32.fc6 ro root=LABEL=/12 iommu=noaperture rhgb quiet initrd /boot/initrd-2.6.22.1-32.fc6.img title Fedora Core (2.6.20-1.2962.fc6) root (hd0,0) kernel /boot/vmlinuz-2.6.20-1.2962.fc6 ro root=LABEL=/12 iommu=noaperture rhgb quiet initrd /boot/initrd-2.6.20-1.2962.fc6.img title F7 Latest root (hd0,6) kernel /boot/vmlinuz-2.6.22.1-33.fc7 ro root=LABEL=/1 rhgb quiet iommu=noaperture initrd /boot/initrd-2.6.22.1-33.fc7.img title F7 root (hd0,6) kernel /boot/vmlinuz-2.6.21-1.3194.fc7 ro root=LABEL=/1 rhgb quiet iommu=noaperture initrd /boot/initrd-2.6.21-1.3194.fc7.img ################################################## #############3 The panic screen lists what I believe are memory registers with hex content. Also a list of library files. I will try to transcribe this when I next reboot.
I have since deduced that this is a problem specific to F7. This behavior on restart is associated with the 2.6.22.1-33.fc7 kernel as it does not happen with the prior kernel. I have discovered that the restart hang also occurs when you restart F7 from this same kernel version, ie: lets say you update or change a parameter that requires reboot to take effect. Anyway I did copy down some lines from the panic screen. ############################################## F7 kernel version = 2.6.22.1-33.fc7 kernel panic on restart, the following is transcribed from screen excluding memory register addresses. Call Trace: [...] pci_fixup_device+0x8c/0x9a [...] pci_init+0x12/0x2b [...] kernel_init+0x206/0x370 [...] child_rip+0xa/0x12 [...] acpi_ds_init_one_object+0x0/0x7c [...] kernel_init+0x0/0x370 [...] child_rip+0x0/0x370 Code: 00 00 00 00 00 ............. RIP [...] quirk_usb_early_handoff+0x0/0x385 RSP <...> CR2 0000000000 end of screen output ###################################################
Please boot in 50-line mode (add vga=ask to the kernel command line, then select 80x50 mode) and take a picture of the screen with a digital camera. Attach that to the bug report.
Created attachment 161935 [details] Screen shot of boot error message vga mode 80x50 As requested
I also have such problem on all 2.6.22 kernels, on my x86_64 machine. Other machines running i686 kernel work fine with each upgrade. I have to use the last working kernel 2.6.21-1.3228.fc7.
adding "reboot=cold" to the kernel command line should fix this but it's really just a workaround. Full list of reboot modes for i386: warm cold bios hard smp x86_64: warm cold triple bios kbd force
My custom compiled kernel has no problem with restarts. It is based on the 2.6.22.1-33 kernel. Jim
Hello, I'm reviewing this bug as part of the kernel bug triage project, an attempt to isolate current bugs in the Fedora kernel. http://fedoraproject.org/wiki/KernelBugTriage I am CC'ing myself to this bug and will try and assist you in resolving it if I can. There hasn't been much activity on this bug for a while. Could you tell me if you are still having problems with the latest kernel? If the problem no longer exists then please close this bug or I'll do so in a few days if there is no additional information lodged.
This bug is no longer an issue for me. I am now using the 2.6.23.12-52 F7 kernel and have no problems with reboot.
Great news - thanks for filing originally. Will close CURRENTRELEASE.