Hide Forgot
Followup to: http://lists.fedoraproject.org/pipermail/test/2011-October/103486.html Description of problem: Shortly before the Plymouth LUKS passphrase prompt, the screen turns black, the monitor reports "No signal" and enters power-saving mode. The system hasn't crashed, because instead of pressing Ctrl+Alt+Del I can also enter the passphrase blindly for the boot procedure to continue. However, nothing "wakes up" the monitor afterwards. Switching to a virtual console causes the signal to return, and what is displayed on the screen is not GDM but the gray background with the central animation having reached 100% or nearly that. There is no virtual console available, and one cannot return to GDM either. Any hints on what I could try out? Or any theories about what could be the culprit? When booting with plymouth:debug for several days, at first I couldn't reproduce it (but other issues), but today a reboot from within gnome-terminal, the boot procedure stopped just before the LUKS prompt. After a delay of a few seconds, monitor reported "No signal" and entered power-saving mode. The plymouth.log of that booting attempt is this: http://mschwendt.fedorapeople.org/tmp/plymouth-debug-pre-luks-freeze-signal-lost.log Compared with all the previous log file contents, this is the first one that mentioned a failure trying to open /dev/tty1: | [ply-terminal.c] ply_terminal_reopen_device:trying to | reopen terminal '/dev/tty1' (attempt 0) | [ply-terminal.c] ply_terminal_open_device:Unable to | open terminal device '/dev/tty1': Input/output error That might be important. Version-Release number of selected component (if applicable): up to and included plymouth-0.8.4-0.20110822.2.fc16.x86_64 How reproducible: Hard. No steps known. Doesn't happen everytime. Additional information: This has been happening some time since F-15. Not always, but occasionally multiple times in a row. With F-16 I had believed it was gone, especially when the boot screen switched to grey colours, but it still happens. My obvious work-around is to boot without "rhgb".
Has happened again a few times since disabling plymouth:debug again. Will also turn on SSH and try to log in to the machine when it happens, since all that works is Ctrl+Alt+Del and the virt.console screens are empty with just a blinking cursor. [...] Just some minutes ago when rebooting F-16, GDM screen greeted me with a background picture shifted by approx. 2/3 of the screen and a line of grey boxes (32x32 size?) at the bottom border of the screen. # grep ERROR /var/log/messages Nov 4 12:24:22 localhost kernel: [ 42.803410] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id Nov 4 12:25:02 localhost kernel: [ 82.389168] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id And another one when logging in to GNOME Shell: Nov 4 12:27:16 localhost kernel: [ 217.099029] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. 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
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.