From: "Mao Rui" <maorui@yuvad.com>
To: <linux-kernel@vger.kernel.org>
Subject: SATA DOM is not identified by ata_piix module
Date: Tue, 15 Jan 2008 18:11:25 +0800 [thread overview]
Message-ID: <003a01c8575f$070d2230$7740a8c0@cmaorui2> (raw)
Hi,
I have a PQI Turbo SATA DOM. It works well under Windows. I installed it in
a SuperMicro motherboard, Intel 5000P chipset. The OS is Ubuntu 7.04, kernel
2.6.20-15. But the DOM is not appeared as a device node, and I found several
error messages in kernel log.
[ 67.124299] ata2.00: qc timeout (cmd 0x91)
[ 67.124306] ata2.00: failed to IDENTIFY (INIT_DEV_PARAMS failed,
err_mask=0x4)
[ 67.124309] ata2: failed to recover some devices, retrying in 5 secs
[ 102.258334] ata2.00: qc timeout (cmd 0x91)
[ 102.258341] ata2.00: failed to IDENTIFY (INIT_DEV_PARAMS failed,
err_mask=0x4)
[ 102.258344] ata2: failed to recover some devices, retrying in 5 secs
[ 137.392654] ata2.00: qc timeout (cmd 0x91)
[ 137.392661] ata2.00: failed to IDENTIFY (INIT_DEV_PARAMS failed,
err_mask=0x4)
Actually I also have a PQI IDE DOM, it have same error with Ubuntu 7.04 /
kernel 2.6.20-15. After I upgrade kernel to 2.6.22, the IDE DOM can work.
But as for SATA DOM, I have no luck this time. Even with the newest kernel,
2.6.23.14 and 2.6.24-rc7-git6, the problem still exists.
I also found an interesting matter. The Ubuntu 6.10, say kernel 2.6.15-28,
can identify both IDE DOM and SATA DOM. But due to other critical problem, I
can not go back to this old kernel.
Whats going on? The new kernel is even worse than old one. It seems the
problem is existing in the ata_piix driver.
Best regards,
Mao Rui
next reply other threads:[~2008-01-15 10:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 10:11 Mao Rui [this message]
2008-01-15 11:02 ` Alan Cox
2008-01-18 6:11 ` Mao Rui
2008-01-30 2:42 ` Mao Rui
2008-02-04 13:00 ` Alan Cox
2008-02-02 8:41 ` Tejun Heo
2008-02-02 9:25 ` Mao Rui
2008-02-02 11:20 ` Tejun Heo
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='003a01c8575f$070d2230$7740a8c0@cmaorui2' \
--to=maorui@yuvad.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
Powered by JetHome