From: Matthias Prager <linux@matthiasprager.de>
To: Robert Trace <maillist@farcaster.org>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
Tejun Heo <tj@kernel.org>,
linux-scsi@vger.kernel.org, Jens Axboe <jaxboe@fusionio.com>,
Eric Moore <Eric.Moore@lsi.com>, Alan <alan@lxorguk.ukuu.org.uk>,
"Darrick J. Wong" <djwong@us.ibm.com>,
linux-ide@vger.kernel.org,
Matthias Prager <linux@matthiasprager.de>
Subject: Re: 'Device not ready' issue on mpt2sas since 3.1.10
Date: Thu, 16 Aug 2012 22:24:56 +0200 [thread overview]
Message-ID: <502D5718.1030303@matthiasprager.de> (raw)
In-Reply-To: <502D3B69.1090403@farcaster.org>
Am 16.08.2012 20:26, schrieb Robert Trace:
> On 07/25/2012 03:55 PM, James Bottomley wrote:
>>
>> Well, reading it, so do I. Unfortunately, we get to deal with the world
>> as it is rather than as we would wish it to be. We likely have this
>> problem with a lot of USB SATLs as well ...
>
> Has this patch made it into the main git trees yet?
Not yet, but it is in James scsi misc tree and last I heard was
scheduled for inclusion in the 3.6 kernel.
Anyways here is his commit:
<http://git.kernel.org/?p=linux/kernel/git/jejb/scsi.git;a=commit;h=98dc81b0d6c483a3eb256764ae10f156ccefdbbb>
>
> I haven't seen anything about it in nearly a month, but I've been using
> the James' patch since he posted it and the sleep/wakeup behavior seems
> improved/correct.
I have been running smoothly with the patch too - problem solved I'd say :-)
>
> -- Robert
>
next prev parent reply other threads:[~2012-08-16 20:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4FFB32E5.1050109@farcaster.org>
[not found] ` <4FFB7354.8040809@matthiasprager.de>
[not found] ` <4FFB8A86.7000009@farcaster.org>
[not found] ` <4FFCBA4C.4000502@farcaster.org>
[not found] ` <4FFD6F3D.2030708@matthiasprager.de>
[not found] ` <4FFD8410.7050604@matthiasprager.de>
[not found] ` <20120717180932.GB2878@google.com>
[not found] ` <5005BF7D.2050703@matthiasprager.de>
[not found] ` <20120717200136.GC24336@google.com>
[not found] ` <500A9D7C.8080801@matthiasprager.de>
[not found] ` <20120722173146.GE5144@dhcp-172-17-108-109.mtv.corp.google.com>
2012-07-25 14:19 ` 'Device not ready' issue on mpt2sas since 3.1.10 James Bottomley
2012-07-25 17:17 ` Tejun Heo
2012-07-25 19:55 ` James Bottomley
2012-07-25 23:56 ` Matthias Prager
2012-07-26 19:16 ` Robert Trace
2012-08-16 18:26 ` Robert Trace
2012-08-16 20:24 ` Matthias Prager [this message]
2012-08-16 20:33 ` Robert Trace
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=502D5718.1030303@matthiasprager.de \
--to=linux@matthiasprager.de \
--cc=Eric.Moore@lsi.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=djwong@us.ibm.com \
--cc=jaxboe@fusionio.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=maillist@farcaster.org \
--cc=tj@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;
as well as URLs for NNTP newsgroup(s).