public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Hurley <peter@hurleysoftware.com>
To: poma <pomidorabelisima@gmail.com>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: apropos Regression with 'x86/cacheinfo: Move cacheinfo sysfs code to generic infrastructure' on AMD i686
Date: Fri, 14 Aug 2015 08:12:33 -0400	[thread overview]
Message-ID: <55CDDB31.2090101@hurleysoftware.com> (raw)
In-Reply-To: <55CDC3E0.8050108@gmail.com>

On 08/14/2015 06:33 AM, poma wrote:
> 
> This is broken almost 2 months.

First reported 19 days ago with fix-it patch on same day.

> Please push this to the stable 4.1.6 and mainline 4.2-rc7.

This has already been answered.

On 08/08/2015 11:41 AM, Greg KH wrote:
> 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

Regards,
Peter Hurley

Ref.
http://www.gossamer-threads.com/lists/linux/kernel/2234622?do=post_view_threaded#2234622


> Ref.
> https://bugzilla.kernel.org/show_bug.cgi?id=101971
> https://bugzilla.redhat.com/show_bug.cgi?id=1253566


  reply	other threads:[~2015-08-14 12:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-14 10:33 apropos Regression with 'x86/cacheinfo: Move cacheinfo sysfs code to generic infrastructure' on AMD i686 poma
2015-08-14 12:12 ` Peter Hurley [this message]
2015-08-16  8:51   ` poma

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=55CDDB31.2090101@hurleysoftware.com \
    --to=peter@hurleysoftware.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pomidorabelisima@gmail.com \
    /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