From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
x86@kernel.org, Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: Dell Studio 1536 needs pci=nocrs to boot.
Date: Tue, 3 Jan 2012 09:30:20 -0800 [thread overview]
Message-ID: <20120103093020.0cbcd735@jbarnes-desktop> (raw)
In-Reply-To: <20120101145354.GA1791@elte.hu>
[-- Attachment #1: Type: text/plain, Size: 794 bytes --]
On Sun, 1 Jan 2012 15:53:54 +0100
Ingo Molnar <mingo@elte.hu> wrote:
>
> * Dave Jones <davej@redhat.com> wrote:
>
> > Some machines don't boot unless passed pci=nocrs.
> > (See https://bugzilla.redhat.com/show_bug.cgi?id=770308 for details of
> > one report. Waiting on dmidecode output for others).
> >
> > Currently there is a DMI whitelist, even though the default is on.
> >
> > This patch extends that dmi list to add a blacklist to automatically
> > apply disable it when necessary.
> >
> > Signed-off-by: Dave Jones <davej@redhat.com>
>
> Acked-by: Ingo Molnar <mingo@elte.hu>
>
> Jesse, will you take this one?
Yeah, I can take it. Bjorn, any comment (I'll bounce over the
original)?
Thanks,
--
Jesse Barnes, Intel Open Source Technology Center
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-01-03 17:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-30 19:37 Dell Studio 1536 needs pci=nocrs to boot Dave Jones
2012-01-01 14:53 ` Ingo Molnar
2012-01-03 17:30 ` Jesse Barnes [this message]
2012-01-03 17:55 ` Bjorn Helgaas
2012-01-03 18:00 ` Dave Jones
2012-01-06 17:32 ` Bjorn Helgaas
2012-01-06 17:57 ` Dave Jones
2012-01-06 20:10 ` Jesse Barnes
2012-01-04 16:33 ` Add Dell Studio 1557 to pci=nocrs blacklist Dave Jones
2012-01-04 17:08 ` Jesse Barnes
2012-01-04 18:37 ` Ingo Molnar
2012-01-11 16:07 ` Bjorn Helgaas
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=20120103093020.0cbcd735@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=bhelgaas@google.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=x86@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.