From: Phillip Susi <psusi@ubuntu.com>
To: "Artem S. Tashkinov" <t.artem@lycos.com>
Cc: patrik.r.jakobsson@gmail.com, 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
Subject: Re: Abysmal HDD/USB write speed after sleep on a UEFI system
Date: Wed, 08 May 2013 09:43:19 -0400 [thread overview]
Message-ID: <518A5677.60203@ubuntu.com> (raw)
In-Reply-To: <1786821921.88859.1368002273356.JavaMail.mail@webmail05>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 5/8/2013 4:37 AM, Artem S. Tashkinov wrote:
> 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 suspend my P8P67 every night. One thing that does come to mind now
though, is that when I first built it, there was a problem involving
suspend and the firewire driver, but IIRC, it manifested as a failure
to suspend with an error in dmesg, so I disabled the firewire
controller since I have no use for it.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJRilZ2AAoJEJrBOlT6nu75IbkH/RdaAwGoBbJbkTxh4vhR3l/+
nILa2X83WwEYADozNL7zi2w8AExTBHzfKZeE7uzXLPzsryPxJxAQY+LtXwRdCHQy
GXVKZL2TpxPsNQTv1uhdCRiSTgIm9U1Y/INPZ2ugn+WbiH9iXzhRzLRgKH3kALO4
OvReW/XQeZ77RP6IaffnoLbStpORAXH+Ttnt5nMdLvm/rGuBlUsyDvT9TAAcF3W1
1muRJnzpDdMj+Ibwn/IW5smp9RBm2EJb2aP2N+KOV7WgiwPC+8T7omWV6Fjl+NI7
xrc8BQTGVfbZJXpeg2KH7v5Ty+M4xFYfdCJjLocL3rFJCYR+3WCDqpRB+I55Yvo=
=eIDL
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-05-08 13:43 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
2013-05-08 8:54 ` Patrik Jakobsson
2013-05-08 13:43 ` Phillip Susi [this message]
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=518A5677.60203@ubuntu.com \
--to=psusi@ubuntu.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=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
--cc=t.artem@lycos.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox