[PATCH 0/2] Re: 2.6.38 regression caused by commit 415e12b

From: Rafael J. Wysocki
Date: Wed Mar 02 2011 - 17:34:39 EST


On Wednesday, March 02, 2011, Rafael J. Wysocki wrote:
> On Wednesday, March 02, 2011, Sarah Sharp wrote:
> > On Wed, Mar 02, 2011 at 01:17:04AM +0100, Rafael J. Wysocki wrote:
> > > On Wednesday, March 02, 2011, Sarah Sharp wrote:
> > > > On Wed, Mar 02, 2011 at 12:30:16AM +0100, Rafael J. Wysocki wrote:
> > > > > On Tuesday, March 01, 2011, Sarah Sharp wrote:
> > > > > > On Tue, Mar 01, 2011 at 09:55:33PM +0100, Rafael J. Wysocki wrote:
> > > > > > > Please check if the appended patch (on top of the Linus' current) helps.
> > > > > >
> > > > > > Sorry, it doesn't help. Same message as before.
> > > > >
> > > > > Can you send dmesg with the patch applied, please?
> > > >
> > > > Attached.
> > >
> > > Something's fishy. Evidently, _OSC is not executed on your system
> > > although it should be with the patch.
> > >
> > > Please try the patch below instead and send dmesg (either way).
> >
> > The host controller works with that patch. dmesg is attached.
>
> OK, thanks.
>
> There are two problems. First, your BIOS says that ASPM is not supported
> by it, so we don't call _OSC, which should be fixed by the previous patch.
> Second, pci_msi_enabled() returns 0 on your system, which is kind of strange,
> because it evidently uses MSIs (as visible in the dmesg).
>
> While I think we can safely request _OSC control even if ASPM is not supported
> by the hardware (according to the BIOS), which is done after the first patch,
> we need to figure out why 0 is returned by pci_msi_enabled() on your system
> and try to work around that.

Regardless, I think we should report MSI and ASPM support to the BIOS unless
directly disabled via the kernel command line or .config.

I'm going to send two patches in replies to this message. Please apply them
both on top of 2.6.38-rc7 and report back.

Thanks,
Rafael

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