Bug 220271

Summary: kernels from FC6 die in do_unblank_screen()
Product: [Fedora] Fedora Reporter: Michal Jaegermann <michal>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 6CC: jonstanley, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-01-08 02:36:28 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:
Bug Depends On:    
Bug Blocks: 427887    
Attachments:
Description Flags
frozen screen picture for 2.6.18-1.2798.fc6
none
frozen screen picture for 2.6.18-1.2868.fc6
none
dmesg from a boot with 1 Gig of memory "lost"
none
an output from 'cat /proc/cpuinfo'
none
dmidecode with the latest BIOS
none
PCI devices detected on the board none

Description Michal Jaegermann 2006-12-20 00:11:08 UTC
Description of problem:

On P5B Asus board with Intel(R) Core(TM)2 CPU and 4 GB of installed
memory an attempt to boot 2.6.18-1.2798.fc6 or 2.6.18-1.2868.fc6
causes an instant lockup pretty close to a beginnig of the whole boot
sequence _provided_ "memory reallocation" feature in BIOS is _not_
disabled.  OTOH if you will do this disabling then a machine does boot
but it is loosing a gig of memory with an output of 'free -m' as
follows:
             total       used       free     shared    buffers     cached
Mem:          2948        559       2389          0         17        335
-/+ buffers/cache:        205       2742
Swap:         1983          0       1983

Updating to the latest available BIOS does not help.

A lockup happens pretty much at the beginning of the whole boot.
At least whatever is printed on a screen scrolls way too fast for
anybody to read anything out of that and after that there is no
reaction to anything whatsoever (and there is no serial port so
no way to try to capture an output that way).  I attach two
screen pictures with whatever is frozen on screen.  One from
2.6.18-1.2798.fc6 boot and one from 2.6.18-1.2868.fc6.  They do
not differ that much with an exception of "CR2" on the screen top,
which is not even in the same range, and slightly different address
for _sinittext.

Apart of these two picturea attached are a dmesg output from a boot
with a "memory reallocation" disabled, and from 'cat /proc/cpuinfo',
from 'dmidecode' and from 'lspci -tv'.

How reproducible:
As described - always, unfortunately.

Comment 1 Michal Jaegermann 2006-12-20 00:11:08 UTC
Created attachment 144061 [details]
frozen screen picture for 2.6.18-1.2798.fc6

Comment 2 Michal Jaegermann 2006-12-20 00:12:35 UTC
Created attachment 144062 [details]
frozen screen picture for 2.6.18-1.2868.fc6

Comment 3 Michal Jaegermann 2006-12-20 00:13:52 UTC
Created attachment 144063 [details]
dmesg from a boot with 1 Gig of memory "lost"

Comment 4 Michal Jaegermann 2006-12-20 00:14:42 UTC
Created attachment 144064 [details]
an output from 'cat /proc/cpuinfo'

Comment 5 Michal Jaegermann 2006-12-20 00:16:15 UTC
Created attachment 144065 [details]
dmidecode with the latest BIOS

Comment 6 Michal Jaegermann 2006-12-20 00:17:22 UTC
Created attachment 144066 [details]
PCI devices detected on the board

Comment 7 Jon Stanley 2008-01-08 01:55:32 UTC
(This is a mass-update to all current FC6 kernel bugs in NEW state)

Hello,

I'm reviewing this bug list as part of the kernel bug triage project, an attempt
to isolate current bugs in the Fedora kernel.

http://fedoraproject.org/wiki/KernelBugTriage

I am CC'ing myself to this bug, however this version of Fedora is no longer
maintained.

Please attempt to reproduce this bug with a current version of Fedora (presently
Fedora 8). If the bug no longer exists, please close the bug or I'll do so in a
few days if there is no further information lodged.

Thanks for using Fedora!

Comment 8 Michal Jaegermann 2008-01-08 02:16:41 UTC
I cannot provide any info as I do not have an access to this hardware.
I had at the time I filed the bug but this was over a year ago and
nobody looked particularly interested.