From: Tejun Heo <htejun@gmail.com>
To: Mao Rui <maorui@yuvad.com>
Cc: "'Alan Cox'" <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: SATA DOM is not identified by ata_piix module
Date: Sat, 02 Feb 2008 20:20:06 +0900 [thread overview]
Message-ID: <47A451E6.5030305@gmail.com> (raw)
In-Reply-To: <001e01c8657d$8c839490$7740a8c0@cmaorui2>
Mao Rui wrote:
> Hi,
>
> No difference... :-(
>
> Here is the log.
>
> [ 26.729011] scsi0 : ata_piix
> [ 26.729067] scsi1 : ata_piix
> [ 26.729095] ata1: SATA max UDMA/133 cmd 0x1880 ctl 0x1874 bmdma 0x1860
> irq 18
> [ 26.729097] ata2: SATA max UDMA/133 cmd 0x1878 ctl 0x1870 bmdma 0x1868
> irq 18
> [ 26.894043] ata1.00: ATA-6: WDC WD2500SD-01KCB0, 08.02D08, max UDMA/133
> [ 26.894046] ata1.00: 488397168 sectors, multi 16: LBA48
> [ 26.910218] ata1.00: configured for UDMA/133
> [ 57.043651] ata2.00: qc timeout (cmd 0x91)
> [ 57.043656] ata2.00: failed to IDENTIFY (INIT_DEV_PARAMS failed,
> err_mask=0x4)
> [ 57.043659] ata2: failed to recover some devices, retrying in 5 secs
> [ 92.177684] ata2.00: qc timeout (cmd 0x91)
> [ 92.177688] ata2.00: failed to IDENTIFY (INIT_DEV_PARAMS failed,
> err_mask=0x4)
Ah.. Timeout. Hmmm... Interesting. Maybe the device just should be
blacklisted such that INIT_DEV_PARAMS is not issued. Can you please
just comment out the INIT_DEV_PARAMS block and see how it works and post
full boot log?
--
tejun
prev parent reply other threads:[~2008-02-02 11:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 10:11 SATA DOM is not identified by ata_piix module Mao Rui
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 [this message]
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=47A451E6.5030305@gmail.com \
--to=htejun@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=maorui@yuvad.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