Bug 168015

Summary: kernel 2.6.13-1.1547_FC5 - general protection fault while booting
Product: [Fedora] Fedora Reporter: Michal Jaegermann <michal>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED CURRENTRELEASE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: 2.6.13-1.1555_FC5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-09-15 17:25:05 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
dmesg fragmet with a recorded general protection fault none

Description Michal Jaegermann 2005-09-10 20:12:46 UTC 
Description of problem:

The following happens when booting on x86_64:

general protection fault: 0000 [1] SMP 
CPU 0 
Modules linked in: sata_via libata sd_mod scsi_mod
Pid: 344, comm: insmod Not tainted 2.6.13-1.1547_FC5
RIP: 0010:[<ffffffff8034f464>] <ffffffff8034f464>{_spin_lock+4}
.....

The whole recorded trace is attached.

After this a machine continues booting and actually runs.  It seems that
the fault is actually caused by a debugging code.

I did not observe anything of that sort booting a similar kernel on i686.
A list of loaded modules (61 entries) looks quite normal.

Version-Release number of selected component (if applicable):
kernel-2.6.13-1.1547_FC5
Comment 1 Michal Jaegermann 2005-09-10 20:12:46 UTC 
Created attachment 118681 [details]
dmesg fragmet with a recorded general protection fault
Comment 2 Michal Jaegermann 2005-09-15 17:25:05 UTC 
Does not happen anymore with 2.6.13-1.1555_FC5