Re: Dell Studio 1536 needs pci=nocrs to boot.

[Bjorn Helgaas]

On Tue, Jan 3, 2012 at 11:00 AM, Dave Jones <davej@xxxxxxxxxx> wrote:
> On Tue, Jan 03, 2012 at 10:55:00AM -0700, Bjorn Helgaas wrote:
>  > On Tue, Jan 3, 2012 at 10:30 AM, Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx> wrote:
>  > > On Sun, 1 Jan 2012 15:53:54 +0100
>  > > Ingo Molnar <mingo@xxxxxxx> wrote:
>  > >
>  > >>
>  > >> * Dave Jones <davej@xxxxxxxxxx> 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@xxxxxxxxxx>
>  > >>
>  > >> Acked-by: Ingo Molnar <mingo@xxxxxxx>
>  > >>
>  > >> Jesse, will you take this one?
>  > >
>  > > Yeah, I can take it.  Bjorn, any comment (I'll bounce over the
>  > > original)?
>  >
>  > This is a band-aid, and we'll have to extend the blacklist for other
>  > machines, but it's the best we have right now, so I think it's the
>  > right thing to do.
>  >
>  > It's probably the same as
>  > https://bugzilla.kernel.org/show_bug.cgi?id=31602 (Dell 1546) and
>  > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/647043
>
> There's at least one more dell (Seems that entire 'studio' product line
> is affected) that I'm waiting on DMI data from.
> Also a thinkpad that I have a patch pending for.

I think we should drop the Dell 1536 blacklist entry from this patch
(adding set_nouse_crs() itself is fine and may be needed for other
machines).

The patches here: https://lkml.org/lkml/2012/1/5/402 should cover the
Dell 1536 issue as well as the Dell 1546 and any others with the same
BIOS defect.

Bjorn
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/