From: Martin Steigerwald <martin@lichtvoll.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jeff Chua <jeff.chua.linux@gmail.com>,
Andreas Mohr <andi@lisas.de>, lkml <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: Stop SSD from waiting for "Spinning up disk..."
Date: Thu, 25 Jun 2015 08:08:50 +0200 [thread overview]
Message-ID: <2354996.jDU4uRfO83@merkaba> (raw)
In-Reply-To: <20150625014152.GA9292@kroah.com>
Am Mittwoch, 24. Juni 2015, 18:41:52 schrieb Greg Kroah-Hartman:
> On Thu, Jun 25, 2015 at 07:55:45AM +0800, Jeff Chua wrote:
> > On Thu, Jun 25, 2015 at 12:28 AM, Greg Kroah-Hartman
> >
> > <gregkh@linuxfoundation.org> wrote:
> > > On Thu, Jun 25, 2015 at 12:22:47AM +0800, Jeff Chua wrote:
> > >> Both sda and sdb have the same SSD model.
> > >
> > > That's a bug in your USB bridge chip, odds are it is not reporting the
> > > value properly. There's nothing the scsi core or USB stack can do
> > > about
> > > this, sorry. Please complain to the hardware manufacturer.
> >
> > There are workaround boot cmdline parameters for other things ... any
> > chance to consider one to fix broken rotational option? I'm not sure
> > how many out there are broken, but I really would like a faster way to
> > access my USB SSD without waiting for the "disk spinup".
>
> Just like module paramaters, boot command lines are not for device
> specific attributes, sorry. Again, please contact the manufacturer to
> get this fixed. We can't add a quirk for this bridge because it would
> not work if you really put a rotational disk behind it.
How about a way to override it in sysfs directly during runtime just for a
device individually, like choosing an I/O scheduler for example?
> Given the cheap cost of these types of bridges, I recommend just getting
> one that works.
That is an option as well and may educate hardware manufacturers to look a
bit better at the quality of those devices (at least then Linux market share
in that market increases).
Thanks,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
next prev parent reply other threads:[~2015-06-25 6:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 18:26 Andreas Mohr
2015-06-23 18:55 ` Martin Steigerwald
2015-06-24 16:22 ` Jeff Chua
2015-06-24 16:28 ` Greg Kroah-Hartman
2015-06-24 23:55 ` Jeff Chua
2015-06-25 1:41 ` Greg Kroah-Hartman
2015-06-25 6:08 ` Martin Steigerwald [this message]
2015-06-25 8:52 ` Jeff Chua
-- strict thread matches above, loose matches on Subject: below --
2015-06-22 7:25 Jeff Chua
2015-06-22 15:36 ` Greg Kroah-Hartman
2015-06-23 15:02 ` Jeff Chua
2015-06-23 18:27 ` Frans Klaver
2015-06-23 18:51 ` Marc Burkhardt
2015-06-25 16:21 ` Henrique de Moraes Holschuh
2015-06-25 16:47 ` Joe Perches
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=2354996.jDU4uRfO83@merkaba \
--to=martin@lichtvoll.de \
--cc=andi@lisas.de \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=jeff.chua.linux@gmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®