Bug 493560 - Frequent kernel failures for
Frequent kernel failures for
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-04-02 05:10 EDT by Joachim Frieben
Modified: 2009-05-05 15:11 EDT (History)
2 users (show)

See Also:
Fixed In Version: kernel-
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-05-05 15:11:04 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Kernel failure report from kerneloops utility (4.85 KB, text/plain)
2009-04-02 05:10 EDT, Joachim Frieben
no flags Details

  None (edit)
Description Joachim Frieben 2009-04-02 05:10:59 EDT
Created attachment 337752 [details]
Kernel failure report from kerneloops utility

Description of problem:
After upgrading to kernel, system frequently emits kernel oopses reported by kerneloops.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Start GNOME session.
2. Do some work.
Actual results:
The kerneloops utility reports occurrence of repeated kernel failures.

Expected results:
Everything quiet on the Western front.

Additional info:
This did not occur for the original "Nouveau Test Day" live CD from which the system had been installed in the first place.
Comment 1 Chuck Ebbert 2009-04-02 11:05:57 EDT
Is the system being susupended and/or resumed when these messages occur?
Comment 2 Joachim Frieben 2009-04-02 17:06:23 EDT
The attachment with the triple failure was from an oops after rebooting the system, I think. However, I have just resumed the system from suspend, and I have gotten exactly the same message albeit a single copy only.
Comment 3 Joachim Frieben 2009-05-05 15:11:04 EDT
Issue hasn't occurred for recent "rawhide kernels.

Note You need to log in before you can comment on or make changes to this bug.