| Summary: | monitor remains on when the system is halted | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Francesco Tapparo <tapparo> | ||||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 15 | CC: | gansalmon, harald, itamar, johannbg, jonathan, kernel-maint, lpoetter, madhu.chinakonda, matt.coffey.1983, metherid, mschmidt, mwc, notting, plautrba | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2012-07-11 17:51:08 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
Francesco Tapparo
2011-07-02 17:47:47 UTC
Does "sync && poweroff -f" work any better? What is the kernel version? Do you use Fedora kernels, or do you build your own? interestingly, "sync && poweroff -f" does not work any better: the monitor still remains on. I use official fedora kernels, my current kernel is: Linux mizar 2.6.38.8-32.fc15.i686.PAE #1 SMP Mon Jun 13 19:55:27 UTC 2011 i686 i686 i386 GNU/Linux Another information: I tried booting in the fedora 15 and fedora 14 dvd, went to the text console and typed "halt -p". The bug appeared in those versions too. Suspension correctly work (tried in my current fedora 15 system). Francesco Then it's not systemd. Reassigning to kernel. Boot with the "rhgb quiet" parameters removed from the kernel command line. Try to poweroff again. What are the last lines written on the screen? The problem must be hardware-specific, so please attach the outputs of "dmesg" and "lspci -nnvvv". I started the pc after having removed rhgb quiet, then executed "poweroff". The last lines are: ACPI: preparing to enter system sleep state S5 disabling non boot BPU power down some lines before them I've seen some suspect logs: ext4-fs: (dm-0): remounted opts:(null) disabling swaps detaching loop devices detaching dm devices not all dm devices detached 1 left detaching dm devices not all dm devices detached 1 left and after that the system renounced to unmount a unspecified dm device Created attachment 511440 [details]
lspci
Created attachment 511441 [details]
dmesg
clarification: it was "disabling non boot CPU", not "disabling non boot BPU" Created attachment 511442 [details]
lspci
Looks similar to this report from Carsten Emde: https://lkml.org/lkml/2011/4/2/41 Is this still happening with the 2.6.40.x kernel updates in F15? (In reply to comment #11) > Is this still happening with the 2.6.40.x kernel updates in F15? Unfortunately yes: it still happens in F15 with the current kernel: [cesco@mizar ~]$ uname -a Linux mizar 2.6.40.6-0.fc15.i686.PAE #1 SMP Tue Oct 4 00:44:38 UTC 2011 i686 i686 i386 GNU/Linux Still happening with 2.6.43/3.3? (Apologies for the repeated questions) Fedora 15 has reached it's end of life as of June 26, 2012. As a result, we will not be fixing any remaining bugs found in Fedora 15. In the event that you have upgraded to a newer release and the bug you reported is still present, please reopen the bug and set the version field to the newest release you have encountered the issue with. Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered. Thank you for taking the time to file a report. We hope newer versions of Fedora suit your needs. I'm using fedora 17 now and the problem persists. |