public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Joseph Salisbury <joseph.salisbury@canonical.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Regression introduced in v3.2.12 stable
Date: Thu, 22 Mar 2012 14:52:23 -0700	[thread overview]
Message-ID: <20120322215223.GA18689@kroah.com> (raw)
In-Reply-To: <4F6B9D0E.2040308@canonical.com>

On Thu, Mar 22, 2012 at 05:43:42PM -0400, Joseph Salisbury wrote:
> On 03/22/2012 05:26 PM, Greg KH wrote:
> > On Thu, Mar 22, 2012 at 03:15:03PM -0400, Joseph Salisbury wrote:
> >> I figured I'd send a heads up regarding a possible regression in v3.2.12
> >> stable.  The issue prevents systems from booting.
> >>
> >> There have been a few bugs[0] reported against the Ubuntu kernel, which
> >> was recently rebased to 3.2.12.  We're in the process of bisecting now
> >> and will post an update..
> > 
> > What specifically happens here when the system does not boot?  Any error
> > message?  Are you sure this isn't the known pci express issue showing up
> > here?
> > 
> > Can you run 'git bisect' to trace it down to a specific patch please?
> > 
> > thanks,
> > 
> > greg k-h
> 
> Hi Greg,
> 
> Thanks for the response.
> 
> We did some bisecting/testing and identified the bad commit in 3.2.12 as
> the following:
> 
> f043ddb60c84ea64a23b755004572afe922e653c PCI: ignore pre-1.1 ASPM
> quirking when ASPM is disabled

Yup, that's the known problem one.  But, note that it does solve other
people's problems at the moment, so you can't just ignore it :)

greg k-h

  reply	other threads:[~2012-03-22 21:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-22 19:15 Regression introduced in v3.2.12 stable Joseph Salisbury
2012-03-22 19:56 ` Joseph Salisbury
2012-03-22 21:26 ` Greg KH
2012-03-22 21:43   ` Joseph Salisbury
2012-03-22 21:52     ` Greg KH [this message]
2012-03-22 21:53       ` Joseph Salisbury

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=20120322215223.GA18689@kroah.com \
    --to=greg@kroah.com \
    --cc=joseph.salisbury@canonical.com \
    --cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox