[Bug 1512120]
I updated the instructions I had put at https://launchpad.net/~yuri-sucupira/+archive/ubuntu/thunar1.6.10-fix ...in order to explain to the other users how to remove my "thunar1.6.10-fix" PPA, enable the "proposed" PPA and then upgrade Thunar to the proposed version 1.6.11. Thank you all for helping making Thunar great again. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512120 Title: [SRU] thunar crashes on file renaming To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1512120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512120]
"Comment 78 for bug 1512120 Kent Lion (klsu) wrote 50 minutes ago: #78 Thought this might help someone who knows Thunar better than I do figure out this bug. When I ran the Xubuntu Thunar test 1512120 on a desktop running XUbuntu 16.04 64 bit on a Dell GX620, not only does Thunar crash, but when Thunar refreshes, it doesn't always show filename changes, and sometimes when Thunar updates, some files don't display (as if the update information was collected while filenames were being changed, instead of after). When I compiled Thunar 1.6.10 and then used the Thunar-1.6.10.patch that I found on line, the crashes stopped, but the other symptoms did not. What might be important is that when I run XUbuntu 16.04 64 bin in VirtualBox on an old MacBook Pro, none of the symptoms occur." [source: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1512120/comments/78] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512120 Title: [SRU] thunar crashes on file renaming To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1512120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512120]
(In reply to slumbergod from comment #141) > @Yuri. Thunar hangs for me trying to view the contents of a newly inserted > flash drive. This is weird. I mean: I'm running 64-bit XUbuntu 16.04.1 LTS with Thunar 1.6.10-2ubuntu1+patch1 installed from my PPA (https://launchpad.net/~yuri-sucupira/+archive/ubuntu/thunar1.6.10-fix) and I'm experiencing no issues at all. I've already tested 2 different USB flash drives (a 4GB USB Kingston flash drive and a 32GB USB Sandisk flash drive) with "msdos" and "gpt" partition tables and "fat32" and "ext4" partitions, yet they always mount correctly and Thunar never crashes, hangs nor freezes, no matter how many times I eject and mount these flash drives again and how many file/folder move/rename operations I make Thunar to perform at these file systems. I also mount remotely shared folders from a samba (SMB) server and again Thunar behaves as it's supposed to. Maybe it's not related to Thunar itself. I'm currently using the generic stable vanilla kernel version 4.7.10 available at http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7.10/ 64-bit users may want to download and install the AMD64 DEBs: * linux-headers-4.7.10-040710_4.7.10-040710.201610220847_all.deb * linux-headers-4.7.10-040710-generic_4.7.10-040710.201610220847_amd64.deb * linux-image-4.7.10-040710-generic_4.7.10-040710.201610220847_amd64.deb 32-bit users may want to download and install the I386 DEBs: * linux-headers-4.7.10-040710_4.7.10-040710.201610220847_all.deb * linux-headers-4.7.10-040710-generic_4.7.10-040710.201610220847_i386.deb * linux-image-4.7.10-040710-generic_4.7.10-040710.201610220847_i386.deb Unfortunately, I'm not a developer, hence I can't fix Thunar myself: all I did was to pick Roy Richardson's patch, created the "patched" source code, sign it and upload it to a PPA I created. If upgrading the kernel to version 4.7.10 doesn't solve the issue I don't think I'll be of any help, sorry. :\ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512120 Title: [SRU] thunar crashes on file renaming To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1512120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512120]
(In reply to Kip from comment #132) > Hey Yuri. I just tried your Thunar packages for Yakkety and I can confirm > that I am unable to reproduce the crash we've all been having on file / > directory rename. Glad to hear that. I had only Xenial (*Ubuntu 16.04) packages on that PPA, but I've recently uploaded the Yakkety (*Ubuntu 16.10) and Wily (*Ubuntu 15.10) contents. I can confirm that after 1 month of testing I haven't experienced a single Thunar crash on Xenial. And now Kip confirmed that Yakkety isn't crashing either, after the update using the PPA. It seems likely that this patch will also work for Wily. I'm not experiencing the issue reported by Andreas (Thunar becoming unresponsive when trying to access another filesystem), I'm not sure why he's going through this kind of problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512120 Title: [SRU] thunar crashes on file renaming To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1512120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512120]
> After a LOT of pain (it took me some hours) I finally managed to sign my > sources and upload'em to a PPA. Here's the PPA: > > https://launchpad.net/~yuri-sucupira/+archive/ubuntu/thunar1.6.10-patched > > However, I noticed that APT is considering "1.6.10-2ubuntu1" as a newer > version than my "1.6.10-2ubuntu1~patch1" version. Does anyone know how I > shall version my packages, in order to make APT choose them instead of those > in version 1.6.10-2ubuntu1? I fixed this issue. I had to delete the PPA and create a new one. Here's the new PPA: https://launchpad.net/~yuri-sucupira/+archive/ubuntu/thunar1.6.10-fix I already tested it: if you add this PPA (which supports both 32-bit/i386 and 64-bit/amd64 systems) and run `sudo apt (dist-)upgrade` it will upgrade Thunar with the patched debs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512120 Title: [SRU] thunar crashes on file renaming To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1512120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512120]
(In reply to Kip from comment #124) > (In reply to Yuri R. Sucupira from comment #123) > > After a LOT of pain (it took me some hours) I finally managed to sign my > > sources and upload'em to a PPA. Here's the PPA: > > > > https://launchpad.net/~yuri-sucupira/+archive/ubuntu/thunar1.6.10-patched > > > > However, I noticed that APT is considering "1.6.10-2ubuntu1" as a newer > > version than my "1.6.10-2ubuntu1~patch1" version. Does anyone know how I > > shall version my packages, in order to make APT choose them instead of those > > in version 1.6.10-2ubuntu1? > > Hey Yuri, > > Well done. I unfortunately can't test because I'm sadly still running Wily, > but by the sounds of it we're all grateful for your contribution. You're welcome. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512120 Title: [SRU] thunar crashes on file renaming To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1512120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512120]
(In reply to haarp from comment #126) > Could we please keep the support and packaging stuff to a minimum here? > > I appreciate the work people do on getting these critical fixes packaged, > but this isn't a support forum. This section is for the bug itself. Ok, sorry. Well, if anyone doesn't manage to add my PPA or experience some difficulty while doing it, e-mail me (in order to avoid flooding this bug report). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512120 Title: [SRU] thunar crashes on file renaming To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1512120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512120]
(In reply to Kip from comment #117) > (In reply to Yuri R. Sucupira from comment #116) > > I've managed to build and install the (actually five) "patched" DEB > > packages. Now Thunar seems to be back to normal, although I still have more > > testing to do. > > > > I've uploaded those packages to my OneDrive: > > > > https://1drv.ms/f/s!AvGdllDm3m3njxZrQkEimLKwSsEI > > > > They're for 64-bit systems, only. > > > > For installation instructions and other info, please read the README.txt > > file that I've uploaded to that same folder. > > Hey Yuri. Thanks a lot. It might be better though if you consider pushing to > a PPA. That's a more "standard" method of distributing personal / testing > debs. I created a PPA and tried to upload data to it, but the process proved to be a real pain in the *ss. After a very long run (because I never had to do it before in my life), I finnaly managed to create a local key on my system, upload this key to the Ubuntu keyserver, confirm my id to the keyserver, and then sign the Code of Conduct. However, those were just the preliminary steps required to allow me to create a PPA and push files into it. And unfortunately I didn't succeed in uploading data to the PPA (I'm using dput, but something's going wrong). I thought I could push the DEB files to the PPA, but it's actually forbidden: one must push the sources, which I'm failing to do, maybe because I'm failing to find out how to sign the source-code and how to authenticate into the PPA in order to push the files into it. I'll try again later, but I'm under the impression that I won't succeed. My key expires in Sep. 02, 2017, so if I happen to succeed in uploading these patched files to a PPA it will stay "active" for 1 year, which I assume is more than enough time for a new Thunar release come up with this bug fixed. Anyway, I still don't know how to push these files to a PPA. I'll let you all know if I overcome this problem. In the meantime, I suggest downloading the DEBs from my OneDrive. Unfortunately it's the only cloud hosting method I currently know how to do. :-\ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512120 Title: [SRU] thunar crashes on file renaming To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1512120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512120]
(In reply to xb from comment #118) > (In reply to Yuri R. Sucupira from comment #116) > > (In reply to xb from comment #115) > > > (In reply to Roy Richardson from comment #114) > > > > Created attachment 6801 [details] > > > > Notes for patching Thunar on Ubuntu with patch #6779 > > > > > > > > > > > > I've successfully tested patch #6779 on Debian Stretch i386, Debian > > > > Stretch > > > > amd64, Xubuntu 16.04 amd64 and Arch x86_64. Here are my notes for > > > > patching > > > > and building Thunar on Ubuntu. I hope this works as well for you as it > > > > does > > > > for me. > > > > > > This looks great, is there a way that you could provide the patched .deb > > > file? I am afraid of doing that compiling thing, as I never did it. I am > > > running Xubuntu 16.04 amd64 too so I think it will be working ok, is that > > > true? > > > Thanks. > > > xb. > > > > I've managed to build and install the (actually five) "patched" DEB > > packages. Now Thunar seems to be back to normal, although I still have more > > testing to do. > > > > I've uploaded those packages to my OneDrive: > > > > https://1drv.ms/f/s!AvGdllDm3m3njxZrQkEimLKwSsEI > > > > They're for 64-bit systems, only. > > > > For installation instructions and other info, please read the README.txt > > file that I've uploaded to that same folder. > > Thank you, Yuri, I will try it, hope it will work on my machine. > xb You're welcome. After I executed `sudo apt-get dist-upgrade`, APT replaced the patched version by the buggy repo version. Thus, I had to manually reinstall the patched packages. In order to prevent it from happening again, I held the 5 packages, which is done by running this command: sudo apt-mark hold thunar thunar-dbg thunar-data libthunarx-2-0 libthunarx-2-dev This will prevent APT from replacing those packages during an `upgrade` or `dist-upgrade`. When a new Thunar release becomes available, all the user has to do is to run this command: sudo apt-mark unhold thunar thunar-dbg thunar-data libthunarx-2-0 libthunarx-2-dev ...and then run `sudo apt-get upgrade` or `sudo apt-get dist-upgrade` to cause APT to install the new Thunar release. I've updated the README.txt file on my OneDrive. Now it explains how to hold/unhold DEB packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512120 Title: [SRU] thunar crashes on file renaming To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1512120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512120]
(In reply to Kip from comment #121) > (In reply to Yuri R. Sucupira from comment #120) > > And > > unfortunately I didn't succeed in uploading data to the PPA (I'm using dput, > > but something's going wrong). I thought I could push the DEB files to the > > PPA, but it's actually forbidden: one must push the sources, which I'm > > failing to do, maybe because I'm failing to find out how to sign the > > source-code and how to authenticate into the PPA in order to push the files > > into it. I'll try again later, but I'm under the impression that I won't > > succeed. > > Hey Yuri, > > Yes, working with a PPA (sbuild) can be a real pain. I've learned over the > years how to do it. All of the things you raised are definitely annoying, > but there's actually very good reasons for all of them that make packages > better. This is the reason why Debian has such a very high quality selection > of packages because of their high standards. I really recommend checking out > the Debian Policy Manual at some point for future benefit too. After a LOT of pain (it took me some hours) I finally managed to sign my sources and upload'em to a PPA. Here's the PPA: https://launchpad.net/~yuri- sucupira/+archive/ubuntu/thunar1.6.10-patched However, I noticed that APT is considering "1.6.10-2ubuntu1" as a newer version than my "1.6.10-2ubuntu1~patch1" version. Does anyone know how I shall version my packages, in order to make APT choose them instead of those in version 1.6.10-2ubuntu1? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512120 Title: [SRU] thunar crashes on file renaming To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1512120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512120]
(In reply to Roy Richardson from comment #114) > Created attachment 6801 [details] > Notes for patching Thunar on Ubuntu with patch #6779 > > > I've successfully tested patch #6779 on Debian Stretch i386, Debian Stretch > amd64, Xubuntu 16.04 amd64 and Arch x86_64. Here are my notes for patching > and building Thunar on Ubuntu. I hope this works as well for you as it does > for me. @Roy: thank you very much for the notes on patching and building Thunar on Ubuntu! It's been 4 days since I've built and installed the patched binaries and so far Thunar hasn't had any crash related to file moving/renaming. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512120 Title: [SRU] thunar crashes on file renaming To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1512120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512120]
(In reply to xb from comment #115) > (In reply to Roy Richardson from comment #114) > > Created attachment 6801 [details] > > Notes for patching Thunar on Ubuntu with patch #6779 > > > > > > I've successfully tested patch #6779 on Debian Stretch i386, Debian Stretch > > amd64, Xubuntu 16.04 amd64 and Arch x86_64. Here are my notes for patching > > and building Thunar on Ubuntu. I hope this works as well for you as it does > > for me. > > This looks great, is there a way that you could provide the patched .deb > file? I am afraid of doing that compiling thing, as I never did it. I am > running Xubuntu 16.04 amd64 too so I think it will be working ok, is that > true? > Thanks. > xb. I've managed to build and install the (actually five) "patched" DEB packages. Now Thunar seems to be back to normal, although I still have more testing to do. I've uploaded those packages to my OneDrive: https://1drv.ms/f/s!AvGdllDm3m3njxZrQkEimLKwSsEI They're for 64-bit systems, only. For installation instructions and other info, please read the README.txt file that I've uploaded to that same folder. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512120 Title: [SRU] thunar crashes on file renaming To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1512120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512120] Re: [SRU] thunar crashes on file renaming
I'm kinda regretting having deleted my "thunar1.6.11-proposed" PPA: by enabling the "proposed" repository, the average user may accidentally execute something like "sudo apt-get dist-upgrade" and then upgrade not only Thunar but his/her ***entire system*** with all the testing/proposed packages, which may be dangerous or at least not desireable as a "general rule". Installing only Thunar packages from a separate PPA like my (now deleted) "thunar1.6.11-proposed" was a "safer" approach. Anyway... Instead of creating another "proposed" PPA, I decided to update the text/description at my "thunar1.6.10-fix" PPA hosted at https://launchpad.net/~yuri-sucupira/+archive/ubuntu/thunar1.6.10-fix ...with instructions on how to: (1) Enable the "proposed" PPA; (2) Upgrade ***only*** Thunar; and (3) Then disable the "proposed" PPA, for the sake of safety/stability. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512120 Title: [SRU] thunar crashes on file renaming To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1512120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512120] Re: [SRU] thunar crashes on file renaming
@flocculant I wasn't aware of that. Thanks for the clarification. :) I've just deleted the PPA so far hosted at https://launchpad.net/~yuri- sucupira/+archive/ubuntu/thunar1.6.11-proposed ...and then I updated the instructions I had put at https://launchpad.net/~yuri-sucupira/+archive/ubuntu/thunar1.6.10-fix ...in order to explain to the other users how to remove my "thunar1.6.10-fix" PPA, enable the "proposed" PPA and then upgrade Thunar to the proposed version 1.6.11. Thank you all for helping making Thunar great again. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512120 Title: [SRU] thunar crashes on file renaming To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1512120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512120] Re: [SRU] thunar crashes on file renaming
To those interested in testing the proposed Thunar 1.6.11 but don't know how to build the package from the source code: I've created a PPA here: https://launchpad.net/~yuri- sucupira/+archive/ubuntu/thunar1.6.11-proposed Just follow the instructions there and see if the new version runs smoothly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512120 Title: [SRU] thunar crashes on file renaming To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1512120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512120] Re: thunar crashes on file renaming
"Comment 78 for bug 1512120 Kent Lion (klsu) wrote 50 minutes ago: #78 Thought this might help someone who knows Thunar better than I do figure out this bug. When I ran the Xubuntu Thunar test 1512120 on a desktop running XUbuntu 16.04 64 bit on a Dell GX620, not only does Thunar crash, but when Thunar refreshes, it doesn't always show filename changes, and sometimes when Thunar updates, some files don't display (as if the update information was collected while filenames were being changed, instead of after). When I compiled Thunar 1.6.10 and then used the Thunar-1.6.10.patch that I found on line, the crashes stopped, but the other symptoms did not. What might be important is that when I run XUbuntu 16.04 64 bin in VirtualBox on an old MacBook Pro, none of the symptoms occur." [source: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1512120/comments/78] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512120 Title: thunar crashes on file renaming To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1512120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512120] Re: thunar crashes on file renaming
@Dani (damufo), @Si Dedman (si-dedman) and @cyrille borne (cyrille): isn't the issue solved after you add the PPA below and run the APT "update" and "dist-upgrade" commands (as explained at the PPA)? https://launchpad.net/~yuri-sucupira/+archive/ubuntu/thunar1.6.10-fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512120 Title: thunar crashes on file renaming To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1512120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608042] Re: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system
While the first good commit isn't applied downstream (in order to fix previous kernel versions), I currently recommend using stable kernel 4.7.4, available at http://kernel.ubuntu.com/~kernel- ppa/mainline/v4.7.4/ There are newer stable kernel versions available, but I haven't tested them. I can confirm, though, that kernel 4.7.4 solves the "freezing" issue. One running 64-bit Ubuntu Linux and interested in installing kernel 4.7.4 must download these files: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7.4/linux- headers-4.7.4-040704_4.7.4-040704.201609150330_all.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7.4/linux- headers-4.7.4-040704-generic_4.7.4-040704.201609150330_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7.4/linux- image-4.7.4-040704-generic_4.7.4-040704.201609150330_amd64.deb ...then open a shell terminal window, "cd" into the folder where these 3 DEB packages were downloaded to, and then run the command "sudo dpkg -i linux-*.deb" (without the quotation marks) in order to manually install the three DEBs. Then reboot the system. For a complete list of kernels, visit http://kernel.ubuntu.com/~kernel- ppa/mainline/?C=N;O=D PS: for 32-bit systems, the 3 DEBs to be downloaded and installed are: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7.4/linux- headers-4.7.4-040704_4.7.4-040704.201609150330_all.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7.4/linux- headers-4.7.4-040704-generic_4.7.4-040704.201609150330_i386.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7.4/linux- image-4.7.4-040704-generic_4.7.4-040704.201609150330_i386.deb If your system is hanging/freezing to the point that you can't even login into the GUI, power off your computer, then turn it on again and press the Esc key until you get into the GRUB menu. Afterwards, press the E key in order to edit the grub menu, then go to the first instance of the code "$vt_handoff" and add the "nomodeset" parameter right before it. Example: => Before = quiet splash $vt_handoff => After = quiet splash nomodeset $vt_handoff After adding the "nomodeset" parameter, press the F10 key (or the Ctrl X key combo). Linux will boot with Kernel Mode Setting (KMS) disabled, then you will be able to log into the Graphical User Interface (GUI) and then download and install a stable kernel. Sorry for the long comment that is not a relevant info for those investigating the bug. It just so other users know how to "deal" with the bug while it's not fixed/removed from previous kernel versions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579374] Re: amdgpu causes NULL pointer dereference when trying to use Topaz (Radeon R7 M265) GPU
*** This bug is a duplicate of bug 1608042 *** https://bugs.launchpad.net/bugs/1608042 Bug report https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- amdgpu/+bug/1608042 is related to this one. ** This bug has been marked a duplicate of bug 1608042 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579374 Title: amdgpu causes NULL pointer dereference when trying to use Topaz (Radeon R7 M265) GPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608042] Re: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system
@Timo Aaltonen (tjaalton): after reading your comment, I decided to install kernel 4.4.0-23.41, but it isn't available on the repo anymore, so I installed kernel 4.4.0-24 (if "that revert is already in the xenial kernel since Ubuntu-4.4.0-23.41", then installing kernel 4.4.0-24 shouldn't be a problem). Then I ran some tests and my system "froze". I had to press the power button of my laptop to shut it down (hardware power off). First I executed "DRI_PRIME=1 glxgears" on the shell: all I got was a black screen. Then I executed "xscreensaver-demo" and previewed the "Molecule" screensaver, twice: at the first time, nothing happened (as usual. This is normal), but at the second time the screen locked and I had to use the "Ctrl Alt F1" combo to switch to TTYS1 and restart lightdm (with the command "sudo service lightdm restart"). Then I returned to TTYS7 (Ctrl Alt F7) and hit the "Power off" (software) button, but the system hanged, so I had to press the physical "power" button of my laptop. If someone builds some 4.4.X kernel with the "good commit" e9bef455af8eb0e837e179aab8988ae2649fd8d3 (mentioned in comment #33) applied/patched, I can test it and confirm if the bug is still there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575000] Re: font glyph corruption on dialog box
Enabling OpenGL rendering also solved this for me (the attached file shows which checkbox must be enabled/marked/checked, at the LibreOffice GUI). I'm running LibreOffice 5.1.4.2 on a 64-bit XUbuntu 16.04 "Xenial Xerus" system. My computer is a Dell laptop (Dell Inspiron 5548) which has hybrid graphics (it has two GPU - Graphics Processing Units): GPU 1 is an Intel Broadwell-U Integrated Graphics (it's embedded into the i7 CPU/processor), while GPU 2 is an Advanced Micro Devices [AMD/ATI] Topaz XT [Radeon R7 M260/M265] (it's a PCI Express 3.0 graphics card). *Ubuntu (Ubuntu, XUbuntu, KUbuntu...) 16.04 distros ship with kernel 4.4.X, which has a bug that causes malfunction of the kernel with the open source "amdgpu" and "radeon" graphics drivers (they superseded the proprietary "fglrx" driver by AMD). See bug #1608042 (https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- amdgpu/+bug/1608042). Hence, if your computer has any AMD GPU (despite of your computer having hybrid graphics or not), and if your distro is *Ubuntu 16.04 and you already installed MESA (OpenGL support for Linux) and activated OpenGL rendering in LibreOffice, but the issue remais, it is likely that your system is affected by the kernel/AMD bug. It's thus recommended to download and install a further stable kernel, like e.g. kernel v4.7.2: - For 64-bit *Ubuntu, download these three files: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7.2/linux-headers-4.7.2-040702_4.7.2-040702.201608201334_all.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7.2/linux-headers-4.7.2-040702-generic_4.7.2-040702.201608201334_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7.2/linux-image-4.7.2-040702-generic_4.7.2-040702.201608201334_amd64.deb - For 32-bit *Ubuntu, download these three files: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7.2/linux-headers-4.7.2-040702_4.7.2-040702.201608201334_all.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7.2/linux-headers-4.7.2-040702-generic_4.7.2-040702.201608201334_i386.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7.2/linux-image-4.7.2-040702-generic_4.7.2-040702.201608201334_i386.deb ...then open a shell terminal window, cd (change directory) into the folder where you donwloaded those DEB packages into, then install the packages and restart your system. For instance, if you downloaded those DEB packages into your downloads folder (/home/your-username/Downloads), then this command will cd into your downloads folder, install the downloaded packages and restart your system (your password will be asked by the shell): cd ~/Downloads ; sudo dpkg -i linux-*.deb ; telinit 6 ** Attachment added: "Activate OpenGL rendering." https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1575000/+attachment/4738500/+files/opengl_rendering.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575000 Title: font glyph corruption on dialog box To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1575000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608042] Re: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system
** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1608042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608042] Re: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system
Note: on that entire PDF table, I used "good" meaning "has bug" and I used "bad" meaning "is bug free", but where it reads "e9bef455af8eb0e837e179aab8988ae2649fd8d3 is the first good commit" the word "good" really means "good": in fact, commit e9bef455af8eb0e837e179aab8988ae2649fd8d3 removed the bug that is present in previous kernel builds. Hence, commit e9bef455af8eb0e837e179aab8988ae2649fd8d3 caused all further kernel commits to build without the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1608042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608042] Re: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system
Hello. It took me some days and 26 kernel compilations, but I finally found the first good commit. I thought kernel 4.6-rc1 carried the first good commit, but it turns out it also had the bug: the first commit is in kernel 4.6-rc4. Here's the output of my last RCB (reverse commit bisect) report: "e9bef455af8eb0e837e179aab8988ae2649fd8d3 is the first good commit commit e9bef455af8eb0e837e179aab8988ae2649fd8d3 Author: Alex Deucher Date: Mon Apr 25 13:12:18 2016 -0400 Revert ""drm/amdgpu: disable runtime pm on PX laptops without dGPU power control"" This reverts commit bedf2a65c1aa8fb29ba8527fd00c0f68ec1f55f1. See the radeon revert for an extended description. Cc: sta...@vger.kernel.org :04 04 5d8682184f857b970ced85be0fae2d4c177cad24 fd74c294984fd4c22ed116ec6a91962a70882b91 M drivers" The attached PDF is a table with the description of all the RCB builds I performed until I reached the first bug-free commit/build. Notice that I had to use "git bisect good" for bad commits and "git bisect bad" for good commits because it's a reverse method. Thus, "good" means bad (has bug) and "bad" means good (is bug-free). ** Attachment added: "RCB table (all kernel builds I had to perform until I reached the first good commit)" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1608042/+attachment/4738005/+files/rcb.pdf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1608042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512120] Re: thunar crashes on file renaming
You're welcome. I've been testing the patched DEBs for 5 days already and so far the bug didn't happen. The patch "rename.patch" was introduced by Roy Richardson (https://bugzilla.xfce.org/show_bug.cgi?id=12264#c114), then I picked the patch, applied it to Thunar's original source-code and then created and signed the patched version that I uploaded to the PPA. Hope it helps other Xenial users. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512120 Title: thunar crashes on file renaming To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1512120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512120] Re: thunar crashes on file renaming
I've created a PPA hosting the patched DEB packages that fix this issue for *Ubuntu 16.04: https://launchpad.net/~yuri-sucupira/+archive/ubuntu/thunar1.6.10-fix It's available for 32-bit/i386 and 64-bit/amd64 systems, but I haven't tested with other releases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512120 Title: thunar crashes on file renaming To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1512120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512120] Re: thunar crashes on file renaming
I can confirm that this bug is present in 64-bit XUbuntu 16.04 "Xenial" (kernel version is 4.6.0-040600rc7-generic, Thunar version is 1.6.10-2ubuntu1). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512120 Title: thunar crashes on file renaming To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1512120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512120] Re: thunar crashes on file renaming
I can confirm that this bug is still present in Thunar 1.6.10 (build "1.6.10-2ubuntu1"). My OS is 64-bit XUbuntu 16.04 "Xenial" running kernel 4.6-rc7 (build "4.6.0-040600rc7-generic"). I've been looking into the logs is here is the same and only error that's always (repeatedly) generated after every crash: "PyGIWarning: Wnck was imported without specifying a version first. Use gi.require_version('Wnck', '3.0') before import to ensure that the right version gets loaded. from gi.repository import GLib, Wnck, GdkX11, Gdk" The attachment above (comment #54) is my most recent Thunar crash log file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512120 Title: thunar crashes on file renaming To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1512120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512120] Re: thunar crashes on file renaming
** Attachment added: "Thunar crash log" https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1512120/+attachment/4717089/+files/update-notifier-crash-_var_crash__usr_bin_thunar.1000.crash.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512120 Title: thunar crashes on file renaming To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1512120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608042] Re: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system
** Tags added: radeon -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1608042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579374] Re: amdgpu causes NULL pointer dereference when trying to use Topaz (Radeon R7 M265) GPU
As I reported here: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- amdgpu/+bug/1608042/comments/31 ...my computer is exactly the same (Dell Inspiron 5448 laptop, BIOS A06, hybrid graphics Intel Broadwell - module i915 + AMD Topaz XT R7 M260/M265 - module amdgpu) and after installing 64-bit XUbuntu 16.04 "Xenial" I got the same problem, because of the kernel 4.4. I got rid of the kernel-AMD GPU issues after doing some reverse commit and identifying that kernel 4.6-rc1 received a "good commit" that fixed the problem. I'm currently running 4.6-rc7, but I can confirm that from 4.6-rc1 ahead the "NULL pointer dereference" bug's gone. From kernel 4.6-rc1 or newer I'm able to execute "DRI_PRIME=1 glxgears" without experiencing any issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579374 Title: amdgpu causes NULL pointer dereference when trying to use Topaz (Radeon R7 M265) GPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1603989] Re: Radeon R7 not work in ubuntu xenial
Please download these files (kernel version 4.7): http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7/linux- headers-4.7.0-040700_4.7.0-040700.201608021801_all.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7/linux- headers-4.7.0-040700-generic_4.7.0-040700.201608021801_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7/linux- image-4.7.0-040700-generic_4.7.0-040700.201608021801_amd64.deb Then install the three files and reboot your system so it loads the 4.7 kernel. How to install these packages: 1) Execute this command in order to install Gdebi: sudo apt-get install gdebi -y 2) Right-click onto any .DEB file then go to "Properties" and define "Gdebi" as the default app to open .DEB packages. 3) Double-click the linux- image-4.7.0-040700-generic_4.7.0-040700.201608021801_amd64.deb file so Gdebi will open it. Click the "Install Package" button and provide your password. 4) Repeat the installation step (item 3, above) with files linux- headers-4.7.0-040700_4.7.0-040700.201608021801_all.deb and linux- headers-4.7.0-040700-generic_4.7.0-040700.201608021801_amd64.deb An alternative way of installing these packages is to open a shell terminal window, then cd (change directory) into the directory where those three .DEB files were downloaded into (make sure those 3 .DEB files are the ONLY .DEB files present in the folder), and then execute this installation command: sudo dpkg -i *.deb Once you install kernel 4.7, reboot your system. GRUB will select 4.7-generic by default. See if this solves the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603989 Title: Radeon R7 not work in ubuntu xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1603989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608042] Re: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system
I performed some reverse commit bisect and thus tested some 4.X kernels. Here's the result: 1) The bug is present in all 4.4.X kernels until kernel "4.5.7-yakkety" (build 4.5.7-040507-generic), which's the last one carrying the bad commit. Starting on kernel "4.6-rc1" (build 4.6.0-040600rc1-generic), the bug is gone. Hence, a "good commit" removed the bad commit on 4.6-rc1. ** Attachment added: "Comparision chart among buggy and non-buggy 4.X kernel versions/builds." https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1608042/+attachment/4714518/+files/COMMITS.pdf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1608042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608042] Re: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system
*** This bug is a duplicate of bug 1579374 *** https://bugs.launchpad.net/bugs/1579374 ** This bug has been marked a duplicate of bug 1579374 amdgpu causes NULL pointer dereference when trying to use Topaz (Radeon R7 M265) GPU -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1608042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608042] Re: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system
** Description changed: COMPUTER: Dell Inspiron 5548 laptop CPU: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz GRAPHICS: Intel-AMD hybrid: - CPU-integrated: Intel Corporation Broadwell-U Integrated Graphics (driver: i915) - GPU: Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260/M265] (driver: amdgpu) OPERATING SYSTEM: 64-bit GNU/Linux XUbuntu 16.04 "Xenial" KERNEL: 4.4.0-31-generic PROBLEM: system hangs / freezes very frequently. I have Xscreensaver installed and noticed that when it's running an OpenGL animation (screensaver) and I move the touchpad pointer the screen freezes. I can still turn the keyboard LED backlight on and off (hence: keyboard doesn't stop working) but the pointer won't move (touchpad is locked) and I can't Ctrl-Alt-F[1-6] (switch TTY/terminals). Only solution is to power off my laptop (press and hold the power button). I usually select the "Molecule" screensaver (it uses OpenGL), then I click the "preview" button and wait for about 20 seconds, then I click the touchpad and the computer hangs. When I used XUbuntu 14.04 "Trusty" with AMD's fglrx (proprietary) driver I didn't experience such issue. After upgrading to 16.04 "Xenial" (which doesn't support fglrx module/driver) amdgpu module is loaded by default but very frequently hangs the entire system. Sometimes I'm quick enough to go to TTYS1 and then I get to see some messages such as "HARD LOCKUP on CPU0" and "HARD LOCKUP on CPU1". However, it's not a hardware problem because I've already executed the Dell Hardware Diagnostics straight from the boot (it's an EFI utility), it tested all the hardware components (CPU, GPU, RAM, keyboard, touchpad, hard disk etc.) and didn't detect any faulty component. The attached file "amdgpu-bug.txt" is the reason why I'm pretty - convinced that the problem is being caused by the amdgpu driver. + convinced that the problem is being caused by the amdgpu driver + (although it seems to be related to how it interacts with the kernel, + thus maybe the problem is kernel-related). - WORKAROUND: Boot from GRUB with the nomodeset parameter. The graphics performance becomes terribly slow. - --- + WORKAROUND: Boot from GRUB with the nomodeset parameter. The graphics + performance becomes terribly slow. + + - + Apport output: + ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: - + CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Dell Broadwell-U Integrated Graphics [1028:0643] -Subsystem: Dell Topaz XT [Radeon R7 M260/M265] [1028:0643] + Â Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) + Â Â Â Subsystem: Dell Broadwell-U Integrated Graphics [1028:0643] + Â Â Â Subsystem: Dell Topaz XT [Radeon R7 M260/M265] [1028:0643] InstallationDate: Installed on 2016-07-29 (1 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 5548 Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=24cb3fff-5c01-4674-9c59-58d7d776fd70 ro quiet splash nomodeset vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Renderer: Software Tags: xenial ubuntu Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev sambashare scanner sudo tape users video _MarkForUpload: True dmi.bios.date: 10/12/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0YDTG3 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A06 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd10/12/2015:svnDellInc.:pnInspiron5548:pvrA06:rvnDellInc.:rn0YDTG3:rvrA02:cvnDellInc.:ct8:cvrA06: dmi.product.name: Inspiron 5548 dmi.product.version: A06 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-int
[Bug 1608042] Re: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system
@Christopher M. Penalver: I've just read comment #26. Ok, I'll test a little more to confirm if v4.6-rc7-wily really fixed this bug and, if it really did, I'll reverse commit bisect until I find the last "downstream" (< v4.6-rc7-wily) kernel that carried the bad commit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1608042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608042] Re: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system
@Christopher M. Penalver: thanks for the tip about apport-collect. I'll keep that in mind in future bug reports. Hopefully there won't be any. :) I'm currently testing kernel 4.6.0-040600rc7-generic ("v4.6-rc7-wily") and so far (~5 hours of intensive use running several 3D applications that would easily cause a system freeze / lockup) I haven't experienced any issue. Looks like the bug is gone on kernel v4.6-rc7-wily. I'll keep testing this kernel for a bit more (just to make sure the bug is really gone) and then test kernel 4.7, as suggested by you and Peter Wu (to check if the bug isn't back on upstream kernel). If everything is ok, I understand that the next step will be to fully reverse commit bisect from kernel v4.6-rc7-wily downwardly (towards kernel 4.4.X) in order to identify the last bad commit followed immediately by the first good one. Right? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1608042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608042] Re: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system
@Peter Wu: ok, got it. Sorry for any inconvenience (for subscribing hybrid-graphic-linux to this bug). By the way: thanks for the tip. I decided to test some different kernels and see how they behave with amdgpu. Some 4.4.X and 4.5.X kernels didn't work either, but I'm currently testing kernel 4.6.0-040600rc7-generic (version "v4.6-rc7-wily") with the module amdgpu loaded along with modules amd_iommu_v2, amdkfd, drm, drm_kms_helper, i915, ttm, video etc. and so far my laptop hasn't stopped (hang/freeze) not even once! It's been ~5 hours of testing, so far, and I already performed a lot of tasks that usually cause the lockups (previewing OpenGL screensavers on Xscreensaver, running 3D games, 3D CAD applications et cetera: all these would cause a CPU hard lockup or kernel panic) but I didn't experience any issue with kernel v4.6-rc7-wily. I will also test kernel 4.7 as you suggested. Thank you for your feedback. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1608042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608042] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1608042/+attachment/4710554/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1608042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608042] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1608042/+attachment/4710553/+files/Xrandr.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1608042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608042] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1608042/+attachment/4710551/+files/XorgLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1608042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608042] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1608042/+attachment/4710550/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1608042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608042] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1608042/+attachment/4710552/+files/XorgLogOld.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1608042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608042] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1608042/+attachment/4710549/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1608042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608042] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1608042/+attachment/4710544/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1608042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608042] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1608042/+attachment/4710548/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1608042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608042] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1608042/+attachment/4710547/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1608042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608042] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1608042/+attachment/4710545/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1608042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608042] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1608042/+attachment/4710546/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1608042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608042] LightdmDisplayLog.gz
apport information ** Attachment added: "LightdmDisplayLog.gz" https://bugs.launchpad.net/bugs/1608042/+attachment/4710542/+files/LightdmDisplayLog.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1608042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608042] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1608042/+attachment/4710539/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1608042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608042] Re: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system
apport information ** Tags added: ubuntu ** Description changed: COMPUTER: Dell Inspiron 5548 laptop CPU: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz GRAPHICS: Intel-AMD hybrid: - CPU-integrated: Intel Corporation Broadwell-U Integrated Graphics (driver: i915) - GPU: Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260/M265] (driver: amdgpu) OPERATING SYSTEM: 64-bit GNU/Linux XUbuntu 16.04 "Xenial" KERNEL: 4.4.0-31-generic PROBLEM: system hangs / freezes very frequently. I have Xscreensaver installed and noticed that when it's running an OpenGL animation (screensaver) and I move the touchpad pointer the screen freezes. I can still turn the keyboard LED backlight on and off (hence: keyboard doesn't stop working) but the pointer won't move (touchpad is locked) and I can't Ctrl-Alt-F[1-6] (switch TTY/terminals). Only solution is to power off my laptop (press and hold the power button). I usually select the "Molecule" screensaver (it uses OpenGL), then I click the "preview" button and wait for about 20 seconds, then I click the touchpad and the computer hangs. When I used XUbuntu 14.04 "Trusty" with AMD's fglrx (proprietary) driver I didn't experience such issue. After upgrading to 16.04 "Xenial" (which doesn't support fglrx module/driver) amdgpu module is loaded by default but very frequently hangs the entire system. Sometimes I'm quick enough to go to TTYS1 and then I get to see some messages such as "HARD LOCKUP on CPU0" and "HARD LOCKUP on CPU1". However, it's not a hardware problem because I've already executed the Dell Hardware Diagnostics straight from the boot (it's an EFI utility), it tested all the hardware components (CPU, GPU, RAM, keyboard, touchpad, hard disk etc.) and didn't detect any faulty component. The attached file "amdgpu-bug.txt" is the reason why I'm pretty convinced that the problem is being caused by the amdgpu driver. - WORKAROUND: Boot from GRUB with the nomodeset parameter. The graphics - performance becomes terribly slow. + WORKAROUND: Boot from GRUB with the nomodeset parameter. The graphics performance becomes terribly slow. + --- + ApportVersion: 2.20.1-0ubuntu2.1 + Architecture: amd64 + BootLog: + + CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' + CompositorRunning: None + CurrentDesktop: XFCE + DistUpgraded: Fresh install + DistroCodename: xenial + DistroRelease: Ubuntu 16.04 + DistroVariant: ubuntu + ExtraDebuggingInterest: Yes + GraphicsCard: + Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) +Subsystem: Dell Broadwell-U Integrated Graphics [1028:0643] +Subsystem: Dell Topaz XT [Radeon R7 M260/M265] [1028:0643] + InstallationDate: Installed on 2016-07-29 (1 days ago) + InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) + MachineType: Dell Inc. Inspiron 5548 + Package: xorg 1:7.7+13ubuntu3 + PackageArchitecture: amd64 + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=24cb3fff-5c01-4674-9c59-58d7d776fd70 ro quiet splash nomodeset vt.handoff=7 + ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 + Renderer: Software + Tags: xenial ubuntu + Uname: Linux 4.4.0-31-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev sambashare scanner sudo tape users video + _MarkForUpload: True + dmi.bios.date: 10/12/2015 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A06 + dmi.board.name: 0YDTG3 + dmi.board.vendor: Dell Inc. + dmi.board.version: A02 + dmi.chassis.type: 8 + dmi.chassis.vendor: Dell Inc. + dmi.chassis.version: A06 + dmi.modalias: dmi:bvnDellInc.:bvrA06:bd10/12/2015:svnDellInc.:pnInspiron5548:pvrA06:rvnDellInc.:rn0YDTG3:rvrA02:cvnDellInc.:ct8:cvrA06: + dmi.product.name: Inspiron 5548 + dmi.product.version: A06 + dmi.sys.vendor: Dell Inc. + version.compiz: compiz N/A + version.ia32-libs: ia32-libs N/A + version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 + version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 + version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A + version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 + version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 + version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 + version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 + version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 + version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1608042/+attachment/4710538/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title:
[Bug 1608042] LightdmLog.gz
apport information ** Attachment added: "LightdmLog.gz" https://bugs.launchpad.net/bugs/1608042/+attachment/4710543/+files/LightdmLog.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1608042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608042] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1608042/+attachment/4710541/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1608042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608042] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1608042/+attachment/4710540/+files/DpkgLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1608042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608042] Re: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system
** Description changed: COMPUTER: Dell Inspiron 5548 laptop CPU: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz GRAPHICS: Intel-AMD hybrid: - CPU-integrated: Intel Corporation Broadwell-U Integrated Graphics (driver: i915) - GPU: Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260/M265] (driver: amdgpu) OPERATING SYSTEM: 64-bit GNU/Linux XUbuntu 16.04 "Xenial" KERNEL: 4.4.0-31-generic PROBLEM: system hangs / freezes very frequently. - I have Xscreensaver installed and noticed that when it's running an OpenGL animation (screensaver) and I move the touchpad pointer the screen freezes. I can still turn the keyboard LED backlight on and off (hence: keyboard doesn't stop working) but the pointer won't move (touchpad is locked) and I can't Alt-F1 (switch terminals). Only solution is to power off my laptop (press and hold the power button). + I have Xscreensaver installed and noticed that when it's running an OpenGL animation (screensaver) and I move the touchpad pointer the screen freezes. I can still turn the keyboard LED backlight on and off (hence: keyboard doesn't stop working) but the pointer won't move (touchpad is locked) and I can't Ctrl-Alt-F[1-6] (switch TTY/terminals). Only solution is to power off my laptop (press and hold the power button). I usually select the "Molecule" screensaver (it uses OpenGL), then I click the "preview" button and wait for about 20 seconds, then I click the touchpad and the computer hangs. When I used XUbuntu 14.04 "Trusty" with AMD's fglrx (proprietary) driver I didn't experience such issue. After upgrading to 16.04 "Xenial" (which doesn't support fglrx module/driver) amdgpu module is loaded by default but very frequently hangs the entire system. Sometimes I'm quick enough to go to TTYS1 and then I get to see some messages such as "HARD LOCKUP on CPU0" and "HARD LOCKUP on CPU1". However, it's not a hardware problem because I've already executed the Dell Hardware Diagnostics straight from the boot (it's an EFI utility), it tested all the hardware components (CPU, GPU, RAM, keyboard, touchpad, hard disk etc.) and didn't detect any faulty component. The attached file "amdgpu-bug.txt" is the reason why I'm pretty convinced that the problem is being caused by the amdgpu driver. WORKAROUND: Boot from GRUB with the nomodeset parameter. The graphics performance becomes terribly slow. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1608042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608042] Re: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system
Attached file shows what is shown on my screen before the computer freezes permanently. ** Attachment added: "syslog.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1608042/+attachment/4710272/+files/syslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1608042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608042] Re: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system
apport information ** Tags added: apport-collected ** Description changed: COMPUTER: Dell Inspiron 5548 laptop CPU: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz GRAPHICS: Intel-AMD hybrid: - CPU-integrated: Intel Corporation Broadwell-U Integrated Graphics (driver: i915) - GPU: Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260/M265] (driver: amdgpu) OPERATING SYSTEM: 64-bit GNU/Linux XUbuntu 16.04 "Xenial" KERNEL: 4.4.0-31-generic PROBLEM: system hangs / freezes very frequently. I have Xscreensaver installed and noticed that when it's running an OpenGL animation (screensaver) and I move the touchpad pointer the screen freezes. I can still turn the keyboard LED backlight on and off (hence: keyboard doesn't stop working) but the pointer won't move (touchpad is locked) and I can't Alt-F1 (switch terminals). Only solution is to power off my laptop (press and hold the power button). I usually select the "Molecule" screensaver (it uses OpenGL), then I click the "preview" button and wait for about 20 seconds, then I click the touchpad and the computer hangs. When I used XUbuntu 14.04 "Trusty" with AMD's fglrx (proprietary) driver I didn't experience such issue. After upgrading to 16.04 "Xenial" (which doesn't support fglrx module/driver) amdgpu module is loaded by default but very frequently hangs the entire system. Sometimes I'm quick enough to go to TTYS1 and then I get to see some messages such as "HARD LOCKUP on CPU0" and "HARD LOCKUP on CPU1". However, it's not a hardware problem because I've already executed the Dell Hardware Diagnostics straight from the boot (it's an EFI utility), it tested all the hardware components (CPU, GPU, RAM, keyboard, touchpad, hard disk etc.) and didn't detect any faulty component. => If I boot from GRUB with the "nomodeset" parameter the problem disappears completely, although graphics performance becomes terribly slow. But I can then preview the "Molecule" screensaver as many times as I want and nothing locks / hangs / freezes. The attached file "amdgpu-bug.txt" is the reason why I'm pretty convinced that the problem is being caused by the amdgpu driver. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-video-amdgpu 1.1.0-1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Jul 30 07:01:32 2016 InstallationDate: Installed on 2016-07-29 (1 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron:  LANGUAGE=pt_BR:pt:en  TERM=xterm  PATH=(custom, no user)  LANG=pt_BR.UTF-8  SHELL=/bin/bash SourcePackage: xserver-xorg-video-amdgpu UpgradeStatus: No upgrade log present (probably fresh install) + --- + ApportVersion: 2.20.1-0ubuntu2.1 + Architecture: amd64 + CurrentDesktop: XFCE + DistroRelease: Ubuntu 16.04 + InstallationDate: Installed on 2016-07-29 (1 days ago) + InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) + Package: xserver-xorg-video-amdgpu 1.1.0-1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 + Tags: xenial + Uname: Linux 4.4.0-31-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev sambashare scanner sudo tape users video + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1608042/+attachment/4710199/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1608042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608042] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1608042/+attachment/4710200/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1608042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608042] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1608042/+attachment/4710201/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1608042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608042] [NEW] 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system
Public bug reported: COMPUTER: Dell Inspiron 5548 laptop CPU: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz GRAPHICS: Intel-AMD hybrid: - CPU-integrated: Intel Corporation Broadwell-U Integrated Graphics (driver: i915) - GPU: Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260/M265] (driver: amdgpu) OPERATING SYSTEM: 64-bit GNU/Linux XUbuntu 16.04 "Xenial" KERNEL: 4.4.0-31-generic PROBLEM: system hangs / freezes very frequently. I have Xscreensaver installed and noticed that when it's running an OpenGL animation (screensaver) and I move the touchpad pointer the screen freezes. I can still turn the keyboard LED backlight on and off (hence: keyboard doesn't stop working) but the pointer won't move (touchpad is locked) and I can't Alt-F1 (switch terminals). Only solution is to power off my laptop (press and hold the power button). I usually select the "Molecule" screensaver (it uses OpenGL), then I click the "preview" button and wait for about 20 seconds, then I click the touchpad and the computer hangs. When I used XUbuntu 14.04 "Trusty" with AMD's fglrx (proprietary) driver I didn't experience such issue. After upgrading to 16.04 "Xenial" (which doesn't support fglrx module/driver) amdgpu module is loaded by default but very frequently hangs the entire system. Sometimes I'm quick enough to go to TTYS1 and then I get to see some messages such as "HARD LOCKUP on CPU0" and "HARD LOCKUP on CPU1". However, it's not a hardware problem because I've already executed the Dell Hardware Diagnostics straight from the boot (it's an EFI utility), it tested all the hardware components (CPU, GPU, RAM, keyboard, touchpad, hard disk etc.) and didn't detect any faulty component. => If I boot from GRUB with the "nomodeset" parameter the problem disappears completely, although graphics performance becomes terribly slow. But I can then preview the "Molecule" screensaver as many times as I want and nothing locks / hangs / freezes. The attached file "amdgpu-bug.txt" is the reason why I'm pretty convinced that the problem is being caused by the amdgpu driver. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-video-amdgpu 1.1.0-1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Jul 30 07:01:32 2016 InstallationDate: Installed on 2016-07-29 (1 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron:  LANGUAGE=pt_BR:pt:en  TERM=xterm  PATH=(custom, no user)  LANG=pt_BR.UTF-8  SHELL=/bin/bash SourcePackage: xserver-xorg-video-amdgpu UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xserver-xorg-video-amdgpu (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 amdgpu apport-bug xenial ** Attachment added: "kernel log with several error messages from amdgpu module a little before every freeze/hang/lockup" https://bugs.launchpad.net/bugs/1608042/+attachment/4710195/+files/amdgpu-bug.txt ** Description changed: COMPUTER: Dell Inspiron 5548 laptop CPU: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz GRAPHICS: Intel-AMD hybrid: - - CPU-integrated: Intel Corporation Broadwell-U Integrated Graphics (module: i915) - - GPU: Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260/M265] (module: amdgpu) + - CPU-integrated: Intel Corporation Broadwell-U Integrated Graphics (driver: i915) + - GPU: Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260/M265] (driver: amdgpu) OPERATING SYSTEM: 64-bit GNU/Linux XUbuntu 16.04 "Xenial" KERNEL: 4.4.0-31-generic PROBLEM: system hangs / freezes very frequently. I have Xscreensaver installed and noticed that when it's running an OpenGL animation (screensaver) and I move the touchpad pointer the screen freezes. I can still turn the keyboard LED backlight on and off (hence: keyboard doesn't stop working) but the pointer won't move (touchpad is locked) and I can't Alt-F1 (switch terminals). Only solution is to power off my laptop (press and hold the power button). I usually select the "Molecule" screensaver (it uses OpenGL), then I click the "preview" button and wait for about 20 seconds, then I click the touchpad and the computer hangs. When I used XUbuntu 14.04 "Trusty" with AMD's fglrx (proprietary) driver I didn't experience such issue. After upgrading to 16.04 "Xenial" (which doesn't support fglrx module/driver) amdgpu module is loaded by default but very frequently hangs the entire system. Sometimes I'm quick enough to go to TTYS1 and then I get to see some messages such as "HARD LOCKUP on CPU0" and "HARD LOCKUP on CPU1". However, it's not a hardware problem because I've already executed the Dell Hardware Diagnostics straight from the boot (it's an EFI utility), it tested all the hardware components (CPU, GPU, RAM, keyboard, touchpad, hard disk etc.) and didn't detect any faul
[Bug 1608042] Re: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system
Kernel log with several error messages related to the unstable behavior of the amdgpu driver. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1608042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1488719] Re: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!"
"I think the flickering problem only occurs if you use two external monitors with e-port-dock." In my case, my laptop suddenly powers off. But another bug that happens in it is this: after a while with Xscreensaver running, the screen flickers and remains that way for some 3 extra seconds after I type my password and the screen is unlocked. Weird thing is that after the screen is unlocked, some 3 seconds later the flickering stops. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1488719 Title: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!" To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1488719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1488719]
Please see this bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520040 This bug makes my Dell Latitude laptop shutdown (power off). In that bug report I provided a lot of information about my system, logs and tests I did. Currently, only kernel "3.13.0-36-generic" running module "/lib/modules/3.13.0-36-generic/kernel/ubuntu/i915/i915_bdw.ko" doesn't have this bug. Hence, this bug is far from "solved" and shutting up dmesg definitely won't solve it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1488719 Title: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!" To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1488719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1488719] Re: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!"
This is a mysterious bug affecting a LOT of machines. As I suggested at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520040, as a temporary workaround I recommend downgrading to kernel "3.13.0-36-generic". Try it out and see if it is of any help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1488719 Title: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!" To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1488719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520040] Re: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!
By the way: "dmesg |grep -i error" and "dmesg |grep -i lied" are two other shell commands I run, too. Where I mentioned above that I didn't find the bug I mean that besides running "dmesg |grep -i i915" I also ran the two previously mentioned commands and got no results (meaning that no "error" string neither "lied" string was found). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520040 Title: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520040] Re: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!
Hello. Happy New Year everyone. :) I have a doubt: I started testing these kernels and one of'em has the following message in dmesg (shell command was 'dmesg | grep -i i915'): [ 11.547334] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) I understand that this isn't a bug (it seems that snd_hda_intel was bound to the audio component of i915 and that's it), but since I'm not 100% sure about what this message actually means it doesn't hurt to ask. Any consideration to be taken into account here? Anyway, so far I've tested the following kernels and got the following outputs from 'dmesg |grep -i i915': 1) v4.1.6-unstable: [1.195451] [drm] Initialized i915 1.6.0 20150327 for :00:02.0 on minor 0 [2.311613] i915 :00:02.0: fb0: inteldrmfb frame buffer device [2.311614] i915 :00:02.0: registered panic notifier [8.605191] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Because I am assuming that "snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915])" isn't a bug, I considered that the bug reported in this ticket is fixed in kernel version "v4.1.6-unstable", hence I decided to test a previous (older) kernel version: v4.0.6-wily. 2) v4.0.6-wily: [1.243539] [drm] Initialized i915 1.6.0 20150130 for :00:02.0 on minor 0 [2.316114] i915 :00:02.0: fb0: inteldrmfb frame buffer device [2.316115] i915 :00:02.0: registered panic notifier [7.558016] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 34.302400] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun I considered that FIFO underrun a bug, hence I then decided to test a newer kernel version: v4.1-rc7-unstable. 3) v4.1-rc7-unstable: [1.194191] [drm] Initialized i915 1.6.0 20150327 for :00:02.0 on minor 0 [2.324857] i915 :00:02.0: fb0: inteldrmfb frame buffer device [2.324858] i915 :00:02.0: registered panic notifier [5.989937] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 26.618897] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun Same FIFO underrun issue, thus I then tested a newer kernel version: v4.1.2-unstable. 4) v4.1.2-unstable: [1.188288] [drm] Initialized i915 1.6.0 20150327 for :00:02.0 on minor 0 [2.296468] i915 :00:02.0: fb0: inteldrmfb frame buffer device [2.296469] i915 :00:02.0: registered panic notifier [7.502745] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Assuming that "snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915])" isn't a bug, I considered the bug fixed in kernel version v4.1.2-unstable, and thus decided to test a previous (older) kernel version: v4.1-wily. 5) v4.1-wily: [1.176185] [drm] Initialized i915 1.6.0 20150327 for :00:02.0 on minor 0 [2.292596] i915 :00:02.0: fb0: inteldrmfb frame buffer device [2.292597] i915 :00:02.0: registered panic notifier [ 11.547334] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Again, since I'm assuming that "snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915])" isn't a bug, I'm considering that the vug is fixed in kernel version v4.1-wily. Is it ok so far? If it is, I am very close to finding out in which kernel version the bug fix was commited. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520040 Title: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520040] Re: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!
Wow, that seems a lot of work. I've never did it before in my life, but ok, let's see if I can do it. I'll need some help here, though, 'coz I'm not 100% sure if the kernel list I created is correct. Could you please confirm this to me? If I understood the instructions correctly, according with "ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7" and "http://people.canonical.com/~kernel/info/kernel-version-map.html"; the mainline kernel version for "3.19.0-33-generic" (which shipped with my notebook) is kernel "3.19.8-ckt7", hence the botton of the kernel list must be "v3.19.8-ckt7-vivid". Also, because the bug was fixed in upstream kernel "v4.4-rc2+cod1-wily", it has to be on the top of the list, thus I am assuming that the kernel list for reverse commit bisect has to be this one: v4.4-rc2+cod1-wily v4.4-rc1-wily v4.4-rc1+cod1-wily v4.3-wily v4.3-unstable v4.3-rc7-unstable v4.3-rc6-unstable v4.3-rc5-unstable v4.3-rc4-unstable v4.3-rc3-unstable v4.3-rc2-unstable v4.3-rc1-unstable v4.2.6-wily v4.2.5-wily v4.2.4-wily v4.2.4-unstable v4.2.3-unstable v4.2.2-unstable v4.2.1-unstable v4.2-wily v4.2-unstable v4.2-rc8-unstable v4.2-rc7-unstable v4.2-rc6-unstable v4.2-rc5-unstable v4.2-rc4-unstable v4.2-rc3-unstable v4.2-rc2-unstable v4.2-rc1-unstable v4.1.13-wily v4.1.12-wily v4.1.11-wily v4.1.11-unstable v4.1.10-unstable v4.1.9-unstable v4.1.8-unstable v4.1.7-unstable v4.1.6-unstable v4.1.5-unstable v4.1.4-unstable v4.1.3-unstable v4.1.2-unstable v4.1.1-unstable v4.1-wily v4.1-unstable v4.1-rc8-unstable v4.1-rc7-unstable v4.1-rc6-unstable v4.1-rc5-unstable v4.1-rc4-unstable v4.1-rc3-unstable v4.1-rc2-vivid v4.1-rc1-vivid v4.0.9-wily v4.0.8-wily v4.0.7-wily v4.0.6-wily v4.0.5-wily v4.0.4-wily v4.0.3-wily v4.0.2-wily v4.0.1-wily v4.0-vivid v4.0-rc7-vivid v4.0-rc6-vivid v4.0-rc5-vivid v4.0-rc4-vivid v4.0-rc3-vivid v4.0-rc2-vivid v4.0-rc1-vivid v3.19.8-vivid v3.19.8-ckt10-vivid v3.19.8-ckt9-vivid v3.19.8-ckt8-vivid v3.19.8-ckt7-vivid Is my line of thought correct? Hence, is the above list correct? As soon as I have a confirmation, I'll begin tracking down the commit that fixed the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520040 Title: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520040] Re: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!
Well, it's been ~24 hours since I started using kernel"4.4-rc2+cod1". My notebook was kept "on" for over 16 of these 24 hours: 8h yesterday + 8h today. So far, no subtle poweroff happened. I restarted the system a couple of times, today and yesterday, and I also powered off the notebook. No issues detected. Here's the current output for 'dmesg |grep -i i915' (the notebook's been on for the last 8 hours): [1.246344] [drm] Initialized i915 1.6.0 20151010 for :00:02.0 on minor 0 [2.431514] i915 :00:02.0: fb0: inteldrmfb frame buffer device [9.782202] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520040 Title: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520040] Re: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!
Okay, I've just (~21:13 UTC) installed kernel "4.4-rc2+cod1". Packages installed: linux-image-4.4.0-040400rc2-generic_4.4.0-040400rc2.201511231054_amd64.deb linux-headers-4.4.0-040400rc2_4.4.0-040400rc2.201511231054_all.deb linux-headers-4.4.0-040400rc2-generic_4.4.0-040400rc2.201511231054_amd64.deb "uname -a": Linux yurix 4.4.0-040400rc2-generic #201511231054 SMP Mon Nov 23 10:56:43 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux "dmesg |grep -i i915": [1.240521] [drm] Initialized i915 1.6.0 20151010 for :00:02.0 on minor 0 [2.461518] i915 :00:02.0: fb0: inteldrmfb frame buffer device [ 13.662232] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) "dmesg |grep -i amd": [0.00] AMD AuthenticAMD [0.00] RAMDISK: [mem 0x3448c000-0x3623dfff] [1.211790] [drm] amdgpu kernel modesetting enabled. [1.214823] AMD IOMMUv2 driver by Joerg Roedel [1.214825] AMD IOMMUv2 functionality not available on this system Last lines of "cat /var/log/kern.log |grep -i lied": Nov 29 11:30:15 yurix kernel: [ 23.887712] [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! Nov 29 11:30:15 yurix kernel: [ 23.887880] [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! Nov 29 11:30:15 yurix kernel: [ 23.888368] [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! Nov 29 11:30:15 yurix kernel: [ 23.888536] [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! (so far no IRQ-related issues after I booted the system with an upstream kernel) "lsmod |grep -i i915": i915 --- 1204224 --- 5 i2c_algo_bit --- 16384 --- 2 --- i915,amdgpu drm_kms_helper --- 135168 --- 2 --- i915,amdgpu drm --- 360448 --- 8 --- ttm,i915,drm_kms_helper,amdgpu video --- 40960 --- 3 --- i915,dell_wmi,dell_laptop "aticonfig --list-adapters": * 0. 04:00.0 AMD Radeon R7 M260 * - Default adapter "amdcccle" (AMD Catalyst Control Center): opens a window with an error message in brazilian portuguese. In english, the message translates to "There was a problem while attempting to start Catalyst Control Center Linux Edition. It may have been caused by the following: No AMD graphics driver installed, or AMD graphics driver not working properly. Install the proper AMD driver to your AMD hardware, or configure it with 'aticonfig'." Well, this pretty much confirms to me that "fglrx_updates" is definitely a proprietary AMD GPU driver and thus doesn't work with these kernels, as explained in https://wiki.ubuntu.com/Kernel/MainlineBuilds I will keep this kernel running for the next hours and report back if any message like "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!" comes up in "dmesg". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520040 Title: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520040] Re: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!
I'm not 100% sure if "Confirmed" refers to the latest / upstream kernel I'm testing (4.3.0-997-generic) or to the one in which I detected the bug in (kernel 3.19.0-33-generic). But I'm assuming that it refers to '4.3.0-997-generic', thus I marked this bug as "Confirmed" (although it seems to be fixed in the last upstream kernel). I just would like to test this upstream kernel it with both 'fglrx_updates' and 'i915'/'i915_bpo' simultaneously loaded. I'm under the impression that maybe there's an IRQ conflict between the default GPU (handled by Broadwell module i915*) and the AMD GPU (handled by AMD module fglrx_updates). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520040 Title: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520040] Re: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520040 Title: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520040] Re: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!
HI. Today I accessed http://kernel.ubuntu.com/~kernel- ppa/mainline/?C=N;O=D but the very top line at the top of the page was a link to http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-rc2-wily/, which doesn't have kernel DEB packages (except for linux- headers-4.4.0-040400rc2_4.4.0-040400rc2.201511251301_all.deb, but this is only the kernel headers, I couldn't find any kernel image). Thus I proceeded to http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel- next/ where the most recent folder with available DEB packages currently is http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel- next/2015-11-21-wily/ >From http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel- next/2015-11-21-wily/ I downloaded and installed the following packages: linux-image-4.3.0-997-generic_4.3.0-997.201511202100_amd64.deb linux-headers-4.3.0-997_4.3.0-997.201511202100_all.deb linux-headers-4.3.0-997-generic_4.3.0-997.201511202100_amd64.deb I was able to boot this kernel. Here's the result of some commands: 'uname -a': Linux yurix 4.3.0-997-generic #201511202100 SMP Sat Nov 21 02:02:46 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux 'dmesg |grep -i i915': [1.175639] [drm] Initialized i915 1.6.0 20151120 for :00:02.0 on minor 0 [2.343450] i915 :00:02.0: fb0: inteldrmfb frame buffer device [ 13.974419] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) (most recent event in dmesg was rcreated @ [ 1282.427420]) 'dmesg |grep -i amd': [0.00] AMD AuthenticAMD [0.00] RAMDISK: [mem 0x34978000-0x364b3fff] [1.143551] [drm] amdgpu kernel modesetting enabled. [1.146516] AMD IOMMUv2 driver by Joerg Roedel [1.146519] AMD IOMMUv2 functionality not available on this system [1.151854] amdgpu :04:00.0: enabling device (0100 -> 0103) [1.224583] amdgpu :04:00.0: Direct firmware load for amdgpu/topaz_mc.bin failed with error -2 [1.224584] mc: Failed to load firmware "amdgpu/topaz_mc.bin" [1.224604] [drm:gmc_v8_0_sw_init [amdgpu]] *ERROR* Failed to load mc firmware! [1.224606] amdgpu :04:00.0: Fatal error during GPU init [1.224607] [drm] amdgpu: finishing device. [1.224944] amdgpu: probe of :04:00.0 failed with error -2 I noticed that 'fglrx_updates.ko' (which seems to be the AMD GPU driver) probably is a proprietary driver and thus wasn't loaded by the kernel (I noticed some dkms error messages related to it, during kernel installation, probably because of restrictions at the driver's dkms.conf file), which caused kernel '4.3.0-997-generic' to try to load /lib/modules/4.3.0-997-generic/kernel/drivers/gpu/drm/amd/amdgpu/amdgpu.ko. Because 'amdgpu.ko' wasn't loaded either, I was unable to run the 'AMD Catalyst Control Center' (shell command: amdcccle). But the kernel did detect the AMD GPU: 'aticonfig --list-adapters': * 0. 04:00.0 AMD Radeon R7 M260 * - Default adapter (managed by /lib/modules/4.3.0-997-generic/kernel/drivers/gpu/drm/i915/i915.ko) 'lspci |grep -i amd': 04:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260] 'i915.ko' was loaded and 'amdgpu.ko' depends on it. Here's the output for 'lsmod |grep -i i915': i915 --- 1204224 --- 5 i2c_algo_bit --- 16384 --- 2 --- i915,amdgpu drm_kms_helper --- 135168 --- 2 --- i915,amdgpu drm --- 356352 --- 8 --- ttm,i915,drm_kms_helper,amdgpu video --- 36864 --- 3 --- i915,dell_wmi,dell_laptop So, in a nutshell: looks like the kernel '4.3.0-997-generic' is doing ok with its module 'i915.ko'. I will keep testing it for a while just to make sure, but so far 'dmesg' hasn't shown me any message like '[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!' for kernel '4.3.0-997-generic'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520040 Title: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520040] Re: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!
Thank you. I've just run the apport-collect app as instructed. Note: until Nov 27 02:32:01 AM UTC-2 (my local time, equivalent to 04:32:01 AM UTC) I was running kernel 3.19.0-33-generic as my default O.S. kernel, but then my notebook subtly powered off once more, thus causing me to decide to boot with kernel 3.13.0-36-generic by default. However, before running 'apport-collect 1520040' I booted the machine with kernel 3.19.0-33-generic again. Please let me know if it's interesting that I keep my system running only kernel 3.19.0-33-generic for a while, in order to further generate useful logs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520040 Title: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520040] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1520040/+attachment/4526411/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520040 Title: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520040] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1520040/+attachment/4526408/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520040 Title: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520040] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1520040/+attachment/4526410/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520040 Title: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520040] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1520040/+attachment/4526407/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520040 Title: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520040] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1520040/+attachment/4526406/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520040 Title: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520040] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1520040/+attachment/4526409/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520040 Title: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520040] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1520040/+attachment/4526412/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520040 Title: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520040] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1520040/+attachment/4526399/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520040 Title: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520040] Re: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!
apport information ** Tags added: apport-collected ** Description changed: Device: notebook Dell Inspiron 5548 Operating system: 64-bit XUbuntu Linux 14.04 LTS Processor: Intel Core i7-5500U Kernel: 3.19.0-33-generic #38~14.04.1-Ubuntu SMP x86_64 Video: dual chip. These are the two display controllers: - Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260] display controller 3300Hz (requires kernel module / device driver "fglrx"); and - Intel Corporation Broadwell-U Integrated Graphics VGA compatible controller 3300Hz (requires kernel module / device driver "i915"). Problem: my notebook's operating system is switching to runlevel 0 (power off) randomly, subtly and thus unexpectedly. And if I 'cat /var/log/kern.log |grep -i i915' I get a lot of "[drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!" messages. I'm under the impression that either the kernel or the kernel module "i915_bpo" is buggy. My notebook's problem can't be related to overheating, because it's a brand-new notebook (less than 1 month old) and I've already monitored its temperature parameters: nothing abnormal is happening. Also, I'm using a cooling laptop base/pad. Other kernels I've tested, with which the same issue happens: - 3.19.0-18-generic (kernel module: i915_bpo) - 3.19.0-23-generic (kernel module: i915_bpo) - 3.19.0-28-generic (kernel module: i915_bpo) - 4.2.0-18-generic (kernel module: i915) Temporary workaround: I downgraded to kernel "3.13.0-36-generic", which isn't buggy with its "i915_bdw.ko" (version 3.0) kernel object (module). Full path for this module: /lib/modules/3.13.0-36-generic/kernel/ubuntu/i915/i915_bdw.ko Notes: - "bdw" stands for "Broadwell" - "bpo", I believe, stands for "backport" ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-33-generic 3.19.0-33.38~14.04.1 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 NonfreeKernelModules: wl fglrx ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Nov 25 23:44:39 2015 InstallationDate: Installed on 2015-11-03 (22 days ago) InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: linux-lts-vivid UpgradeStatus: No upgrade log present (probably fresh install) + --- + ApportVersion: 2.14.1-0ubuntu3.19 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: yuriyrs2832 F pulseaudio + /dev/snd/controlC1: yuriyrs2832 F pulseaudio + CurrentDesktop: XFCE + DistroRelease: Ubuntu 14.04 + HibernationDevice: RESUME=UUID=a08f36f9-0611-4894-9da9-8b1dcc960a86 + InstallationDate: Installed on 2015-11-03 (24 days ago) + InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) + MachineType: Dell Inc. Inspiron 5548 + NonfreeKernelModules: fglrx wl + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-33-generic.efi.signed root=UUID=4f05c2b3-c971-4bf8-bcb6-a76d60b68e45 ro quiet splash video.use_native_backlight=1 intremap=no_x2apic_optout vt.handoff=7 + ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 + RelatedPackageVersions: + linux-restricted-modules-3.19.0-33-generic N/A + linux-backports-modules-3.19.0-33-generic N/A + linux-firmware 1.127.18 + Tags: trusty + Uname: Linux 3.19.0-33-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare scanner sudo tape video + _MarkForUpload: True + dmi.bios.date: 10/12/2015 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A06 + dmi.board.name: 0YDTG3 + dmi.board.vendor: Dell Inc. + dmi.board.version: A02 + dmi.chassis.type: 8 + dmi.chassis.vendor: Dell Inc. + dmi.chassis.version: A06 + dmi.modalias: dmi:bvnDellInc.:bvrA06:bd10/12/2015:svnDellInc.:pnInspiron5548:pvrA06:rvnDellInc.:rn0YDTG3:rvrA02:cvnDellInc.:ct8:cvrA06: + dmi.product.name: Inspiron 5548 + dmi.product.version: A06 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1520040/+attachment/4526397/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520040 Title: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520040] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1520040/+attachment/4526403/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520040 Title: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520040] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1520040/+attachment/4526404/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520040 Title: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520040] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1520040/+attachment/4526405/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520040 Title: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520040] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1520040/+attachment/4526400/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520040 Title: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520040] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1520040/+attachment/4526398/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520040 Title: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520040] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1520040/+attachment/4526402/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520040 Title: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520040] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1520040/+attachment/4526401/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520040 Title: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520040] Re: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!
** Description changed: Device: notebook Dell Inspiron 5548 Operating system: 64-bit XUbuntu Linux 14.04 LTS Processor: Intel Core i7-5500U Kernel: 3.19.0-33-generic #38~14.04.1-Ubuntu SMP x86_64 Video: dual chip. These are the two display controllers: - Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260] display controller 3300Hz (requires kernel module / device driver "fglrx"); and - Intel Corporation Broadwell-U Integrated Graphics VGA compatible controller 3300Hz (requires kernel module / device driver "i915"). Problem: my notebook's operating system is switching to runlevel 0 (power off) randomly, subtly and thus unexpectedly. And if I 'cat /var/log/kern.log |grep -i i915' I get a lot of "[drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!" messages. I'm under the impression that either the kernel or the kernel module "i915_bpo" is buggy. My notebook's problem can't be related to overheating, because it's a - brand-new notebook (~1 week old) and I've already monitored its - temperature parameters: nothing abnormal is happening. Also, I'm using a - cooling laptop base/pad. + brand-new notebook (less than 1 month old) and I've already monitored + its temperature parameters: nothing abnormal is happening. Also, I'm + using a cooling laptop base/pad. Other kernels I've tested, with which the same issue happens: - 3.19.0-18-generic (kernel module: i915_bpo) - 3.19.0-23-generic (kernel module: i915_bpo) - 3.19.0-28-generic (kernel module: i915_bpo) - 4.2.0-18-generic (kernel module: i915) Temporary workaround: I downgraded to kernel "3.13.0-36-generic", which isn't buggy with its "i915_bdw.ko" (version 3.0) kernel object (module). Full path for this module: /lib/modules/3.13.0-36-generic/kernel/ubuntu/i915/i915_bdw.ko - Notes: - "bdw" stands for "Broadwell" - "bpo", I believe, stands for "backport" ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-33-generic 3.19.0-33.38~14.04.1 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 NonfreeKernelModules: wl fglrx ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Nov 25 23:44:39 2015 InstallationDate: Installed on 2015-11-03 (22 days ago) InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: linux-lts-vivid UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520040 Title: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1520040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520040] Re: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!
Other filed bugs reporting the same issue in other kernels: 1) Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 x86_64 + "i915" kernel module: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488719 2) Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6 x86_64 + "i915_bpo" kernel module: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1503541 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520040 Title: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1520040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520040] Re: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!
Recent 'dmesg' showing more detailed system info plus the error messages. ** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1520040/+attachment/4525562/+files/dmesg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520040 Title: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1520040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520040] [NEW] [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!
Public bug reported: Device: notebook Dell Inspiron 5548 Operating system: 64-bit XUbuntu Linux 14.04 LTS Processor: Intel Core i7-5500U Kernel: 3.19.0-33-generic #38~14.04.1-Ubuntu SMP x86_64 Video: dual chip. These are the two display controllers: - Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260] display controller 3300Hz (requires kernel module / device driver "fglrx"); and - Intel Corporation Broadwell-U Integrated Graphics VGA compatible controller 3300Hz (requires kernel module / device driver "i915"). Problem: my notebook's operating system is switching to runlevel 0 (power off) randomly, subtly and thus unexpectedly. And if I 'cat /var/log/kern.log |grep -i i915' I get a lot of "[drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!" messages. I'm under the impression that either the kernel or the kernel module "i915_bpo" is buggy. My notebook's problem can't be related to overheating, because it's a brand-new notebook (~1 week old) and I've already monitored its temperature parameters: nothing abnormal is happening. Also, I'm using a cooling laptop base/pad. Other kernels I've tested, with which the same issue happens: - 3.19.0-18-generic (kernel module: i915_bpo) - 3.19.0-23-generic (kernel module: i915_bpo) - 3.19.0-28-generic (kernel module: i915_bpo) - 4.2.0-18-generic (kernel module: i915) Temporary workaround: I downgraded to kernel "3.13.0-36-generic", which isn't buggy with its "i915_bdw.ko" (version 3.0) kernel object (module). Full path for this module: /lib/modules/3.13.0-36-generic/kernel/ubuntu/i915/i915_bdw.ko Notes: - "bdw" stands for "Broadwell" - "bpo", I believe, stands for "backport" ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-33-generic 3.19.0-33.38~14.04.1 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 NonfreeKernelModules: wl fglrx ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Nov 25 23:44:39 2015 InstallationDate: Installed on 2015-11-03 (22 days ago) InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: linux-lts-vivid UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-lts-vivid (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug broadwell i915 trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520040 Title: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1520040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
RE: [Bug 1503541] Re: kern.log flooded with "[drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!"
Hi, Christopher, thank you for your reply. I'm currently running kernel "3.13.0-36-generic", which doesn't have any issue with module "i915_bdw.ko". I know I'll have to upgrade the kernel in order to make the issue come up again. My doubt is: which kernel shall I upgrade my system to? Shall I upgrade to kernel "3.19.0-33-generic" (module "i915_bpo.ko")? Or kernel "4.2.0-18-generic" (module "i915.ko")? Or shall I switch kernels and file a bug for each one of'em? I can do both (file a bug for 3.19.0-33-generic and another for 4.2.0-18-generic), it's not a problem. I'm just not sure if it's necessary. Please let me know which option is the best and I'll do it. []'s Yuri > Date: Tue, 24 Nov 2015 20:06:04 + > From: christopher.m.penal...@gmail.com > To: yuri_sucup...@hotmail.com > Subject: [Bug 1503541] Re: kern.log flooded with "[drm:gen8_irq_handler > [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!" > > Yuri Ribeiro Sucupira, it will help immensely if you filed a new report via a > terminal: > ubuntu-bug linux > > Please feel free to subscribe me to it. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1503541 > > Title: > kern.log flooded with "[drm:gen8_irq_handler [i915_bpo]] *ERROR* The > master control interrupt lied (SDE)!" > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > On an intel i5 toshiba laptop on vivid. Upgraded to the > 3.19.0-30-generic kernel and started seeing this. Additionally, bootup > was slow. > > kern.log/dmesg is flooded with this output > > [ 69.070503] [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master > control interrupt lied (SDE)! > > ProblemType: Bug > DistroRelease: Ubuntu 15.04 > Package: linux-image-3.19.0-30-generic 3.19.0-30.34 > ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6 > Uname: Linux 3.19.0-30-generic x86_64 > ApportVersion: 2.17.2-0ubuntu1.5 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: wolsen 2493 F pulseaudio >/dev/snd/controlC1: wolsen 2493 F pulseaudio > CurrentDesktop: Unity > Date: Tue Oct 6 22:30:20 2015 > HibernationDevice: RESUME=UUID=096b9e95-621b-4cc7-a10c-250149e1b48b > InstallationDate: Installed on 2015-07-15 (83 days ago) > InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) > MachineType: TOSHIBA Satellite E45-B > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-30-generic.efi.signed > root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash > RelatedPackageVersions: >linux-restricted-modules-3.19.0-30-generic N/A >linux-backports-modules-3.19.0-30-generic N/A >linux-firmware 1.143.3 > SourcePackage: linux > UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 01/12/2015 > dmi.bios.vendor: INSYDE Corp. > dmi.bios.version: 1.10 > dmi.board.asset.tag: Type2 - Board Asset Tag > dmi.board.name: CA10CU > dmi.board.vendor: TOSHIBA > dmi.board.version: 2.0 > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: OEM Chassis ManuFacturer > dmi.chassis.version: OEM Chassis Version > dmi.modalias: > dmi:bvnINSYDECorp.:bvr1.10:bd01/12/2015:svnTOSHIBA:pnSatelliteE45-B:pvrPSPNAU-001002:rvnTOSHIBA:rnCA10CU:rvr2.0:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: > dmi.product.name: Satellite E45-B > dmi.product.version: PSPNAU-001002 > dmi.sys.vendor: TOSHIBA > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1503541/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1503541 Title: kern.log flooded with "[drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1503541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1488719] Re: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!"
This bug also affects me. Well, now it doesn't anymore, because I've downgraded my system kernel. Device: notebook Dell Inspiron 5548 Operating system: 64-bit XUbuntu Linux 14.04 Processor: Intel Core i7-5500U Video: dual chip. These are the two display controllers: - Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260] display controller 3300Hz (requires kernel module / device driver "fglrx"); and - Intel Corporation Broadwell-U Integrated Graphics VGA compatible controller 3300Hz (requires kernel module / device driver "i915"). Problem: the message "[drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!" floods my dmesg, and from time to time my system crashes and my computer powers off. If I 'cat /var/log/kern.log |grep -i i915' i see a huge amount of messages exactly like this one, hence I can only assume that the kernel module i915_bpo is buggy (or these kernels are buggy while they interact with that kernel module). My notebook is subtly powering off from time to time (unrelated with overheat, I'm pretty sure 'coz I've already monitored temperature parameters and also 'coz I'm using a cooling laptop base/pad, besides the fact that my notebook is brand-new: only 1 week old). Kernels I've tested which have this issue: - 3.19.0-18-generic - 3.19.0-23-generic - 3.19.0-28-generic - 3.19.0-33-generic - 4.2.0-18-generic All of them have the same problem: the kernel module "i915.ko" (in 4.2.0-18-generic) and the kernel module "i915_bpo.ko" (in kernels 3.19.0-??-generic) randomly cause subtle system shutdown (halt / poweroff) in my notebook. Solution: I downgraded to kernel 3.13.0-36-generic, which isn't buggy with its "i915_bdw.ko" (version 3.0) kernel object (module). Full path for this module: /lib/modules/3.13.0-36-generic/kernel/ubuntu/i915/i915_bdw.ko Notes: - "bdw" stands for "Broadwell" - "bpo", I believe, stands for "backport" IMO, this bug is pretty serious and is taking a lot of time to get fixed: my notebook could get damaged if it kept subtly powering off several times a day, on an everyday basis, like it was doing because of this bug. Hence, my strong suggestion to those who are experiencing this issue is to downgrade to a stable kernel version (I recommend kernel 3.13.0-36-generic). If you don't want to downgrade your kernel: become root ('sudo su'), then open '/etc/default/grub' for edition (e.g. 'gedit /etc/default/grub'), then add the 'nomodeset' option to "GRUB_CMDLINE_LINUX_DEFAULT=" (e.g. GRUB_CMDLINE_LINUX_DEFAULT="nomodeset"), then save the file, exit the text editor and, still as root, run the command 'update-grub && telinit 6'. Your GRUB will be updated and your system will be restarted. After that you won't be able to see OpenGL graphics anymore (e.g. Xscreensaver openGL screensavers won't load), but your system will stop subtly powering off. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1488719 Title: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!" To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1488719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1503541] Re: kern.log flooded with "[drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!"
This bug also affects me. Well, now it doesn't anymore, because I've downgraded my system kernel. Device: notebook Dell Inspiron 5548 Operating system: 64-bit XUbuntu Linux 14.04 Processor: Intel Core i7-5500U Video: dual chip. These are the two display controllers: - Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260] display controller 3300Hz (requires kernel module / device driver "fglrx"); and - Intel Corporation Broadwell-U Integrated Graphics VGA compatible controller 3300Hz (requires kernel module / device driver "i915"). Problem: the message "[drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!" floods my dmesg. If I "cat /var/log/kern.log |grep -i i915" i see a huge amount of messages exactly like this one, hence I can only assume that the kernel module i915_bpo is buggy. Also, my notebook was subtly powering off from time to time (unrelated with overheat, I'm pretty sure 'coz I've already monitored temperature parameters and also 'coz I'm using a cooling laptop base/pad). Kernels I've tested which have this issue: - 3.19.0-18-generic - 3.19.0-23-generic - 3.19.0-28-generic - 3.19.0-33-generic - 4.2.0-18-generic All of them have the same problem: the kernel module "i915.ko" (in 4.2.0-18-generic) and the kernel module "i915_bpo.ko" (in kernels 3.19.0-??-generic) cause subtle system shutdown (halt / poweroff) in my notebook. Solution: I downgraded to kernel 3.13.0-36-generic, which isn't buggy with its "i915_bdw.ko" (version 3.0) kernel object (module). Full path for this module: /lib/modules/3.13.0-36-generic/kernel/ubuntu/i915/i915_bdw.ko Notes: - "bdw" stands for "Broadwell" - "bpo", I believe, stands for "backport" IMO, this bug is pretty serious and is taking a lot of time to get fixed: my notebook could get damaged if it kept subtly powering off on an everyday basis like it was doing because of this bug. Hence, my strong suggestion to those who are experiencing this issue is to downgrade to a stable kernel version (I recommend kernel 3.13.0-36-generic. If you don't want to downgrade your kernel: become root ('sudo su'), then open '/etc/default/grub' for edition (e.g.: 'gedit /etc/default/grub'), then add the 'nomodeset' option to "GRUB_CMDLINE_LINUX_DEFAULT=" (e.g.: GRUB_CMDLINE_LINUX_DEFAULT="nomodeset"), then save the file, exit the text editor and, still as root, run the command 'update-grub && telinit 6'. Your GRUB will be updated and your system will be restarted. After that you won't be able to see OpenGL graphics anymore (e.g. Xscreensaver openGL screensavers won't load), but your system will stop subtly powering off. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1503541 Title: kern.log flooded with "[drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1503541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310220] Re: System sound volume gets reduced when screen lock is activated
Old topic, old bug: I have the same issue. When the screen is locked, the volume changes to about 50%. I left my Dell notebook playing music (YouTube musical flash videos in a playlist), but when Light Locker automatically started the volume was reduced from 100% to 50%. uname -a: Linux yurix 3.19.0-32-generic #37~14.04.1-Ubuntu SMP Thu Oct 22 09:41:40 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Distro: 64-bit GNU/Linux XUbuntu 14.04 Device: notebook Dell Inspiron 5548 (0643), Intel CPU i7 5500U@2.4GHz & 16GB RAM @1600MHz Light Locker version: 1.4.0-0ubuntu1 Light Locker Settings version: 1.2.1-0ubuntu1.1 The command "lsmod |grep sound" tells me that the "soundcore" is in use and being used by kernel modules "snd" and "snd_hda_codec". My GPU is an AMD Radeon R7 M260 @ 2GB RAM/900MHz clock. The command "lsmod |grep fglrx" (fglrx is the proprietary device driver for AMD GPUs) tells me that the modules "fglrx" and "amd_iommu_v2" are being used by the OS. After I disabled Light Locker, the problem didn't happen anymore. Now I'm using only Xscreensaver. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310220 Title: System sound volume gets reduced when screen lock is activated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1310220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs