Bug 493560

Summary: Frequent kernel failures for 2.6.29.1-37.rc1.fc11.x86_64
Product: [Fedora] Fedora Reporter: Joachim Frieben <jfrieben>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: kernel-maint, quintela
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: kernel-2.6.29.1-111.fc11 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-05-05 19:11:04 UTC Type: ---
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
Kernel failure report from kerneloops utility none

Description Joachim Frieben 2009-04-02 09:10:59 UTC
Created attachment 337752 [details]
Kernel failure report from kerneloops utility

Description of problem:
After upgrading to kernel 2.6.29.1-37.rc1.fc11.x86_64, system frequently emits kernel oopses reported by kerneloops.

Version-Release number of selected component (if applicable):
2.6.29.1-37.rc1.fc11.x86_64

How reproducible:
Frequently.

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 15:05:57 UTC
Is the system being susupended and/or resumed when these messages occur?

Comment 2 Joachim Frieben 2009-04-02 21:06:23 UTC
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 19:11:04 UTC
Issue hasn't occurred for recent "rawhide kernels.