Bug 1414616 - System crash not work [NEEDINFO]
Summary: System crash not work
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 25
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-19 02:39 UTC by lijun.bai
Modified: 2019-01-09 12:54 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-28 17:16:10 UTC
Type: Bug
Embargoed:
jforbes: needinfo?


Attachments (Terms of Use)
System crash photo and message (67.49 KB, image/jpeg)
2017-01-19 02:39 UTC, lijun.bai
no flags Details
select kernel (52.38 KB, image/jpeg)
2017-01-19 02:41 UTC, lijun.bai
no flags Details

Description lijun.bai 2017-01-19 02:39:38 UTC
Created attachment 1242325 [details]
System crash photo and message

Description of problem:


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

4.9.3-200.fc25.x86_64 25
How reproducible:


Steps to Reproduce:
1.start computer
2.select above 
3.System crash not login

Actual results:


Expected results:


Additional info:

Comment 1 lijun.bai 2017-01-19 02:41:01 UTC
Created attachment 1242326 [details]
select kernel

Comment 2 Justin M. Forbes 2017-04-11 14:43:27 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 3 Justin M. Forbes 2017-04-28 17:16:10 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. 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.


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