https://bugzilla.kernel.org/show_bug.cgi?id=85491
Bug ID: 85491 Summary: radeon 0000:01:00.0: Fatal error during GPU init Product: Drivers Version: 2.5 Kernel Version: 3.16.3-200.fc20.x86_64 Hardware: All OS: Linux Tree: Fedora Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri@kernel-bugs.osdl.org Reporter: zermond@gmail.com Regression: No
Created attachment 152241 --> https://bugzilla.kernel.org/attachment.cgi?id=152241&action=edit journalctl
hello,
if I want upgrade kernel 3.11.* to 3.16.* I have subj problems (radeon 0000:01:00.0: Fatal error during GPU init). With kernel 3.11.* all working.
I attached systemctl --system (last booting with kernel 3.16*), uname -a, dmesg, lspci
https://bugzilla.kernel.org/show_bug.cgi?id=85491
--- Comment #1 from Zermond zermond@gmail.com --- Created attachment 152251 --> https://bugzilla.kernel.org/attachment.cgi?id=152251&action=edit dmesg
https://bugzilla.kernel.org/show_bug.cgi?id=85491
--- Comment #2 from Zermond zermond@gmail.com --- Created attachment 152261 --> https://bugzilla.kernel.org/attachment.cgi?id=152261&action=edit lspci
https://bugzilla.kernel.org/show_bug.cgi?id=85491
--- Comment #3 from Zermond zermond@gmail.com --- Created attachment 152271 --> https://bugzilla.kernel.org/attachment.cgi?id=152271&action=edit uname-a with working kernel
https://bugzilla.kernel.org/show_bug.cgi?id=85491
Zermond zermond@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Tree|Fedora |Mainline
https://bugzilla.kernel.org/show_bug.cgi?id=85491
Alex Deucher alexdeucher@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |alexdeucher@gmail.com
--- Comment #4 from Alex Deucher alexdeucher@gmail.com --- Can you narrow down when the problem started? Even better, can you bisect?
https://bugzilla.kernel.org/show_bug.cgi?id=85491
--- Comment #5 from Zermond zermond@gmail.com --- (In reply to Alex Deucher from comment #4)
Can you narrow down when the problem started? Even better, can you bisect?
As soon as I updated the kernel. At version 3.11, everything was fine with version 3.16 of the problem.
https://bugzilla.kernel.org/show_bug.cgi?id=85491
--- Comment #6 from Alex Deucher alexdeucher@gmail.com --- (In reply to Zermond from comment #5)
(In reply to Alex Deucher from comment #4)
Can you narrow down when the problem started? Even better, can you bisect?
As soon as I updated the kernel. At version 3.11, everything was fine with version 3.16 of the problem.
Can you narrow it down any more than that? Does 3.12 work ok? 3.13? etc.
https://bugzilla.kernel.org/show_bug.cgi?id=85491
--- Comment #7 from Zermond zermond@gmail.com --- (In reply to Alex Deucher from comment #6)
(In reply to Zermond from comment #5)
(In reply to Alex Deucher from comment #4)
Can you narrow down when the problem started? Even better, can you bisect?
As soon as I updated the kernel. At version 3.11, everything was fine with version 3.16 of the problem.
Can you narrow it down any more than that? Does 3.12 work ok? 3.13? etc.
I'm sorry, I do not know how to use the old kernel. I installed 3.17, but it also did not work. I installed the boot loader to the kernel boot 3.17 1 level and made dmesg, journalctl -xn I am attached.
https://bugzilla.kernel.org/show_bug.cgi?id=85491
--- Comment #8 from Zermond zermond@gmail.com --- Created attachment 152401 --> https://bugzilla.kernel.org/attachment.cgi?id=152401&action=edit dmesg with 3.17 kernel
https://bugzilla.kernel.org/show_bug.cgi?id=85491
--- Comment #9 from Zermond zermond@gmail.com --- Created attachment 152411 --> https://bugzilla.kernel.org/attachment.cgi?id=152411&action=edit journalctl with 3.17 kernel
https://bugzilla.kernel.org/show_bug.cgi?id=85491
Marek kordikmarek@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |kordikmarek@gmail.com
--- Comment #10 from Marek kordikmarek@gmail.com --- Hi all, I have simillar problem and I tried to find some solution but with no success. Until kernel 3.15.10-201 worked everythink fine, but after upgrade to 3.16.2-200 (and every next kernel up to 3.16.7-200) instead radeon driver VESA is used (small resolution, kde gui is bit laggy probably because gpu acceleration is not used). My description maybe isn`t accurate but I will be happy to answer any of your questions. I have attached output of journalctl, lsmod, dmesg and Xorg.log for last working and first not working kernel. I am using Fedora 20 x64 on asus notebook M51Se with ati radeon HD3470 graphics.
https://bugzilla.kernel.org/show_bug.cgi?id=85491
--- Comment #11 from Marek kordikmarek@gmail.com --- Created attachment 157331 --> https://bugzilla.kernel.org/attachment.cgi?id=157331&action=edit logs for last working kernel
https://bugzilla.kernel.org/show_bug.cgi?id=85491
--- Comment #12 from Marek kordikmarek@gmail.com --- Created attachment 157341 --> https://bugzilla.kernel.org/attachment.cgi?id=157341&action=edit logs for first not working kernel
https://bugzilla.kernel.org/show_bug.cgi?id=85491
--- Comment #13 from Michel Dänzer michel@daenzer.net --- Marek, can you bisect or otherwise narrow down what kernel change caused the problem for you?
https://bugzilla.kernel.org/show_bug.cgi?id=85491
--- Comment #14 from Marek kordikmarek@gmail.com --- I can try, but this will be the first time I am going to do this. I have read this article: https://wiki.ubuntu.com/Kernel/KernelBisection and I am going to proceed accordingly.
https://bugzilla.kernel.org/show_bug.cgi?id=85491
--- Comment #15 from Marek kordikmarek@gmail.com --- Hi, I tried also Kubuntu with new kernel (newer than 3.15) and it was not working (previous versions of kernel were working also with Kubuntu) so it is not Fedora specific problem. The result of bisection is that the first bad commit is:
e5558d1a516fa6924fa8d53152b665d4c26f142e Merge branches 'dma-api', 'pci/virtualization', 'pci/msi', 'pci/misc' and 'pci/resource' into next
I took a look at code that was changed, but it is (yet) far beyond my abylities to come to some conclusion/quess. I am java developer and in the past I have written also few small C programs - so if needed I could help with some testing/debugging.
https://bugzilla.kernel.org/show_bug.cgi?id=85491
--- Comment #16 from Michel Dänzer michel@daenzer.net --- (In reply to Marek from comment #15)
The result of bisection is that the first bad commit is:
e5558d1a516fa6924fa8d53152b665d4c26f142e Merge branches 'dma-api', 'pci/virtualization', 'pci/msi', 'pci/misc' and 'pci/resource' into next
In general, if the result of a bisection is a merge commit, it indicates something might have gone wrong during the bisection. In this case, I suspect the problem might not happen every time even with affected kernels, so you need to test several times before declaring a commit good.
You can double-check this by testing commit e5558d1a516fa6924fa8d53152b665d4c26f142e again several times. Does it happen every time? If yes, test its parent commit(s) again several times. Does it never happen? If the answer to either question is no, I'm afraid you need to start the bisection again.
https://bugzilla.kernel.org/show_bug.cgi?id=85491
--- Comment #17 from Dave Airlie airlied@linux.ie --- this looks like a PCI regresion
окт 03 03:49:35 localhost.localdomain kernel: pci 0000:01:00.0: can't claim BAR 0 [mem 0xc0000000-0xcfffffff pref]: no compatible bridge window
окт 03 03:49:35 localhost.localdomain kernel: pci 0000:01:00.0: BAR 0: can't assign mem pref (size 0x10000000) окт 03 03:49:35 localhost.localdomain kernel: pci 0000:01:00.0: BAR 0: trying firmware assignment [mem size 0x10000000 pref] окт 03 03:49:35 localhost.localdomain kernel: pci 0000:01:00.0: BAR 0: [mem size 0x10000000 pref] conflicts with PCI Bus 0000:02 [mem 0xc0000000-0xc01fffff]
Bjorn?
Dave.
https://bugzilla.kernel.org/show_bug.cgi?id=85491
--- Comment #18 from Marek kordikmarek@gmail.com --- It seemd weird also to me, that result of the bisect was a merge so I tried to build one of parents of this wrong merge commit (before Michael's comment) and then I was merging to the parent the other parents one by one:
Parent: 518a6a34f645897ec3440e5cbcf53ced3493ee1c - good - I startded with this one Parent: 14574674e461077a9f4dd5eae050f622e8b8c084 - good - I merged this to the commit above Parent: 3cb30b73ad71b384c6289243d4ccd31ab90bce6f - good - I merged this to the commit above Parent: 034cd97ebda4062eb4402a6cf963ccd262caa86a - good - I merged this to the commit above Parent: 9edbcd2252b5ef148177c9f2c11a56469cf5db52 - good - I merged this to the commit above Parent: 67d29b5c6c40e91b124695e9250c2fd24915e24a - bad
After Dave's comment I decided to merge commit 67d29b5c6c40e91b124695e9250c2fd24915e24a as the last. Based on this I think that it is possible that the commit we are looking for is one of commits between 67d29b5c6c40e91b124695e9250c2fd24915e24a and 0b2d70764bb39242dcc49c0ebd10fcb8258ce5fa
https://bugzilla.kernel.org/show_bug.cgi?id=85491
Bjorn Helgaas bhelgaas@google.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |yinghai@kernel.org Component|Video(DRI - non Intel) |PCI Assignee|drivers_video-dri@kernel-bu |drivers_pci@kernel-bugs.osd |gs.osdl.org |l.org Regression|No |Yes
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠bugzilla.kernel.org