public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Calvin Walton <calvin.walton@kepstin.ca>
To: Romain Francoise <romain@orebokech.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Matthew Garrett <mjg@redhat.com>,
	Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: Linux 3.3 release
Date: Mon, 26 Mar 2012 11:23:53 -0400	[thread overview]
Message-ID: <1332775433.22830.7.camel@ayu> (raw)
In-Reply-To: <87r4wpx7lr.fsf@silenus.orebokech.com>

On Mon, 2012-03-19 at 10:28 +0100, Romain Francoise wrote:
> There seems to be a regression in the final release compared to -rc7,
> specifically this commit:
> 
> > Matthew Garrett (1):
> >       PCI: ignore pre-1.1 ASPM quirking when ASPM is disabled
> 
> causes an early kernel panic on my machine (Intel DP67BG). Reverting the
> change fixes it. Unfortunately it crashes before setting up the video mode
> so I don't have the full stack trace, but RIP points to
> pcie_aspm_init_link_state().
> 
> When the machine boots successfully, dmesg contains the following related
> to ASPM:
> 
> [    0.382384] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
> [    0.433016] pci 0000:06:00.0: disabling ASPM on pre-1.1 PCIe device.  You can enable it with 'pcie_aspm=force'

This commit is also breaking boot on one of my boxes; it's causing the
pata_jmicron driver to fail to detect my IDE boot drive. This was
reported in this thread as well:
https://lkml.org/lkml/2012/3/22/6

Apparently, using the 'pcie_aspm=force' may work around the issue, from
some reports that I've seen when searching around. Haven't tried it
myself, yet.

-- 
Calvin Walton <calvin.walton@kepstin.ca>


  reply	other threads:[~2012-03-26 15:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19  1:25 Linux 3.3 release Linus Torvalds
2012-03-19  9:28 ` Romain Francoise
2012-03-26 15:23   ` Calvin Walton [this message]
2012-04-02 16:46     ` Linus Torvalds
2012-04-02 17:21       ` Romain Francoise

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=1332775433.22830.7.camel@ayu \
    --to=calvin.walton@kepstin.ca \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg@redhat.com \
    --cc=romain@orebokech.com \
    --cc=torvalds@linux-foundation.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