mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Philip Müller" <philm@manjaro.org>
To: Greg KH <gregkh@linuxfoundation.org>, Borislav Petkov <bp@suse.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org, Sudeep Holla <sudeep.holla@arm.com>,
	Guenter Roeck <linux@roeck-us.net>,
	manjaro-dev@manjaro.org, Ingo Molnar <mingo@redhat.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Andre Przywara <andre.przywara@arm.com>,
	manjaro-dev@manjaro.org
Subject: Re: [PATCH] cpu/cacheinfo: Fix teardown path
Date: Sat, 8 Aug 2015 20:23:49 +0200	[thread overview]
Message-ID: <55C64935.4010301@manjaro.org> (raw)
In-Reply-To: <20150808154156.GC11851@kroah.com>

Hi Greg,

I bi-sected it to following commit:

0d55ba46bfbee64fd2b492b87bfe2ec172e7b056 is the first bad commit
commit 0d55ba46bfbee64fd2b492b87bfe2ec172e7b056
Author: Sudeep Holla <sudeep.holla@arm.com>
Date:   Wed Mar 4 12:00:16 2015 +0000

    x86/cacheinfo: Move cacheinfo sysfs code to generic infrastructure

You can follow it on my github repo in rich detail:

https://github.com/philmmanjaro/linux41/blob/master/git-bisect.txt

kind regards
Philip Müller

Am 08.08.2015 um 17:41 schrieb Greg KH:
> On Sat, Aug 08, 2015 at 10:46:02AM +0200, Borislav Petkov wrote:
>> On Mon, Jul 27, 2015 at 09:58:05AM +0200, Borislav Petkov wrote:
>>> Philip Müller reported a hang when booting 32-bit 4.1 kernel on an AMD
>>> box. A fragment of the splat was enough to pinpoint the issue:
>>
>> Bah, this goes to Greg and not to tip. Anyway, here's a version with
>> updated tags.
>>
>> Greg, please queue for 4.2 as it fixes a hang.
> 
> What commit caused this issue?
> 
> And it's a bit late for 4.2, as you say 4.1 is also affected, I'll wait
> for 4.3-rc1 to give this a chance to get some testing.
> 
> thanks,
> 
> greg k-h
> 


  reply	other threads:[~2015-08-08 18:23 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-23 22:23 [linux41] Kernel panic at i686 Philip Müller
2015-07-26  6:18 ` [linux41] regression with 'x86/cacheinfo: Move cacheinfo sysfs code to generic infrastructure' on AMD i686 Philip Müller
2015-07-26  8:13   ` Thomas Gleixner
2015-07-26  8:41     ` Borislav Petkov
2015-07-26 10:54       ` Philip Müller
2015-07-26 14:42         ` Borislav Petkov
2015-07-26 15:59           ` Philip Müller
2015-07-26 16:11             ` Guenter Roeck
2015-09-16 23:52           ` Josh Boyer
2015-09-17  5:36             ` Philip Müller
2015-09-17  7:15             ` Borislav Petkov
2015-09-17 12:54               ` Greg KH
2015-07-27  7:58   ` [PATCH] cpu/cacheinfo: Fix teardown path Borislav Petkov
2015-07-27  8:56     ` Sudeep Holla
2015-07-27 11:10     ` Thomas Gleixner
2015-07-27 18:49       ` Philip Müller
2015-08-05 20:14     ` [tip:x86/urgent] x86/cpu/cacheinfo: " tip-bot for Borislav Petkov
2015-08-08  8:46     ` [PATCH] cpu/cacheinfo: " Borislav Petkov
2015-08-08 15:41       ` Greg KH
2015-08-08 18:23         ` Philip Müller [this message]
2015-08-08 19:42           ` Borislav Petkov
2015-08-08 19:47         ` Borislav Petkov
2015-09-13  7:03           ` Philip Müller

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=55C64935.4010301@manjaro.org \
    --to=philm@manjaro.org \
    --cc=andre.przywara@arm.com \
    --cc=bp@suse.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=manjaro-dev@manjaro.org \
    --cc=mingo@redhat.com \
    --cc=sudeep.holla@arm.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

Powered by JetHome