Bug 1377158 - Kdump kernel will hang if specify notsc in cmdline
Summary: Kdump kernel will hang if specify notsc in cmdline
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Baoquan He
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-19 01:48 UTC by Baoquan He
Modified: 2019-10-28 08:51 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-28 08:51:23 UTC
Type: Bug


Attachments (Terms of Use)

Description Baoquan He 2016-09-19 01:48:28 UTC
Description of problem:
If specify 'notsc' in kdump kernel, then trigger a crash, kdump kernel will
hang in calibrate_delay_converge() and wait for jiffies changes.
serial log as follows:

    tsc: Fast TSC calibration using PIT
    tsc: Detected 2099.947 MHz processor
    Calibrating delay loop...

The reason for jiffies not changes is there's no timer interrupt
passed to dump-capture kernel.
Version-Release number of selected component (if applicable):

This is because no timer interrupt in kdump kernel before apic mode is enabled.

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Laura Abbott 2017-01-17 01:11:07 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 2 Baoquan He 2017-01-17 01:42:35 UTC
This has not been resolved in upstream, change it to rawhide because I didn't saw f26 version.

Comment 3 Dave Young 2019-10-28 08:51:23 UTC
Should have been solved in latest rawhide and F31 kernels, if not please reopen it.


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