On Wed, Jul 1, 2015 at 8:45 AM, Craig Goodyear <cjhs22a@xxxxxxxxxxxx> wrote: > Where do I start in order to determine the cause of this problem? The closest thing I find that are semi recent is https://bbs.archlinux.org/viewtopic.php?id=184783 So it sounds like a hardware bug that the kernel previously worked around and now it's not working around it (?) and thus is a kernel bug. Try using a different kernel. kernel-4.0.7-300.fc22 is in updates-testing repo so you could easily try that. If that doesn't work then I'd go to koji and get kernel-4.1.0-1.fc23. If that doesn't work, then I suggest you go backwards to the newest Fedora 21 kernel available which presumably will work since it worked for you before. And you can stick with that for now. But then you'll need to file a bug report, including which kernels you've tested, which versions have the problem and don't. And full details on your hardware, like an lspci -vvnn > lspci.txt and attach that file. Same with dmesg > dmest.txt, and attach that. (Anything either long, or important to format correctly without web browser wrapping issues should be attachments.) Before you get started, you should probably change /etc/dnf/dnf.conf such that installonly_limit is set to something like 10, just to make sure dnf doesn't start deleting kernels. You can clean this up later, which is a bit tedious, but that's another matter. -- Chris Murphy -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
