Hide Forgot
Description of problem: I am not 100% on the exact situation to trigger this. But generally, if I have music playing through Rhythmbox and am simultaneously using other programs such as Firefox with several tabs open, the kernel may freeze. This normally happens when switching between tabs, but not always. When the kernel freezes the last second or so of audio continues to loop. Once frozen I am unable to switch to a different terminal to diagnose the issue and will need to reset the computer with the hardware reset switch. I am happy to provide any additional diagnostics to help understand the issue. Version-Release number of selected component (if applicable): kernel-3.1.1-2.fc16.x86_64 How reproducible: Not, 100%, only occasionally and sporadically. Steps to Reproduce: 1. Play music 2. Use desktop in a normal fashion with browser, terminals, emacs, etc Actual results: After a spike in CPU, kernel may freeze Expected results: No freeze. Additional info: Hardware profile: http://www.smolts.org/client/show/pub_621c77b7-dfc4-4b1f-b643-19efd5fbe185
This could also be related to a memory load and not cpu load A way to reproduce this with a higher frequency for me: 0. Have music playing through rhythmbox 1. Have Firefox open; have several tabs open 2. Start a large MySQL restore from a previous mysqldump; must be reasonably large 3. Browse the web a frequently switch back and forth between tabs 4. Kernel, and everythin, stalls, but last ~1s of music continues to loop As mentioned previously I am willing to collect debug information if it will help diagnose the issue. I am just not sure what is needed.
Created attachment 536835 [details] dmesg from the next boot after a freeze
This bug still occurs. Most recently happened with one user logged in. Running: * Firefox * Rhythmbox * gnome-terminal * yum update This seems especially dangerous to me because the yum updated was cut off due to the kernel freezing. I think the audio (through Rhythmbox) is the common factor between freezes. If there is *any* information I can provide or actions I can take to help diagnose the issue, I would be glad to take those steps.
Are you still seeing this on the 3.2.7 or newer kernel? If so, when it freezes is the machine accessible via ping or ssh? Does the capslock light toggle when you press the key?
> Are you still seeing this on the 3.2.7 or newer kernel? Yes. I was able to reproduce the bug with the following steps: 1. Upgrade to latest: kernel-3.2.7-1.fc16.x86_64 2. Restart machine 3. Start rhythmbox and play music 4. In a loop import a previous mysqldump 5. Use desktop as normal, including browse the web 6. Eventually the kernel freezes and last ~1s of audio loops The kernel froze within 10 minutes of trying. > If so, when it freezes is the machine accessible via ping or ssh? No. I can successfully log in with ssh before the crash. But after the freeze, logging in with ssh times out. > Does the capslock light toggle when you press the key? No. The caps lock key has no effect. --- Please let me know if there is any additional information I can collect.
[mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update.
Bug still present with kernel kernel-3.3.0-4.fc16.x86_64. Same steps to reproduce.
# Mass update to all open bugs. Kernel 3.6.2-1.fc16 has just been pushed to updates. This update is a significant rebase from the previous version. Please retest with this kernel, and let us know if your problem has been fixed. In the event that you have upgraded to a newer release and the bug you reported is still present, please change 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. If you are not the original bug reporter and you still experience this bug, please file a new report, as it is possible that you may be seeing a different problem. (Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).
> Please retest with this kernel, and let us know if your problem has been fixed. The bug is still present after updating to the latest kernel and rebooting. Same steps to reproduce. kernel-3.6.2-1.fc16.x86_64
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.