Bug 926064

Summary: Kernel 3.8.3-203.fc18 breaks HP MicroServer + Remote Access Card KVM
Product: [Fedora] Fedora Reporter: Daniele ViganĂ² <dennyvatwork>
Component: xorg-x11-drv-astAssignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 20CC: andreas, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, sgallagh, xgl-maint
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: 2015-06-29 11:50:02 UTC Type: Bug
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
Last console messages before "out of range" none

Description Daniele ViganĂ² 2013-03-23 15:18:56 UTC
Created attachment 715111 [details]
Last console messages before "out of range"

Description of problem:

After upgrading my HP ProLiant MicroServer (with the HP Remote Access Card, based on AST1100) from Fedora 17 (kernel-3.8.3-103.fc17) to Fedora 18 (kernel-3.8.3-203.fc18) the console via KVM viewer and via RAC VGA stopped to work with "Out of range" signal. To fix I had to add ast.modeset=0 as kernel boot parameter.

I also created a file in /etc/modprobe.d/ast.conf with
options ast modeset=0


Version-Release number of selected component (if applicable):
Kernel-3.8.3-203.fc18
Fedora 18


How reproducible:
Have a HP MicroServer with a Remote Access Card
Install Fedora 18 with latest kernel as writing

Steps to Reproduce:
1. Activate HP RAC KVM console
2. Boot the kernel
  
Actual results:
The KVM console goes out of range after
Mar 23 16:14:47 microserver kernel: [    4.104785] [TTM] Zone  kernel: Available graphics memory: 2024944 kiB
Mar 23 16:14:47 microserver kernel: [    4.104913] [TTM] Initializing pool allocator
Mar 23 16:14:47 microserver kernel: [    4.105035] [TTM] Initializing DMA pool allocator
Mar 23 16:14:47 microserver kernel: [   10.522147] [sched_delayed] sched: RT throttling activated

Expected results:
To see the console and login prompt

Additional info:
To fix ast.modeset=0 is needed

modinfo:
filename:       /lib/modules/3.8.3-203.fc18.x86_64/kernel/drivers/gpu/drm/ast/ast.ko
license:        GPL and additional rights
description:    AST
author:         Dave Airlie
alias:          pci:v00001A03d00002010sv*sd*bc03sc*i*
alias:          pci:v00001A03d00002000sv*sd*bc03sc*i*
depends:        drm,drm_kms_helper,ttm,i2c-core,i2c-algo-bit
intree:         Y
vermagic:       3.8.3-203.fc18.x86_64 SMP mod_unload
parm:           modeset:Disable/Enable modesetting (int)

Everything was woking fine on Fedora 17 with kernel-3.8.2-103.fc17

Comment 1 Josh Boyer 2013-04-01 15:52:43 UTC
The F17 kernel doesn't have the AST module enabled.

Comment 2 Andreas Thienemann 2013-11-05 10:02:13 UTC
Still an issue with F20.

Installer needs nomodeset in order to actually be able to install a machine.

Comment 3 Fedora End Of Life 2015-05-29 08:57:03 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 4 Fedora End Of Life 2015-06-29 11:50:02 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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