Created attachment 1306542 [details] syslog entry for kernel BUG Description of problem: After upgrading from Fedora 25 (which worked fine) to Fedora 26, The following happens: - System starts without obvious problems - Desktop environment (FVWM) starts without obvious problems - everything appears to be working fine - when I try to start firefox, I get the following messages on the console: Message from syslogd@nyx at Jul 30 11:40:10 ... kernel:page:fffff5c5061e2600 count:0 mapcount:-127 mapping: (null) index:0x0 Message from syslogd@nyx at Jul 30 11:40:10 ... kernel:flags: 0x17ffffc0000000() ...and firefox does not come up. The syslog contains an error entry (see attachment): Jul 30 11:40:10 nyx kernel: page:fffff5c5061e2600 count:0 mapcount:-127 mapping: (null) index:0x0 Jul 30 11:40:10 nyx kernel: flags: 0x17ffffc0000000() Jul 30 11:40:10 nyx kernel: raw: 0017ffffc0000000 0000000000000000 0000000000000000 00000000ffffff80 Jul 30 11:40:10 nyx kernel: raw: fffff5c507670020 ffff9b061ffd1ef8 0000000000000003 0000000000000000 Jul 30 11:40:10 nyx kernel: page dumped because: VM_BUG_ON_PAGE(page_ref_count(page) == 0) Jul 30 11:40:10 nyx kernel: ------------[ cut here ]------------ Jul 30 11:40:10 nyx kernel: kernel BUG at ./include/linux/mm.h:462! Jul 30 11:40:10 nyx kernel: invalid opcode: 0000 [#2] SMP - From then, all attempts to access the filesystem (i. e. a simple "ls /" will hang permanently in uninterruptable sleep ('D' in ps). - in 4 out of 5 attepmts this happened while firefox was starting, before any window was displayed. - in one attempt firefox came up, but the same error happened when I tried to open a web page. Running another kernel in the same installation works fine (kernel-4.11.12-200.fc25.x86_64 - i. e. basically same kernel version, but previous fedora release) Version-Release number of selected component (if applicable): kernel-4.11.12-100.fc24.x86_64 How reproducible: Always Steps to Reproduce: 1. Boot the system 2. Login 3. start firefox Actual results: Kernel Bug, system becomes unusable Expected results: no bug Additional info: see attachment for full syslog entry
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. The kernel moves very fast so bugs may get fixed as part of a kernel update. Due to this, we are doing a mass bug update across all of the Fedora 26 kernel bugs. Fedora 26 has now been rebased to 4.15.4-200.fc26. 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. If you have moved on to Fedora 27, and are still experiencing this issue, please change the version to Fedora 27. If you experience different issues, please open a new bug report for those.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.