| Summary: | After updating, Fedora 15 Beta hangs up during boot. Can be recovered with hitting a key, then boots normally | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jirka Daněk <juraad> | ||||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 15 | CC: | gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, wdhammond, yaneti, yann | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | kernel-2.6.38.8-32.fc15 | Doc Type: | Bug Fix | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2011-06-25 19:13:43 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Attachments: |
|
||||||||||
|
Description
Jirka Daněk
2011-04-29 12:45:59 UTC
Created attachment 495770 [details]
/var/log/boot.log
One more thing. These hangups also appeared when I tried to update my Fedora 15 Beta instalation USB. I did not report it, because I read afterwards, that updating live USB is not supported and is an easy way to hell. So it has to be unrelated to the kernel version, because kernel is not updated when runnig live USB Yet another thing. The bug I wrote could be related is a mistake. I was pointed not to that bug, but to page that is the search result for bugs related to cgroup, sorry Sounds like https://bugzilla.kernel.org/show_bug.cgi?id=15289 You can try disabling AMD C1E support in then BIOS as a workaround. Yes, that is it. I tried your fix and some other mentioned in the kernel bugzilla Disabling AMD C1E in BIOS will fix it for me. My standard kernel line is "kernel /boot/vmlinuz-2.6.38.3-18.fc15.x86_64 ro root=UUID=4b152f7e-0493-40ae-b1e9-2dc41e73b6e7 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=cz-lat2" + " rhgb quiet" booting with AMD C1E on and with various suggested parameters kernel line + " debug" will hang up several times, but not in kernel, like hpet and irqpool below kernel line + " debug nomsi" will hang up twice, but it will recover itself without pressing any keys. But this also hung up during shutdown and that need the helping key in the end kernel + " debug maxcpus=1" will work without error kernel + " acpi_skip_timer_override" will work without error kernel + " hpet=disable" & kernel + " irqpool" will hang up in kernel, after initializing USBs, in which moment key is not enough and power button has to be pushed. Then hangs up few more times which gets corrected by key kernel + " idle=mwait" works fine, no hang ups kernel + " ioacpi" hangs up My HW profile is at smolt.org as f8c35d19-a61d-4f3c-83ba-ca00bed65130, I have CPU0: AMD Phenom(tm) II X4 905e Processor stepping 02 and Gigabyte 790XTA-UD4 at kernel bugzilla, there is link to bug 648837 which is filled against Fedora 14 Beta. So should that bug be updated to include Fedora 15 and this bug be marked as a duplicate? This is not due to having C1E enabled if it worked before. Did it start with the 2.6.38.4 kernel? There was a bug introduced in that one that has since been fixed in the pending 2.6.38.6 update. Look at the "flags" line in /proc/cpuinfo and see if it contains the string "arat". If it is present, boot an older kernel and see if that goes away. kernel-2.6.38.6-26.rc1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/kernel-2.6.38.6-26.rc1.fc15 Please test the update and report whether it fixes this bug. kernel-2.6.38.6-26.rc1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report. I have updated to [jirka@private ~]$ uname -a Linux private 2.6.38.6-27.fc15.x86_64 #1 SMP Sun May 15 17:23:28 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux and the problem still persits. Strangely, when I rebooted from 2.6.38.5 after installing the update, the first boot went well. But when I tried three more times, it got stuck at least once each time. (In reply to comment #10) > I have updated to > > [jirka@private ~]$ uname -a > Linux private 2.6.38.6-27.fc15.x86_64 #1 SMP Sun May 15 17:23:28 UTC 2011 > x86_64 x86_64 x86_64 GNU/Linux > > and the problem still persits. > > Strangely, when I rebooted from 2.6.38.5 after installing the update, the first > boot went well. But when I tried three more times, it got stuck at least once > each time. Please attach the contents of /proc/cpuinfo after booting the latest update. (You can keep it from stalling by moving the mouse pointer around and/or hitting the shift key repeatedly.) Created attachment 500171 [details]
/proc/cpuinfo on 2.6.38.6-27.fc15.x86_64
Should be fixed in : https://admin.fedoraproject.org/updates/kernel-2.6.38.8-32.fc15 I just installed Fedora 15 on my wife's Sony Viao and now the boot process hangs at right after "Started SYSV: Emable monthly update of Smolt." Switching to a terminal window and performing "yum -y update smolt" does not fix the problem. During install, the GUI was trashed so after switching to a terminal I installed RPM Fusion repos and the Kmod nvidia drivers. The next boot and each subsequent boot stops as above. Is there hope to rescue this installation or must I re-install Fedora 14? (In reply to comment #14) > I just installed Fedora 15 on my wife's Sony Viao and now the boot process > hangs at right after "Started SYSV: Emable monthly update of Smolt." Switching > to a terminal window and performing "yum -y update smolt" does not fix the > problem. > And does it continue if you keep hitting the "shift' key? Does that machine have an AMD processor in it? |