All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Leach <matthew@mattleach.net>
To: Ingo Molnar <mingo@kernel.org>
Cc: Kan Liang <kan.liang@intel.com>,
	linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org
Subject: Re: [BUG]: Intel uncore boot warning introduced in 4.1
Date: Thu, 06 Aug 2015 16:13:14 +0000	[thread overview]
Message-ID: <87bneko0o5.fsf@mattleach.net> (raw)
In-Reply-To: <1438853676.3139.20.camel@mattleach.net> (Matthew Leach's message of "Thu, 06 Aug 2015 10:34:36 +0100")

Hi Ingo,

Matthew Leach <matthew@mattleach.net> writes:

[...]

> I've bisected the kernel and found that commit [2] seems to introduce
> the warning message.  I have checked on a v4.2-rc5 kernel and the
> warning message is still there.

[...]

> [2]: 8cf1a3de97804b047973dd44cfacdc1930da8403

Apologies, I got it wrong.  The commit that is causing the issue is [1].
If I revert it, the warning goes away.  I'm also testing to see if this
is the cause of the random freezing that occurs (which I can confirm is
also happening with v4.2-rc5).

[1]: 15c1247953e8a45232ed5a5540f291d2d0a77665

Thanks,
-- 
Matt

WARNING: multiple messages have this Message-ID (diff)
From: Matthew Leach <matthew@mattleach.net>
To: Ingo Molnar <mingo@kernel.org>
Cc: Kan Liang <kan.liang@intel.com>,
	linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org
Subject: Re: [BUG]: Intel uncore boot warning introduced in 4.1
Date: Thu, 06 Aug 2015 17:13:14 +0100	[thread overview]
Message-ID: <87bneko0o5.fsf@mattleach.net> (raw)
In-Reply-To: <1438853676.3139.20.camel@mattleach.net> (Matthew Leach's message of "Thu, 06 Aug 2015 10:34:36 +0100")

Hi Ingo,

Matthew Leach <matthew@mattleach.net> writes:

[...]

> I've bisected the kernel and found that commit [2] seems to introduce
> the warning message.  I have checked on a v4.2-rc5 kernel and the
> warning message is still there.

[...]

> [2]: 8cf1a3de97804b047973dd44cfacdc1930da8403

Apologies, I got it wrong.  The commit that is causing the issue is [1].
If I revert it, the warning goes away.  I'm also testing to see if this
is the cause of the random freezing that occurs (which I can confirm is
also happening with v4.2-rc5).

[1]: 15c1247953e8a45232ed5a5540f291d2d0a77665

Thanks,
-- 
Matt

  reply	other threads:[~2015-08-06 16:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-06  9:34 [BUG]: Intel uncore boot warning introduced in 4.1 Matthew Leach
2015-08-06  9:34 ` Matthew Leach
2015-08-06 16:13 ` Matthew Leach [this message]
2015-08-06 16:13   ` Matthew Leach
2015-08-06 18:10   ` Liang, Kan
2015-08-06 18:10     ` Liang, Kan
2015-08-06 18:44     ` Matthew Leach
2015-08-06 18:44       ` Matthew Leach
2015-08-07  9:05     ` Peter Zijlstra
2015-08-07  9:05       ` Peter Zijlstra
2015-08-10 13:23       ` Liang, Kan
2015-09-15 13:35         ` Josh Boyer
2015-09-15 13:35           ` Josh Boyer

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=87bneko0o5.fsf@mattleach.net \
    --to=matthew@mattleach.net \
    --cc=kan.liang@intel.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.