[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110304175210.GA3798@xanatos>
Date: Fri, 4 Mar 2011 09:52:10 -0800
From: Sarah Sharp <sarah.a.sharp@...ux.intel.com>
To: "Rafael J. Wysocki" <rjw@...k.pl>
Cc: linux-usb@...r.kernel.org, linux-pci@...r.kernel.org,
linux-kernel@...r.kernel.org,
Jesse Barnes <jbarnes@...tuousgeek.org>,
Ozan Caglayan <ozan@...dus.org.tr>
Subject: Re: [PATCH 0/2] Re: 2.6.38 regression caused by commit 415e12b
On Wed, Mar 02, 2011 at 11:30:49PM +0100, Rafael J. Wysocki wrote:
> On Wednesday, March 02, 2011, Rafael J. Wysocki wrote:
> > 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.
I applied your patches on top of 2.6.38-rc6 again and tested them.
dmesg is attached. Let me know if you need me to test Linus' latest
instead.
Sarah Sharp
View attachment "dmesg-2011-03-04-08-37.txt" of type "text/plain" (75904 bytes)
Powered by blists - more mailing lists