From: "Artem S. Tashkinov" <t.artem@lycos.com>
To: bhelgaas@google.com
Cc: 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: Tue, 26 Feb 2013 06:35:09 +0000 (UTC) [thread overview]
Message-ID: <337833384.57445.1361860509194.JavaMail.mail@webmail08> (raw)
In-Reply-To: CAErSpo7NZoOQZyW76HEoOTVgdqL2CgbVScAeF6HGLAVaNCq0=w@mail.gmail.com
Feb 26, 2013 03:57:52 AM, Bjorn Helgaas wrote:
>
>Where are we at with this, Artem? I assume it's still a problem.
>
Yes, it is, Bjorn.
In order to eliminate this problem I switched back to MBR yesterday, because
so far I haven't received any instructions or guidance as to how I can debug
it further. I'm absolutely sure USB write speed is just another manifestation of
it so I decided not to debug USB specifically (it just doesn't make too much
sense).
What I see is that something terribly wrong is going on but if Linus has no ideas
I, as an average Joe, don't have a slightest clue as to what I can do.
The bug report with necessary, but seemingly useless information, can be
found here: https://bugzilla.kernel.org/show_bug.cgi?id=53551
If anyone comes up with new ideas I can quickly try UEFI again now that I
have two HDDs at my disposal (the old one is formatted as GPT, the new one is
MBR).
Best regards,
Artem
next prev parent reply other threads:[~2013-02-26 6:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <587312497.6453.1360650312498.JavaMail.mail@webmail01>
[not found] ` <CA+55aFyscOeZUPaYj_-QYgjADPD59+=c5aMvtpPEnd1tmpUGiA@mail.gmail.com>
[not found] ` <1362466310.40337.1360693775935.JavaMail.mail@webmail03>
[not found] ` <CA+55aFyK1zhNerWHkd=FMMeTH_sfiL4sBFq00y4n5eAJ88Z_cA@mail.gmail.com>
[not found] ` <1661570408.42886.1360700013207.JavaMail.mail@webmail03>
2013-02-13 4:26 ` Abysmal HDD/USB write speed after sleep on a UEFI system Bjorn Helgaas
2013-02-19 16:22 ` Alan Stern
2013-02-25 21:57 ` Bjorn Helgaas
2013-02-26 6:35 ` Artem S. Tashkinov [this message]
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
2013-05-08 8:31 ` Artem S. Tashkinov
2013-05-07 16:12 ` Phillip Susi
[not found] ` <1373477126220-681610.post@n7.nabble.com>
2013-07-10 20:50 ` Bjorn Helgaas
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=337833384.57445.1361860509194.JavaMail.mail@webmail08 \
--to=t.artem@lycos.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).