Bug 624979

Summary: [kernel] general protection fault: 0000 [#1] SMP
Product: [Fedora] Fedora Reporter: Joachim Frieben <jfrieben>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: anton, aquini, dougsland, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-18 12:22:30 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 oops caused by recent F14 kernels. none

Description Joachim Frieben 2010-08-18 09:47:50 UTC 
Description of problem:
On a fully updated F14 system, a kernel oops appears once in while starting with

  kernel: general protection fault: 0000 [#1] SMP
  kernel: last sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
  ..

This message appears in /var/log/messages but an abridged version is also issued to the console.

Version-Release number of selected component (if applicable):
2.6.35.2-9.fc14.x86_64

How reproducible:
Intermittently.

Steps to Reproduce:
1. Run GNOME session.
  
Actual results:
At some point, a beep occurs, and above message is spawned to existing terminal windows.

Expected results:
No kernel fault should occur.

Additional info:
A fully updated F13 is not affected by this issue.
Comment 1 Joachim Frieben 2010-08-18 09:51:18 UTC 
Created attachment 439347 [details]
Kernel oops caused by recent F14 kernels.

The hardware profile of this Tyan S2865 based Opteron 146 system can be found at

http://www.smolts.org/client/show/pub_d4052415-5ebc-436c-8b63-2943d0e7bcc3
Comment 2 Chuck Ebbert 2010-08-18 12:22:30 UTC 

*** This bug has been marked as a duplicate of bug 577968 ***