Re: [PATCH] x86: mpparse: fix mp_bus_not_pci handling

From: Ingo Molnar
Date: Tue Oct 18 2011 - 02:37:19 EST



* Bjorn Helgaas <bhelgaas@xxxxxxxxxx> wrote:

> On Sun, Sep 25, 2011 at 3:29 PM, Bjorn Helgaas <bhelgaas@xxxxxxxxxx> wrote:
> > Dan bisected a Dell PowerEdge 4200 boot regression to commit f8924e770.
> > Prior to that commit, 32-bit kernels set mp_bus_not_pci for all buses
> > except PCI.  Afterwards, we set mp_bus_not_pci only for ISA.  But ISA is
> > not the only non-PCI bus, so it's better to always set mp_bus_not_pci
> > and clear it only for PCI.
> >
> > The workaround was to boot with "noapic".  Dan verified that with this
> > patch, his system boots without "noapic".
> >
> > Reference: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586494
> > Reported-and-tested-by: Dan McGrath <troubledaemon@xxxxxxxxx>
> > Cc: Alexey Starikovskiy <astarikovskiy@xxxxxxx>
> > Cc: stable@xxxxxxxxxx # 2.6.26+
> > Signed-off-by: Bjorn Helgaas <bhelgaas@xxxxxxxxxx>
> > ---
> >  arch/x86/kernel/mpparse.c |    2 +-
> >  1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/arch/x86/kernel/mpparse.c b/arch/x86/kernel/mpparse.c
> > index 9103b89..0741b062 100644
> > --- a/arch/x86/kernel/mpparse.c
> > +++ b/arch/x86/kernel/mpparse.c
> > @@ -95,8 +95,8 @@ static void __init MP_bus_info(struct mpc_bus *m)
> >        }
> >  #endif
> >
> > +       set_bit(m->busid, mp_bus_not_pci);
> >        if (strncmp(str, BUSTYPE_ISA, sizeof(BUSTYPE_ISA) - 1) == 0) {
> > -               set_bit(m->busid, mp_bus_not_pci);
> >  #if defined(CONFIG_EISA) || defined(CONFIG_MCA)
> >                mp_bus_id_to_type[m->busid] = MP_BUS_ISA;
> >  #endif
> >
> >
>
> Ping? I don't see this in linux-next, so I don't know if it got
> dropped or if there's something wrong with it.

Please resend - this is one of the mails that got lost in my korg
email disconnect.

Patch looks good at first sight.

Thanks,

Ingo
--
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/