public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Woody Suwalski <terraluna977@gmail.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com
Subject: Re: 4.10-rc1: thinkpad x60: who ate my cpu?
Date: Sun, 15 Jan 2017 10:56:56 +0100	[thread overview]
Message-ID: <20170115095656.GA16524@amd> (raw)
In-Reply-To: <20170114113054.GA22012@amd>

[-- Attachment #1: Type: text/plain, Size: 1335 bytes --]

On Sat 2017-01-14 12:30:54, Pavel Machek wrote:
> Hi!
> 
> On Thu 2017-01-12 20:19:31, Woody Suwalski wrote:
> > Pavel Machek wrote:
> > >Hi!
> > >
> > >>I used to have two cpus, and Thinkpad X60 should have two cores, but I
> > >>only see one on 4.10-rc1. This machine went through many
> > >>suspend/resume cycles. When backups finish, I'll try -rc2.
> > >Whoever did it, he seems to have returned the cpu in -rc3. All seems
> > >to be good now.
> 
> > Actually since you have mentioned - I have checked my x60 - same problem -
> > only one CPU. However I was running 4.8.13 with uptime 33 days, multiple
> > sleep/wake-ups.
> > Installed a current EOL 4.8.17 and rebooted - I see 2 CPUs. So the issue is
> > older then 4.10 kernel, and I suspect it is the CPU hotplug / wakeup
> > related...
> 
> Hmm. So I seen two cores in -rc3 after boot. But it is quite well
> possible that -rc1 was ok just after boot, too, and problem happened
> sometime later (probably during suspend/resume cycles). Let me go back
> to -rc1 to check.

Indeed in -rc1 I see both CPUs after boot. So we have hard to
reproduce case where 4.8 to 4.10 kernels lose one of the cpu cores...



-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2017-01-15  9:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-08 22:17 4.10-rc1: thinkpad x60: who ate my cpu? Pavel Machek
2017-01-09  9:30 ` Pavel Machek
2017-01-13  1:19   ` Woody Suwalski
2017-01-14 11:30     ` Pavel Machek
2017-01-15  9:56       ` Pavel Machek [this message]
2017-02-11 23:48         ` Woody Suwalski
2017-02-12 15:43           ` Woody Suwalski
2017-02-12 19:57             ` Pavel Machek
2017-02-13  1:35               ` Woody Suwalski
2017-02-13  8:02                 ` Pavel Machek
2017-02-13  8:48                   ` Thomas Gleixner
2017-02-13  9:42                     ` Pavel Machek
2017-02-13 10:18                       ` lkml
2017-02-13 11:25                         ` Thomas Gleixner
2017-02-13 11:39                           ` lkml
2017-02-13 11:40                           ` lkml
2017-02-13 11:53                         ` Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170115095656.GA16524@amd \
    --to=pavel@ucw.cz \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rjw@rjwysocki.net \
    --cc=terraluna977@gmail.com \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox