Bug 753610 - after using for a while system freezes
Summary: after using for a while system freezes
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-13 18:30 UTC by Sigrid Philippsen
Modified: 2012-03-05 20:21 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-03-05 20:21:14 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Sigrid Philippsen 2011-11-13 18:30:18 UTC 
Description of problem:
Been working for about 15-30min, then everything freezes.

Version-Release number of selected component (if applicable):
kernel-3.1.0-7.fc16.x86_64
kernel-3.1.1-1.fc16.x86_64

How reproducible:
Reproducible.

Steps to Reproduce:
1. Use for a while (surf the web)
  
Actual results:
System freezes (no mouse pointer movement, not reachable over the network)

Expected results:
None of the above.

Additional info:
System worked fine on Fedora 15.

Hardware info: http://www.smolts.org/client/show/pub_4177bc21-d587-47d3-8157-642476ed31a3

Suspend-to-RAM and -to-disk ceased working as well.
Comment 1 Dave Jones 2011-11-15 20:22:28 UTC 
can you try the kernel-debug build, and see if you get a backtrace ?
Comment 2 Nils Philippsen 2011-11-16 21:58:49 UTC 
Besides installing and booting into it, is there anything else to do to get a backtrace?
Comment 3 Nils Philippsen 2011-11-17 23:07:11 UTC 
Hmm, simply booting kernel-debug doesn't work -- plymouth doesn't progress to the end, pressing Escape shows udevd endlessly attempting to kill some modprobe processes...
Comment 4 Josh Boyer 2012-02-29 19:51:50 UTC 
Is this still being seen with 3.2.7 or newer?
Comment 5 Sigrid Philippsen 2012-03-01 18:37:12 UTC 
No, with 3.2.7 I never had it again.
Comment 6 Josh Boyer 2012-03-05 20:21:14 UTC 
Thank you for letting us know.
Note You need to log in before you can comment on or make changes to this bug.