Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753638Ab3EHIyu (ORCPT ); Wed, 8 May 2013 04:54:50 -0400 Received: from mail-la0-f41.google.com ([209.85.215.41]:32857 "EHLO mail-la0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751557Ab3EHIyq (ORCPT ); Wed, 8 May 2013 04:54:46 -0400 MIME-Version: 1.0 In-Reply-To: <1786821921.88859.1368002273356.JavaMail.mail@webmail05> References: <337833384.57445.1361860509194.JavaMail.mail@webmail08> <569718148.80620.1361906088301.JavaMail.mail@webmail13> <771333906.75854.1367057440028.JavaMail.mail@webmail08> <518097B8.4020402@gmail.com> <384171828.66802.1367942365492.JavaMail.mail@webmail05> <1786821921.88859.1368002273356.JavaMail.mail@webmail05> Date: Wed, 8 May 2013 10:54:44 +0200 Message-ID: Subject: Re: Abysmal HDD/USB write speed after sleep on a UEFI system From: Patrik Jakobsson To: "Artem S. Tashkinov" Cc: bhelgaas@google.com, hancockrwd@gmail.com, stern@rowland.harvard.edu, torvalds@linux-foundation.org, linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org, rjw@sisk.pl, psusi@ubuntu.com Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1597 Lines: 34 On Wed, May 8, 2013 at 10:37 AM, Artem S. Tashkinov wrote: >>I think this is the official statement from Intel on the SATA issue: >>http://newsroom.intel.com/community/intel_newsroom/blog/2011/01/31/intel-identifies-chipset-design-error-implementing-solution > > My motherboard has a new fixed B3 revision so this issue doesn't affect me. > Besides this SATA ports degradation issue is constantly present - it has no > relationship to suspend. Yes, Rev. B3 should be fine. >>And here's a link to a discussion about the PCIe-to-PCI bridge stuff: >>https://lkml.org/lkml/2012/1/30/216 >> >>> Artem's system has a PCIe-to-PCI bridge (not a PCI-to-PCIe bridge) at >>> 05:00.0, but it leads to [bus 06] and there's nothing on bus 06, so I >>> don't think that's the problem. >> >>I meant what you said ;) and yes, it seems unrelated. Both my P8H67 and a >>P8P67 I've built behave nicely if nothing is connected. > > Have you tried suspending more than three times? In the absence of UEFI > boot this bug emerges only on a third or even fourth resume attempt. UEFI > boot triggers it immediately on a first resume though. I haven't enabled UEFI boot but did ~10 suspend/resume cycles with no issues. I'm on 3.9-rc5 if that makes a difference. I'll do some more testing with various kernel versions to see if I can trigger it. -Patrik -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/