Bug 953679

Summary: Random System Freeze Ups
Product: [Fedora] Fedora Reporter: KitchM <tech>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 19CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, rutger.noot, tech
Target Milestone: ---Flags: jforbes: needinfo?
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-10 14:42:04 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 Flags
dmesg output none

Description KitchM 2013-04-18 21:37:06 UTC 
Description of problem:
The operating system environment is unstable.

Am experiencing system freeze-ups at random times.  Two issues seem to be a problem.  First is sound-related, and the second is scanner-related.

In one instance various programs were open, including listening to an Internet stream on QMMP.  Started a youtube video in browser and the system ground to a halt and froze.  Even the mouse was unresponsive.  Perhaps the system cannot handle multiple streams as it should.

Another example was when the system was trying to use the scanner.  I started Simple Scan while just Firefox and Thunderbird were open, and the system froze with the scan program full screen but with active mouse action.  However, the mouse could do nothing and there was no way to stop a program.  The system was frozen in that state.  Evidently, the system slowly builds to an overload state and freezes.  Unfortunately, there is no way to notice until it is too late to respond.

Upon resetting from this last example, the action following the grub menu was strange.  A few lines of error messages appeared and the word "froze" displayed in one of them.  Then a blue, multi-stage progress bar appeared across the bottom of a blank screen with the number 18 at the right end.  At some point in its progess, it jumped to the center of the screen and changed resolution.  It finally showed a small command-line-like line of boot up detail, and then immediately gave the normal login action.  All very bizarre and unhelpful actions.

ABRT does not capture these events.  Obviously there can be no screen shots.


Version-Release number of selected component (if applicable):
Fedora 18 with Xfce 4.10.0

How reproducible:
Unknown

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:
Smooth integration of all processes.

Additional info:
Comment 1 Josh Boyer 2013-07-02 17:09:54 UTC 
Are you still seeing this with kernel 3.9.8 or newer?  If so, can you attach the output of dmesg?
Comment 2 KitchM 2013-07-03 00:56:53 UTC 
Just fedup-d my system to 19 and did try the simple scan program again.  This time there was an improvement. The program opened and, upon selecting to scan, it reported that no scanner was available and did not freeze up at all.  I was able to close the program and everything is good.

I have not tried the multiple sound programs again, but will report here if I see any more system freezes of any sort.

I will say that fedup stopped after reboot with very little progress indicated on the progress bar.  It had been left running for a couple hours.  But I reset the computer and it came back up as the first item on the grub menu, so I selected it and let it finish.  This time it completed after a fairly short interval; probably less than 30 minutes.

However, after it rebooted it came up to an unknown screen, because when I came back to it, there appeared to be a screen displaying the time in digital format and a sound adjustment icon in the upper right corner.  The mouse was active, but I could not get anything to change no matter what I tried.  Even the keyboard seemed to be unable to do anything.  There was a series of arrows from the middle of the bottom part of the screen.  They would appear, one after the other in an upward column and then go away.  There was no way to recover, so I reset the computer again and got my regular logon screen back.

Evidently, there is a flaw in the system with some sort of what might be called a screensaver program.  This shows yet another way that Fedora is not stable as it should be.
Comment 3 KitchM 2013-07-03 02:15:07 UTC 
Okay, I just tried simplescan again and the system froze.

I am attaching the output from dmesg.
Comment 4 KitchM 2013-07-03 02:15:53 UTC 
Created attachment 768012 [details]
dmesg output
Comment 5 Josh Boyer 2013-09-18 20:35:20 UTC 
*********** 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.
Comment 6 KitchM 2013-09-18 21:18:05 UTC 
Thank you.  The update is not in Yumex right now, but I will check in the morning and see if the update is available then.
Comment 7 KitchM 2013-09-19 15:27:30 UTC 
FAIL
Comment 8 Justin M. Forbes 2014-01-03 22:09:37 UTC 
*********** 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.12.6-200.fc19.  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 20, and are still experiencing this issue, please change the version to Fedora 20.

If you experience different issues, please open a new bug report for those.
Comment 9 Justin M. Forbes 2014-03-10 14:42:04 UTC 
*********** MASS BUG UPDATE **************

This bug has been in a needinfo state for more than 1 month and is being closed with insufficient data due to inactivity. If this is still an issue with Fedora 19, please feel free to reopen the bug and provide the additional information requested.