the shutdown process hangs on the laptop HP TX2 1165ea. No matter the system was shut down by a command line like 'shutdown -h now' or by the menu item. Version-Release number of selected component (if applicable): $ uname -a Linux localhost.localdomain 2.6.31.1-56.fc12.x86_64 #1 SMP Tue Sep 29 16:16:22 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux $ yum list | grep initscripts initscripts.x86_64 9.00-1 @rawhide How reproducible: shut the system down Actual results: displays the log message "power down." at upper left of the screen. And hangs without switching power off. Expected results: power off the system. Additional info:
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This also applies to the HP (Pavilion) TX2500 tablet PC in the last couple of days. The next time I tried to boot it, the boot failed, too, showing only a black screen. I had to hard power down (again) and on next boot it finally booted fine. I'll note that I recently switched to using mesa-dri-drivers-experimental to obtain DRI for my ATI Radeon HD 3200 card.
Could anyone clueful give me a hint as to where I should start looking for this? Kernel source, upstart, or initscripts? I'll try to write a patch if someone can point me in the right direction.
That is, yes, whenever I shut down, it always takes me to a black screen with small white text reading "Power down."
If the kernel power down doesn't, that's a kernel bug. You might try different kernel versions to see if a particular one works.
This behavior is, AFAICR, new with the latest kernel release. However, it seems not to be the kernel itself because all three of the kernels I have in place behave the same way. So I suspect it has to do with the ancillary updates installed at about the same time. I updated to the -174 kernel on December 26. But I don't keep complete enough records to identify them, although I suppose it's in my system logs somewhere.
Hi, I have the same issue on an uptodate F12 install (not tainted) and its default *PAE* 2.6.31.9-174 kernel. With i686 kernel shutdown and reboot work and I even get the icon for my battery status back (telling me my battery is dead which I already know :). This is a laptop: compaq presario 2100. I'm attaching lspci -nv, and message from both bootups. If you need something else let me know. cheers Tobias
Created attachment 382794 [details] output of lspci -nv on presario 2100
Created attachment 382795 [details] boot messages with i686 kernel boot messages with i686 kernel With this kernel the machine shutsdown and reboots sucessfully
Created attachment 382796 [details] boot messages with PAE kernel boot messages with PAE kernel with this kernel the machine wont shutdown/reboot or see my battery status
Created attachment 382799 [details] boot messages with PAE kernel boot messages with PAE kernel Replacing the previous messages.PAE because it was from the wrong boot (different kernel line parameters than the i686 one: nomodset was missing and rhgb was there) I did a diff of this PAE and i686 (after cut -b 17-) and couldn't see anything obvious that changed... Tobias
Bill: Thanks. I've tried compiling different kernel versions, but my HP TX2500 has a terrible problem with overheating and automatically shutting down whenever I try to compile a kernel (or do voice/video (or play an intensive video game (or...))). Until I find a solution to that, it'll take a while to find the spare time to test this. I can say that the following kernel from koji also had this problem: kernel-2.6.32.3-10.fc12 cebbert 2010-01-07 12:50:17 If I recall correctly, F11 never had this problem with my machine, and every kernel on F12 has had this problem. Perhaps trying a F11 live image will help.
Looking through the comments, I find no mention of another annoying aspect of this problem. That is that, at least on my HP tx2500z laptop, there is no way to reboot from the "powerdown" black screen other than to force power off first. As a workaround, I've taken to rebooting into Windows and powering down from there. R. Schwarting: your last comment disagrees with my earlier posting; I suspect your recollection is better than mine. Also, I cannot give you any clues - I'm too far away from the innards of the kernel.
I've got this on my HP TX2600 also. It started when I've switched to 2.6.32. I keep a 2.6.31 around that works well. It is not yet fixed in 2.6.32.11-99.fc12.
I seem to see the same issue with a Dell Inspirion 1545 and F13. I believe the problem is somehow related to the radeon framebuffer. Reason being is that in when the ATI Catalyst drivers appeared and installed, and "radeon" was blacklisted the computer shutdown and / or restarted on demand. Prior to that, with the open source Radeon drivers, I saw the same hang on shutdown. Problem is, there currently is no catalyst driver available for F13 and so the open source driver is once again deployed and of course the radeon framebuffer is once again running. If I blacklist the radeon framebuffer, X Windows does not work. So, the framebuffer is required. However, the computer does not shutdown or restart properly
As a result of difficulties with the 2.6.34 kernel, I have learned something that might be useful in troubleshooting this problem. If I include "nomodeset" in the kernel boot line, powerdown properly shuts off the power. This is my first exposure to kernel mode setting, so I have not yet taken time to learn how to find out how mode setting causes the problem. If I learn anything about that, I'll post something here.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
The fact that nomodeset must be enabled indicates the bug is not completely resolved; the indication seems to me to be that the interaction between the vanilla Fedora kernel and the AMD fglrx program (or something related to it) is not quite right. No idea how to track it; since current standard installation sets nomodeset it is no longer a problem for me.
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.