From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Vasily Averin <vvs@parallels.com>
Cc: James Bottomley <jbottomley@parallels.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
Adaptec OEM Raid Solutions <aacraid@adaptec.com>,
Mark Salyzyn <mark_salyzyn@us.xyratex.com>,
Shaohua Li <shaohua.li@intel.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: aacraid controller hangs if kernel uses non-default ASPM policy
Date: Fri, 11 Nov 2011 13:53:00 +0000 [thread overview]
Message-ID: <20111111135300.GA10798@srcf.ucam.org> (raw)
In-Reply-To: <4EBD278B.6050707@parallels.com>
On Fri, Nov 11, 2011 at 05:47:55PM +0400, Vasily Averin wrote:
> It's quite hard to identify all affected hardware, as far as I understand in all cases it was various controllers.
> Probably hardware vendor could do it, but I doubt that it is possible in current situation.
Yeah, without assistance from the vendor it becomes much harder to do.
It's worth noting that there are (as far as I know) no situations in
which we'll enable ASPM when Windows won't if the "Maximum power
savings" option is enabled, so hardware that's broken on Linux should
also be broken on Windows. In theory ASPM should be blacklisted in the
Windows driver .inf, but it turns out that some vendors do it directly
in the drivers instead.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2011-11-11 13:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 9:42 aacraid controller hangs if kernel uses non-default ASPM policy Vasily Averin
2011-11-11 12:27 ` James Bottomley
2011-11-11 13:11 ` Matthew Garrett
2011-11-11 13:47 ` Vasily Averin
2011-11-11 13:53 ` Matthew Garrett [this message]
2011-11-11 13:09 ` Matthew Garrett
2011-11-11 14:15 ` James Bottomley
2011-11-11 14:20 ` Mark Salyzyn
2011-11-11 14:41 ` James Bottomley
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=20111111135300.GA10798@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=aacraid@adaptec.com \
--cc=jbottomley@parallels.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mark_salyzyn@us.xyratex.com \
--cc=shaohua.li@intel.com \
--cc=vvs@parallels.com \
/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