Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 202980 - Fedora Core 5 refuses to boot
Fedora Core 5 refuses to boot
Status: CLOSED DUPLICATE of bug 202978
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
i686 Linux
medium Severity urgent
: ---
: ---
Assigned To: Kernel Maintainer List
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2006-08-17 12:36 EDT by Shashank
Modified: 2007-11-30 17:11 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-08-23 01:01:50 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 Shashank 2006-08-17 12:36:13 EDT
Description of problem:
Fedora Core 5 refuses to boot

Version-Release number of selected component (if applicable):
kernel 2.6.15-1.2054_FC5 ( i386 )

How reproducible:

Steps to Reproduce:
1. Start my Computer, and try to boot into FC5
Actual results:
I get an error screen that looks something like this ( its different each time )
cpu : 0
eip : 0060:[<c0165fb7>] not tainted VLI
eflags : 00210202
eip is at d_albc+0x151/0x1bc
eax:f68195b8 ebx:f797cdd0 ecx:00200246
edx:f6ef201b esi:f6ef201b edi:eefe43e1

process : python ( pid:1547, threadinfo:f797c00 )

It also gives me some call trace.
It also says it will continue in 120 seconds.

After 120 seconds, sometimes i again get a similar screen, or my comp just 
stops responding.

error screen #2
cpu 0
eip 0060:[<c0165fb7>] not tainted vli
eflags 00210202
eip is at d_alloc+0x151/0x1bc
eax:f7fb06e0   ebx:f669bdb0   ecx:00000246 
edx:f7fb06c0   esi:f6a9d00a   edi:ee6e43e1

process cpuspeed ( pid: 1147, threadinfo=f6f9b000 task f6f2e550 )

Expected results:
Normal Boot

Additional info:
The error screens are different each time i boot.
I also tried booting into runlevel 1, 2 & 3, with same results
Comment 1 Hans de Goede 2006-08-23 01:01:50 EDT
You filed this 4 times!, closing 3 as dups.

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

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