Description of problem: https://bugzilla.kernel.org/show_bug.cgi?id=178641 https://bugzilla.kernel.org/show_bug.cgi?id=178641#c14 Version-Release number of selected component (if applicable): kernel Fedora 24 x86_64 4.7.7 Platform Sandy Bridge: CPUID = 0x206A7 [http://www.cpu-world.com/cgi-bin/CPUID.pl?CPUID=9802] How reproducible: https://bugzilla.kernel.org/show_bug.cgi?id=178641#c13 Actual results: Platform hangs forever. Expected results: To resume and continue to work as expected! Additional info: http://www.forums.fedoraforum.org/showthread.php?t=311898
To explain this problem more explicitly (to be technical and punctual): Here are the logs from https://bugzilla.kernel.org/show_bug.cgi?id=178641#c13 - Comment 13 The log https://bugzilla.kernel.org/attachment.cgi?id=243341 exhibits the following: [ 78.858081] ehci-pci 0000:00:1a.0: cache line size of 4 is not supported [ 78.858201] ehci-pci 0000:00:1d.0: cache line size of 4 is not supported If you start googling on "cache line size of 4 is not supported", you never find one on the net (or I did not look enough carefully/in-depth)! You should try on ANY INTEL platform on ANY Linux to execute the following commands: $ cat /proc/cpuinfo | grep cache_alignment $ getconf LEVEL1_ICACHE_LINESIZE $ getconf LEVEL1_DCACHE_LINESIZE And tell me what number do you see? You should see ONLY one number, guess which? ;-) The questions which are hanging in the air are the following: [1] Why Sandy Bridge: CPUID = 0x206A7 exhibits this behavior (root cause of this problem) in Fedora 24 kernels? [2] What is the solution to this problem? Floor all yours, RHL experts! Thank you, _nobody_
Moving this whole Bugzilla to Fedora 25 (so I NEED/REQUEST investigation on this insanity), since the following info: https://bugzilla.kernel.org/show_bug.cgi?id=178641#c24 So, this bug/"feature" persists on Fedora 25. Let us see if this bug/"feature" will continue to persist on Fedora 26?! Thank you, _nobody_
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 EOL if it remains open with a Fedora 'version' of '25'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
This remains in Fedora 27. Thank you for understanding, _nobody_
I'm done, I managed to get a motherboard, processor and ram for free. The hardware is older and less powerful but that work. I'm really disappointed.
I apologize, Jeremy, for the late answer! I have very pro arrangement with RT kernels, and have very little time for other activities, these days. Since I NEVER saw such a problem, I can just imagine that on your HW (motherboard, namely PCH and surrounding USB 2.0 hub controllers) something went really wrong (there is some HW bug, cold soldering, or some of the internal USB 2.0 hub circuitry does not work correctly anymore). I will continue to monitor if such a message will reappear on the WWW pages (in order to understand if there is a HW system INTEL architectural error). _nobody_
Well, the replacement motherboard died... I'm back to the motherboard that have the suspend problem... (In reply to niemand from comment #7) > Since I NEVER saw such a problem, I can just imagine that on your HW > (motherboard, namely PCH and surrounding USB 2.0 hub controllers) something > went really wrong (there is some HW bug, cold soldering, or some of the > internal USB 2.0 hub circuitry does not work correctly anymore). The thing is that it work on windows, so it can't be a hardware problem.
I use Windows 10 on this computer... You may be should close this. Thanks.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 EOL if it remains open with a Fedora 'version' of '27'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days