From: Tom Rini <tom.rini@gmail.com>
To: Shane Huang <shane.huang@amd.com>, linux-ide@vger.kernel.org
Cc: Aaron Lu <aaron.lwe@gmail.com>, Jeff Garzik <jgarzik@redhat.com>
Subject: BUG: 65fe1f0 (ahci: implement aggressive SATA...) fail to boot
Date: Sun, 21 Oct 2012 10:57:17 -0700 [thread overview]
Message-ID: <20121021175717.GA3543@bill-the-cat> (raw)
Hello,
I've got an Asus motherboard with:
00:11.0 SATA controller: Advanced Micro Devices [AMD] nee ATI
SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] (rev 40)
...
02:00.0 SCSI storage controller: OCZ Technology Group, Inc. RevoDrive 3
X2 PCI-Express SSD 240 GB (Marvell Controller) (rev 02)
And with 65fe1f0 merged I no longer see all devices on the RevoDrive.
Happy to provide whatever further information might be helpful.
--
Tom
next reply other threads:[~2012-10-21 17:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-21 17:57 Tom Rini [this message]
2012-10-22 4:52 ` 65fe1f0 (ahci: implement aggressive SATA...) fail to boot Huang, Shane
2012-10-25 0:15 ` Tom Rini
2012-10-25 0:25 ` Tom Rini
2012-12-24 8:10 ` Huang, Shane
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=20121021175717.GA3543@bill-the-cat \
--to=tom.rini@gmail.com \
--cc=aaron.lwe@gmail.com \
--cc=jgarzik@redhat.com \
--cc=linux-ide@vger.kernel.org \
--cc=shane.huang@amd.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