Bug 1101344 - smpboot randomly detects that CPUs are "not responding" and boots with only one CPU core
Summary: smpboot randomly detects that CPUs are "not responding" and boots with only o...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 20
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-27 02:48 UTC by Jean-François Fortin Tam
Modified: 2015-09-08 14:17 UTC (History)
31 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-12-10 14:59:08 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
journalctl output (16.29 KB, text/plain)
2014-05-27 02:48 UTC, Jean-François Fortin Tam
no flags Details

Description Jean-François Fortin Tam 2014-05-27 02:48:35 UTC
Created attachment 899366 [details]
journalctl output

I didn't notice this with previous kernels, but with 3.14 (3.14.3 is the version I'm currently running on Fedora 20 64-bits), my desktop machine randomly boots with only one core enabled (out of the 4 cores of my Intel Core2 Quad).

The result is that any operation feels sluggish (gnome shell animations are slow, restoring Firefox's tabs is sluggish, refreshing Evolution mail folders is slow, etc.).

Soft-reboots (sometimes multiple times) "fixes" the issue (until it reappears at some other boot instance).

Attaching a journalctl output that mirrors what I shortly see "before plymouth starts" on boot when this happens (more details in the log, at the end):

> smpboot: CPU1: Not responding
> smpboot: CPU2: Not responding
> smpboot: CPU3: Not responding

Comment 1 Justin M. Forbes 2014-11-13 15:59:01 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 20 kernel bugs.

Fedora 20 has now been rebased to 3.17.2-200.fc20.  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 21, and are still experiencing this issue, please change the version to Fedora 21.

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

Comment 2 Justin M. Forbes 2014-12-10 14:59:08 UTC
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 3 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.

Comment 3 Jakub 2015-09-08 11:07:18 UTC
thsi issue has reoccurred on the 4.3 kernel in current rawhide but only on my core2 duo T5600 CPU in my laptop. and only with the 4.3. kernel.
4.2 works fine.
my core2 quad in the desktop (also fedora rawhide) seems unaffected and uses all 4 cores

there is generally a slowdown with newly issued kernels. is this intentional? can be mostly (not sure if even ONLY) seen when using flash. this applies for both systems.


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