All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Artem S. Tashkinov" <t.artem@lycos.com>
To: patrik.r.jakobsson@gmail.com
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
Subject: Re: Abysmal HDD/USB write speed after sleep on a UEFI system
Date: Wed, 8 May 2013 08:37:53 +0000 (UTC)	[thread overview]
Message-ID: <1786821921.88859.1368002273356.JavaMail.mail@webmail05> (raw)
In-Reply-To: CAMeQTsY1jc99boFC_KDTL=-Pt-W1q5ZiS+r89QkPE+vAk386UQ@mail.gmail.com

May 8, 2013 04:25:43 AM, Patrik Jakobsson wrote:
On Wed, May 8, 2013 at 12:02 AM, Bjorn Helgaas wrote:
>> On Tue, May 7, 2013 at 2:48 PM, Patrik Jakobsson wrote:
>>> On Tue, May 7, 2013 at 10:20 PM, Bjorn Helgaas  wrote:
>>>>> I'm not sure if reading /proc/mtrr actually reads the registers out of
>>>>> the CPU each time, or whether we just return the cached values we read
>>>>> out during initial boot-up. If the latter, then this output isn't
>>>>> really useful as there's no guarantee the values are still intact.
>>>>
>>>> Good point.  From what I can tell, on Artem's system with "CPU0:
>>>> Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz," we would be using
>>>> generic_mtrr_ops, and generic_get_mtrr() appears to read from the
>>>> MSRs, so I think it should be useful.
>>>
>>> FWIW, that motherboard suffers from a PCI to PCIE bridge problem. It might
>>> have been fixed by bios upgrades by now but not sure.
>>>
>>> It might also suffer (depending on the revision) from the Sandy bridge SATA
>>> issue. So if affected, SATA controller is a ticking bomb.
>>>
>>> I have a P8H67-V motherboard but I haven't seen any suspend related issues.
>>>
>>> If this is totally unrelated I'm sorry for wasting your time. Just thought it
>>> might be good to know.
>>
>> Thanks for chiming in.  I'm not familiar with either of the issues you
>> mentioned.  Do you have any references where I could read up on them?
>
>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.

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

>> And the issue affects both USB and a hard drive, so I suspect it's
>> more than just SATA.  Artem, did you identify the PCI devices leading
>> to your USB and hard drive?  I can't remember if I've actually seen
>> that.

  reply	other threads:[~2013-05-08  8:37 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <587312497.6453.1360650312498.JavaMail.mail@webmail01>
2013-02-12 17:29 ` Abysmal HDD/USB write speed after sleep on a UEFI system Linus Torvalds
2013-02-12 18:29   ` Artem S. Tashkinov
2013-02-12 19:32     ` Linus Torvalds
2013-02-12 20:13       ` Artem S. Tashkinov
2013-02-13  4:26         ` Bjorn Helgaas
2013-02-19 16:22           ` Alan Stern
2013-02-25 21:57             ` Bjorn Helgaas
2013-02-26  6:35               ` Artem S. Tashkinov
2013-02-26 18:46                 ` Bjorn Helgaas
2013-02-26 19:14                   ` Artem S. Tashkinov
2013-03-07  0:17                     ` Bjorn Helgaas
2013-04-26 21:36                       ` Bjorn Helgaas
2013-04-27 10:10                         ` Artem S. Tashkinov
2013-04-30  4:47                           ` Bjorn Helgaas
2013-05-01  4:19                             ` Robert Hancock
2013-05-07 15:25                               ` Bjorn Helgaas
2013-05-07 15:59                                 ` Artem S. Tashkinov
2013-05-07 16:27                                   ` Bjorn Helgaas
2013-05-07 18:50                                     ` Artem S. Tashkinov
2013-05-07 18:54                                       ` Bjorn Helgaas
2013-05-07 19:05                                   ` Robert Hancock
2013-05-07 20:20                                     ` Bjorn Helgaas
2013-05-07 21:48                                       ` Patrik Jakobsson
2013-05-07 22:02                                         ` Bjorn Helgaas
2013-05-07 22:25                                           ` Patrik Jakobsson
2013-05-08  8:37                                             ` Artem S. Tashkinov [this message]
2013-05-08  8:54                                               ` Patrik Jakobsson
2013-05-08 13:43                                               ` Phillip Susi
2013-05-08  8:31                                           ` Artem S. Tashkinov
2013-05-07 16:12                                 ` Phillip Susi
2013-07-10 17:25   ` hyphop
2013-07-10 20:50     ` Bjorn Helgaas
2013-02-10 10:43 Artem S. Tashkinov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1786821921.88859.1368002273356.JavaMail.mail@webmail05 \
    --to=t.artem@lycos.com \
    --cc=bhelgaas@google.com \
    --cc=hancockrwd@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=patrik.r.jakobsson@gmail.com \
    --cc=psusi@ubuntu.com \
    --cc=rjw@sisk.pl \
    --cc=stern@rowland.harvard.edu \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.