Bug 633040 - kernel-2.6.34.6-54.fc13.x86_64 does not boot
Summary: kernel-2.6.34.6-54.fc13.x86_64 does not boot
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-12 15:08 UTC by Kronos003
Modified: 2011-06-28 12:59 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-06-28 12:59:05 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Kronos003 2010-09-12 15:08:55 UTC
Description of problem:
system gets past grub shows usual APIC error, then hangs - blank screen

Version-Release number of selected component (if applicable):
kernel-2.6.34.6-54.fc13.x86_64

How reproducible: everytime


Steps to Reproduce:
1. boot

  
Actual results:
nothing happens after grub

Expected results:
system loads modules and performs usual startup operations, then presents gui.



Additional info:
last working kernel (still works)
Linux localhost 2.6.34.6-47.fc13.x86_64 #1 SMP Fri Aug 27 08:56:01 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux

relevant system specs
Toshiba A215-S7422
AMD Turion TL-58
4GB ram


also the APIC error is the sameone i always see on this laptop - something to the effect apic timer not connected or something like that. ive seen it on every kernel since fedora 9

Comment 1 Chuck Ebbert 2010-09-13 11:49:49 UTC
Can you remove "rhgb quiet" from the kernel options in /etc/grub.conf and see if there are any more messages?

Comment 2 Kronos003 2010-09-13 13:15:18 UTC
last thing i see is (darn my bad memory) cfq scheduler loaded (default) then black screen(nothing else happens. i cant remember the exact error as this is my only box

no scary looking errors...

on another note - i usually see a ata1 soft reset error just prior to the gui starting to load. on this kernel i dont see that and the gui doesnt load. wonder if that says anything about where in the process things are getting hung up.

Comment 3 Kronos003 2010-09-13 13:19:39 UTC
the cfq thing actually didnt appear to be an error - more like a notice. at any rate its the last thing i see before the screen goes blank...

Comment 4 Bug Zapper 2011-05-31 13:44:19 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 '13'.

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 13'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 13 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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Bug Zapper 2011-06-28 12:59:05 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.