Bug 977012
Summary: | monitor cycles through "no signal" then suspend every 10 seconds | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dean Hunter <deanhunter> | ||||||
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 20 | CC: | deanhunter, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, michele | ||||||
Target Milestone: | --- | Keywords: | Reopened | ||||||
Target Release: | --- | Flags: | jforbes:
needinfo?
|
||||||
Hardware: | x86_64 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2014-12-10 14:58:49 UTC | Type: | Bug | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Dean Hunter
2013-06-22 15:41:33 UTC
This problem persists after upgrading to Fedora 19 and kernel 3.9.9-302.fc19.x86_64. *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs. Fedora 19 has now been rebased to 3.11.1-200.fc19. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those. This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously. This problem is occurring on Fedora 20-beta. Hi Dean, which kernel version on Fedora 20 is still broken? Could you give this experimental kernel a spin: http://koji.fedoraproject.org/koji/buildinfo?buildID=478832 That way we will know if it is fixed upstream yet or not. Thanks, Michele Oops! [dean@developer ~]$ uname -r 3.11.8-300.fc20.x86_64 I am sorry, but I have forgotten how to use the koji link to update my system. I remember that I did something to download one or more rpms to an additional local repository, enabled the repository, then updated my system. Please remind me how to download the rpms. It would also help if you could specify which rpms to download for x86_64. Thank you. Please, I need a little help on the procedure for applying the requested update? (In reply to Michele Baldessari from comment #5) > Hi Dean, > > which kernel version on Fedora 20 is still broken? > Could you give this experimental kernel a spin: > http://koji.fedoraproject.org/koji/buildinfo?buildID=478832 > > That way we will know if it is fixed upstream yet or not. > > Thanks, > Michele Yes, the problem still occurs with kernel 3.13.0-0.rc0.git5.1.fc21.886_64. Hi Dean, thanks this lets us at least know that the problem likely exists upstream as well. Could you please upload /var/log/messages and /var/log/Xorg.0.log to this BZ? Thanks, Michele Created attachment 828612 [details]
/var/log/messages
Created attachment 828624 [details]
/var/log/Xorg.0.log
(In reply to Michele Baldessari from comment #9) The requested log files have been attached. Please note that the rawhide kernel will not display the Gnome login screen unless I disable the graphics accelerator as follows: if lspci | grep VGA | grep NVIDIA then echo "nVidia graphics adapter in use" sed --in-place \ '/^GRUB_CMDLINE_LINUX/ s/rhgb quiet/& nouveau.noaccel=1/' \ /etc/default/grub grub2-mkconfig -o /boot/grub2/grub.cfg fi *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.13.4-200.fc20. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those. *********** MASS BUG UPDATE ************** This bug has been in a needinfo state for several weeks and is being closed with insufficient data due to inactivity. If this is still an issue with Fedora 20, please feel free to reopen the bug and provide the additional information requested. I apologize for the delay. I just updated to 3.13.6-200.fc20.x86_64 and the problem persists. *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.14.4-200.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those. I just updated to 3.14.5-200.fc20.x86_64 and the problem persists. *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.17.2-200.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those. This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously. |