Description of problem: I set the nomodeset line in the kernel, and this happened. Before I added the nomodeset line, I was unable to boot as the system hung after grub. I was able to boot with the default kernel, but not with the 3.7.4-204 kernel. I'm running an intel i7 3700K, with an Nvidia 650Ti Graphics card that is powering a 2560*1400 monitor via a DVI connection. I hadn't installed the proprietary graphics drivers, and was running the noveau drivers when the issue occurred. Additional info: WARNING: at arch/x86/mm/ioremap.c:85 __ioremap_caller+0x35a/0x370() Hardware name: To Be Filled By O.E.M. Modules linked in: Pid: 0, comm: swapper/0 Not tainted 3.7.4-204.fc18.x86_64 #1 Call Trace: [<ffffffff8105e67f>] warn_slowpath_common+0x7f/0xc0 [<ffffffff8105e6da>] warn_slowpath_null+0x1a/0x20 [<ffffffff810476aa>] __ioremap_caller+0x35a/0x370 [<ffffffff81059793>] ? efi_bgrt_init+0xb3/0x150 [<ffffffff81369450>] ? acpi_get_table_with_size+0x5f/0xbe [<ffffffff81047717>] ioremap_nocache+0x17/0x20 [<ffffffff81059793>] efi_bgrt_init+0xb3/0x150 [<ffffffff81d135cb>] efi_late_init+0x9/0xb [<ffffffff81cfbc2b>] start_kernel+0x3b8/0x3d4 [<ffffffff81cfb672>] ? repair_env_string+0x5e/0x5e [<ffffffff81cfb356>] x86_64_start_reservations+0x131/0x135 [<ffffffff81cfb45a>] x86_64_start_kernel+0x100/0x10f
Is this still an issue with 3.8.x?
I have kernel 3.8.8 installed right now, but am using the proprietary graphics drivers. Would removing the proprietary drivers and testing the boot recreate the situation I had, or do I need to do a complete reinstall of my OS to test this?
If you aren't seeing the message, then don't bother. If you are, then please remove the proprietary drivers and post the dmesg output from the machine once that is done.
This happens for me on 3.8.11-200.fc18.x86_64, without nomodeset, and with no proprietary drivers. I have an MS-7760, which did not ship with the highest quality of BIOSes.
Created attachment 749440 [details] Decoded BGRT table My BGRT table is clearly bogus.
We saw this with bug 751553 as well, and a firmware update fixed the issue. Andy, is there a firmware update that fixes the BGRT table for your machine?
Created attachment 769354 [details] Possible fix I sent this patch awhile ago and got no response. (I apparently failed to cc any lists -- oops.) I'm on the second-newest BIOS now, I think. The newest one isn't obviously installable without Windows.
*** Bug 989136 has been marked as a duplicate of this bug. ***
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 18 kernel bugs. Fedora 18 has now been rebased to 3.11.4-101.fc18. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 19, and are still experiencing this issue, please change the version to Fedora 19. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. It has been over a month since we asked you to test the 3.11 kernel updates and let us know if your issue has been resolved or is still a problem. When this happened, the bug was set to needinfo. Because the needinfo is still set, we assume either this is no longer a problem, or you cannot provide additional information to help us resolve the issue. As a result we are closing with insufficient data. If this is still a problem, we apologize, feel free to reopen the bug and provide more information so that we can work towards a resolution If you experience different issues, please open a new bug report for those.
The bug is still present on 3.11.6-200.fc19.x86_64.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs. Fedora 19 has now been rebased to 3.12.6-200.fc19. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 20, and are still experiencing this issue, please change the version to Fedora 20. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.13.4-200.fc20. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
This is still present. I suspect that it's fixed by: commit 09503379dc99535b1bbfa51aa1aeef340f5d82ec Author: Matt Fleming <matt.fleming> Date: Thu Feb 13 17:17:54 2014 +0000 x86/efi: Check status field to validate BGRT header So far I haven't succeeded in booting a 3.14-rc kernel on this box, so I haven't tested it yet.
This bug seems to be fixed in a kernel.org 3.14 kernel. Is there any plan to update F20 to 3.14?
Yes, eventually.
F20 was rebased to 3.14.1 this morning. A build is on-going.
kernel-3.14.2-200.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/kernel-3.14.2-200.fc20
Package kernel-3.14.2-200.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-3.14.2-200.fc20' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-5808/kernel-3.14.2-200.fc20 then log in and leave karma (feedback).
kernel-3.14.2-200.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.