Bug 1400956 - Kernel crashes hard since upgading to Fedora 25
Summary: Kernel crashes hard since upgading to Fedora 25
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1401056 1401057
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-02 12:06 UTC by Richard W.M. Jones
Modified: 2019-01-09 12:54 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:03:33 UTC
Type: Bug


Attachments (Terms of Use)
Xorg log file (36.53 KB, text/plain)
2016-12-02 12:06 UTC, Richard W.M. Jones
no flags Details

Description Richard W.M. Jones 2016-12-02 12:06:31 UTC
Created attachment 1227296 [details]
Xorg log file

Description of problem:

Since upgrading to Fedora 25, the kernel crashes hard, daily,
during routine activity such as web browsing.

I have a reproducer (for me at least) which is playing a
specific video.  The machine will crash hard after about 5-15
minutes of playing this video.

The only thing to do is to hard reboot.

Also ssh and ping stop during the crash, so I was not able to
see if the kernel dumps and info to the message log.

I am going to try to see if kdump can capture anything.

Version-Release number of selected component (if applicable):

Both of the following kernels crash:
kernel-4.8.8-300.fc25.x86_64
kernel-4.8.10-300.fc25.x86_64

How reproducible:

100%

Steps to Reproduce:

It crashes during routine activity such as web browsing, but
I also found that playing a specific video in VLC crashes the
machine reproducibly.

Additional information:

Lenovo Thinkpad T450s

Xorg log attached.

Comment 1 Richard W.M. Jones 2016-12-02 12:38:57 UTC
Sadly kdump didn't capture anything.

Comment 2 Richard W.M. Jones 2016-12-02 15:05:38 UTC
(In reply to Richard W.M. Jones from comment #1)
> Sadly kdump didn't capture anything.

Actually kdump appears to be broken.  I'll file a separate
bug about that.

Comment 3 Florian Weimer 2016-12-02 15:57:25 UTC
(In reply to Richard W.M. Jones from comment #1)
> Sadly kdump didn't capture anything.

What about netconsole?

Comment 4 Richard W.M. Jones 2016-12-02 16:15:48 UTC
netconsole fails to load with:
# modprobe netconsole netconsole=@/wlp3s0,@192.168.0.167/modprobe: ERROR: could not insert 'netconsole': Unknown error 524

I'll file a bug about this one too.

Comment 5 Richard W.M. Jones 2016-12-02 16:24:49 UTC
OK turns out that "Unknown error 524" really means "the error was
written to dmesg", and the real error was that netconsole doesn't
support wifi.  I don't have an ethernet cable to hand, so I'll
have to try out netconsole a bit later.

Comment 6 Laura Abbott 2017-01-17 01:25:15 UTC
*********** MASS BUG UPDATE **************
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 25 kernel bugs.
 
Fedora 25 has now been rebased to 4.9.3-200.fc25.  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 26, and are still experiencing this issue, please change the version to Fedora 26.
 
If you experience different issues, please open a new bug report for those.

Comment 7 Richard W.M. Jones 2017-01-17 06:26:51 UTC
Why even bother filing kernel bugs?

Comment 8 Justin M. Forbes 2017-04-11 14:56:09 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 25 kernel bugs.

Fedora 25 has now been rebased to 4.10.9-200.fc25.  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 26, and are still experiencing this issue, please change the version to Fedora 26.

If you experience different issues, please open a new bug report for those.

Comment 9 Richard W.M. Jones 2017-04-12 10:26:13 UTC
Still crashing every few days.

Comment 10 Fedora End Of Life 2017-11-16 19:27:59 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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.

Comment 11 Fedora End Of Life 2017-12-12 10:03:33 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.


Note You need to log in before you can comment on or make changes to this bug.