Created attachment 1183163 [details] failed radeon drm init with 4.6.4-301 Description of problem: I have a TOSHIBA SATELLITE L850 notebook. Since I have switched to 4.6.x kernels it is booting on text mode, and X is coming up in low resolution mode. Version-Release number of selected component (if applicable): How reproducible: Boot with 4.6.3-300 or 4.6.4-301 kernel. If I boot 4.5.7-300 kernel everything is fine, Steps to Reproduce: 1. 2. 3. Actual results: My laptop is coming up in low resolution mode which is not so usable for desktop. Expected results: Boot up with native high resolution mode, which older kernel does. Additional info: Relevant part of journalctl -b is attached.
Created attachment 1183164 [details] successful radeon init with 4.5.7-300 kernel Attaching messages from successful radeon init with 4.5.7-300 kernel for reference.
[drm] Initialized drm 1.1.0 20060810 r8169 0000:09:00.0 enp9s0: renamed from eth0 [drm] radeon kernel modesetting enabled. AMD IOMMUv2 driver by Joerg Roedel <jroedel> AMD IOMMUv2 functionality not available on this system CRAT table not found Finished initializing topology ret=0 kfd kfd: Initialized module [drm] initializing kernel modesetting (TURKS 0x1002:0x6840 0x1179:0xFB31 0x00). [drm] register mmio base: 0xC2000000 [drm] register mmio size: 131072 ------------[ cut here ]------------ WARNING: CPU: 2 PID: 307 at arch/x86/mm/ioremap.c:122 __ioremap_caller+0x1d1/0x350 ioremap on RAM at 0x0000000000000000 - 0x000000000001ffff Modules linked in: amdkfd amd_iommu_v2 radeon(+) i2c_algo_bit drm_kms_helper crc32c_intel ttm drm serio_raw r8169 mii fjes CPU: 2 PID: 307 Comm: systemd-udevd Not tainted 4.6.4-301.fc24.x86_64 #1 Hardware name: TOSHIBA SATELLITE L850/Type2 - Board Product Name1, BIOS 6.80 10/01/2013 0000000000000286 00000000b00d4aaa ffff8801c4fff6e8 ffffffff813dbcaf ffff8801c4fff738 0000000000000000 ffff8801c4fff728 ffffffff810a742b 0000007affffffff 0000000000020000 ffffffff8142e2ad 0000000000000000 Call Trace: [<ffffffff813dbcaf>] dump_stack+0x63/0x84 [<ffffffff810a742b>] __warn+0xcb/0xf0 [<ffffffff8142e2ad>] ? pci_map_rom+0x5d/0xd0 [<ffffffff810a74af>] warn_slowpath_fmt+0x5f/0x80 [<ffffffff8106b204>] ? iounmap.part.1+0x64/0x90 [<ffffffff8106af31>] __ioremap_caller+0x1d1/0x350 [<ffffffff8106b0c7>] ioremap_nocache+0x17/0x20 [<ffffffff8142e2ad>] pci_map_rom+0x5d/0xd0 [<ffffffffc014c31a>] radeon_read_bios.isra.2+0x3a/0xc0 [radeon] [<ffffffffc014c63b>] radeon_get_bios+0x29b/0x1040 [radeon] [<ffffffff81100037>] ? vprintk_emit+0x297/0x490 [<ffffffff81222872>] ? kmem_cache_alloc_trace+0x1c2/0x1d0 [<ffffffff815166ab>] ? register_client+0x3b/0xf0 [<ffffffff8151671f>] ? register_client+0xaf/0xf0 [<ffffffffc018a784>] evergreen_init+0x14/0x380 [radeon] [<ffffffffc0117069>] radeon_device_init+0xa09/0xc60 [radeon] [<ffffffffc01194cd>] radeon_driver_load_kms+0x9d/0x220 [radeon] [<ffffffffc003d4d7>] drm_dev_register+0xa7/0xb0 [drm] [<ffffffffc003fb1f>] drm_get_pci_dev+0x8f/0x1e0 [drm] [<ffffffffc0115427>] radeon_pci_probe+0xd7/0x100 [radeon] [<ffffffff8142a6e5>] local_pci_probe+0x45/0xa0 [<ffffffff8142bb23>] pci_device_probe+0x103/0x150 [<ffffffff8151e18c>] driver_probe_device+0x22c/0x440 [<ffffffff8151e471>] __driver_attach+0xd1/0xf0 [<ffffffff8151e3a0>] ? driver_probe_device+0x440/0x440 [<ffffffff8151babc>] bus_for_each_dev+0x6c/0xc0 [<ffffffff8151d87e>] driver_attach+0x1e/0x20 [<ffffffff8151d2c3>] bus_add_driver+0x1c3/0x280 [<ffffffff8151edc0>] driver_register+0x60/0xe0 [<ffffffff8142a04c>] __pci_register_driver+0x4c/0x50 [<ffffffffc003fd50>] drm_pci_init+0xe0/0x110 [drm] [<ffffffffc0286000>] ? 0xffffffffc0286000 [<ffffffffc0286098>] radeon_init+0x98/0xad [radeon] [<ffffffff81002123>] do_one_initcall+0xb3/0x1f0 [<ffffffff81202721>] ? __vunmap+0x81/0xd0 [<ffffffff81222832>] ? kmem_cache_alloc_trace+0x182/0x1d0 [<ffffffff811b6a9c>] ? do_init_module+0x27/0x1d8 [<ffffffff811b6ad4>] do_init_module+0x5f/0x1d8 [<ffffffff81130c60>] load_module+0x1fe0/0x27a0 [<ffffffff8112d6b0>] ? __symbol_put+0x60/0x60 [<ffffffff8113156e>] SYSC_init_module+0x14e/0x190 [<ffffffff811316de>] SyS_init_module+0xe/0x10 [<ffffffff81003d92>] do_syscall_64+0x62/0x110 [<ffffffff817e0821>] entry_SYSCALL64_slow_path+0x25/0x25 ---[ end trace c8b5aa271327388b ]--- [drm:radeon_get_bios [radeon]] *ERROR* Unable to locate a BIOS ROM radeon 0000:01:00.0: Fatal error during GPU init [drm] radeon: finishing device.
*** Bug 1352272 has been marked as a duplicate of this bug. ***
Any news on this matter ? Kernel 4.5.7 is even disappeared from repo which is the last working kernel
just updated to kernel 4.6.7-300.....problem still there
Kernel 4.7.2-201 problem still there
Appears to be an upstream kernel bug. There's a test patch at https://bugzilla.kernel.org/show_bug.cgi?id=175391
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.