Bug 437304

Summary: Kernel panic on x86_64
Product: [Fedora] Fedora Reporter: Jeremy Sanders <jss>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 7CC: rmj
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-03-24 15:00:42 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
none
another panic in swapper (when doing something)
none
yet another panic in swapper none

Description Jeremy Sanders 2008-03-13 14:31:56 UTC 
Description of problem:

A x86-64 system panics with recent kernels in current_kernel_time+0x12/0x38.
This is a FOXCONN 6150K8MA-8EKRS motherboard with an AMD Athlon 64 X2 4600+
processor. The machine boots and within a few minutes kernel panics.

We've tried replacing the memory and trying different memory configurations.

The machine doesn't panic while running the Fedora 7 install CD.

Version-Release number of selected component (if applicable):
kernel-2.6.23.15-80.fc7

How reproducible:
Very.

Steps to Reproduce:
1. Boot system
2. Wait
3.
  
Additional info:
See attached file (gathered using serial cable from crashing system)
Comment 1 Jeremy Sanders 2008-03-13 14:31:56 UTC 
Created attachment 297939 [details]
kernel oops
Comment 2 Jeremy Sanders 2008-03-13 17:52:32 UTC 
Created attachment 297960 [details]
another panic in swapper (when doing something)

Here's another panic. It seems to have a call trace if it is doing something,
but always crashes in swapper.
Comment 3 Jeremy Sanders 2008-03-13 17:53:22 UTC 
Created attachment 297961 [details]
yet another panic in swapper
Comment 4 Chuck Ebbert 2008-03-13 20:15:13 UTC 
Those oops messages point to some kind of serious hardware problem, like bad
power supply or memory. The system is jumping to addresses in the middle of an
instruction and oopsing on instructions that can't possibly fail the way they do.
Comment 5 Jeremy Sanders 2008-03-24 15:00:42 UTC 
Thanks for the comment. It indeed appears to be a hardware fault. It wasn't the
memory, motherboard or power supply. After lots of swapping hardware, it turned
out to be a bad CPU!

I'll close this bug.