Bug 499625 - oops on boot
oops on boot
Product: Fedora
Classification: Fedora
Component: kerneloops (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-05-07 09:27 EDT by David Huff
Modified: 2011-12-13 17:28 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-06-28 08:25:02 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David Huff 2009-05-07 09:27:36 EDT
Description of problem:

oops on boot

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

Fedora-11 preview Fedora release 10.93 (Leonidas) #1 SMP Mon May 4 04:46:15 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux

How reproducible:

Install on Dell 490 boot:

Kernel failure message 1:
------------[ cut here ]------------
WARNING: at arch/x86/kernel/cpu/mtrr/generic.c:407 generic_get_mtrr+0xc8/0x105() (Not tainted)
Hardware name: Precision WorkStation 490    
mtrr: your BIOS has set up an incorrect mask, fixing it up.
Modules linked in:
Pid: 0, comm: swapper Not tainted #1
Call Trace:
[<ffffffff81048a63>] warn_slowpath+0xbc/0xf0
[<ffffffff810495d1>] ? vprintk+0x308/0x335
[<ffffffff813ab3cc>] ? _spin_unlock_irqrestore+0x2c/0x42
[<ffffffff813ab3cc>] ? _spin_unlock_irqrestore+0x2c/0x42
[<ffffffff8101e8c3>] generic_get_mtrr+0xc8/0x105
[<ffffffff8164996d>] mtrr_bp_init+0x222/0x59f
[<ffffffff816532f5>] ? early_gart_iommu_check+0x8a/0x25b
[<ffffffff8164540d>] setup_arch+0x418/0x7d5
[<ffffffff81060679>] ? raw_notifier_chain_register+0x9/0x2e
[<ffffffff8163da83>] start_kernel+0x99/0x3cc
[<ffffffff8163d2c1>] x86_64_start_reservations+0xac/0xb0
[<ffffffff8163d3ce>] x86_64_start_kernel+0xe6/0xf5
---[ end trace 4eaa2a86a8e2da22 ]---

can provide more info if needed......
Comment 1 Bug Zapper 2009-06-09 11:19:32 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
Comment 2 Bug Zapper 2010-04-27 10:11:06 EDT
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 3 Bug Zapper 2010-06-28 08:25:02 EDT
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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