Description of problem: At booting I get the following message in journal: Mär 05 10:52:04 kernel: vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem Mär 05 10:52:04 kernel: [drm] Wrong MCH_SSKPD value: 0x16040307 Mär 05 10:52:04 kernel: [drm] This can cause pipe underruns and display issues. Mär 05 10:52:04 kernel: [drm] Please upgrade your BIOS to fix this. Mär 05 10:52:04 kernel: i915 0000:00:02.0: No connectors reported connected with modes Version-Release number of selected component (if applicable): Mär 05 10:52:01 kernel: Linux version 3.13.5-200.fc20.x86_64 (mockbuild@bkernel02) (gcc version 4.8.2 20131212 (Red Hat 4.8.2-7) (GCC) ) #1 SMP Mon Feb 24 16:51:35 U Mär 05 10:52:01 kernel: Command line: BOOT_IMAGE=/vmlinuz-3.13.5-200.fc20.x86_64 root=/dev/md8 ro vconsole.font=latarcyrheb-sun16 rhgb quiet LANG=en_US.UTF-8 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Only this information so far. Expected results: Please check and explain if we really should/have to update the BIOS or if this could be ignored and will disappear with a new kernel? Additional info:
I'm fairly sure it won't disappear with the next kernel. It was added in commit 1d7aaa0cf.
i'm observing this issue (pipe underruns/broken display) from time to time on my asus laptop with hybrid graphics with the latest asus bios update. is there any plan in the linux world to fix this problem or should i finally install windows on my hardware?
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.
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.