I did use kernel version 4. Both platforms are using the same kernel drivers mostly. There were no other messages on the screen, for a few more minutes that I could take this until I turned it off. Other than booting up takes a few minutes longer, it doesn't seem to affect anything else - or rather, the system is not noticeably poorer. Jun 05 18:41:36 djm kernel: hub 1-1:1.
It is Fedora's policy to close all bug reports from releases that are no longer maintained. I'm not a kernel hacker. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Then you need to install the kernel-debuginfo and crash package. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26. With Windows I get 6 hours if I use it mildly.
It's a bug and it may happen again. At first, it wasn't clear to me if this was happening just under Xorg, but it's happening in Wayland desktop sessions too. So I removed the nouveau driver completely from the kernel and rebuild it. I also have the same laptop: Dell Inspiron 7559. The dmesg 'es did show that the i915 driver couldn't load necessary firmware.
One thing I did afterwards and it could or could not be related to the lockup. The only way to shut the machine down is by long-pressing the power key. Try 'nomodeset' instead of your nouveau command. However once I managed to boot with Intel and it gave me 6:30 hours of battery life. The uevents are normal fast as well now too. Hopefully this can help you, I know it's a few days late but I just stumbled across the sub. The software have to control the hardware.
All packages are up to date. My knowledge is far away from being able to solve the bug. More precise - I realized this later on - is that the system locks when X was running, even in a remote console session. Jun 05 18:41:54 djm kernel: hub 1-1:1. What's the best way to get the journalctl -ar output into a textfile? One gets this panic, the other doesn't. As I did run into this issue too, I want to share my experience about what I did to solve it. So I decided to start from here and removed all modules which are not nessecary for my hardware from the kernel.
All I want is to be able to run a proper Linux distro off the stick with persistence. If kernel-tools is installed, you might need to do a 'systemctl stop cpupower. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Elder speaking about Xorg and Wayland sessions. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously. Just the other day, I wiped the hard drive and did a fresh install of Fedora 26 on this particular box, and the problem is still happening.
The locks came up randomly, but always during an X session. Any thoughts are welcome, thank you! Expected results: smooth boot up. The correct firmware was in linux-firmware-20160331 which I did install shortly after. Hopefully it was just a one-off. Last edited by frostbittenking 2014-02-07 11:25:56. Except same symptoms, I see no similarities between the traces. If I do prime-select intel, and try to log off, it gets stuck and I have to reboot it multiple times to make it boot.
If X was not started at all I haven't had lockups. Jun 05 18:42:00 djm kernel: hub 1-1:1. I will upload whatever info is helpful, if asked. However, the system journal is absolutely rife with other messages that are telling me that something doesn't smell right. Please test this kernel update or newer and let us know if you issue has been resolved or if it is still present with the newer kernel.
However I also have problems. What This Sub Is This subreddit is for the latest news and updates regarding Tails, requesting Tails support, and discussion regarding the Tails project. Additional info: Same hard ware new hard disk, so new install did not seem to have problem earlier. Jun 05 18:41:41 djm kernel: hub 1-1:1. I looked at my old logs - it is identical hardware and almost identical software, except for a new hard disk as the old was showing a fair number of smartd errors.
From my knowledge base - I know enough to know that I know nothing. I barely managed to login with the keyboard the system was no longer responsive over the network. I tried to reboot, but after 30 minutes, the system almost completed the procedure, but got stuck, so I had to force a reset Magic SysRq key was disabled by default The kernel was 4. I could hear a fan inside the laptop going crazy, and the temperature was going up. I also tested with the default current kernel 4. Only one graphic card was connected to a monitor at the same time.