From: Tejun Heo <htejun@gmail.com>
To: Harsha Padmanabha <harsha@purplevisiontech.com>
Cc: linux-ide@vger.kernel.org, jgarzik@pobox.com
Subject: Re: Sil 3512 and Seagate ST3802110AS
Date: Sat, 12 Aug 2006 00:59:57 +0900 [thread overview]
Message-ID: <44DCA97D.2070900@gmail.com> (raw)
In-Reply-To: <455FCE13-2A0E-4BBE-8D1B-45C02C3C1C69@purplevisiontech.com>
Harsha Padmanabha wrote:
> I am trying to get sata_sil running on a MPC8349(PPC) board, I runto the
> following errors. I cannot upgrade my kernel to the latest one since
> most of my changes for MPC8349 to work are for 2.6.11.
>
> 1) How can i patch the latest release of libata for 2.6.11 without
> having to change to 2.6.17
It's difficult. You'll have to update not only libata but also some
SCSI midlayer stuff too.
> 2) I have tried SIL 3112 card with the same results
> 3) I have also tried different hard drives like samsung and WDC
>
> Please let me know what i can do to get this running.
> sda:<3>ata_scsi_dump_cdb: CDB (2:0,0,0) 28 00 00 00 00 00 00 00 08
> ata_scsi_translate: ENTER
> ata_scsi_rw_xlat: ten-byte command
> ata_sg_setup: ENTER, ata2
> ata_sg_setup: 1 sg elements mapped
> ata_fill_sg: PRD[0] = (0x3748000, 0x1000)
> ata_dev_select: ENTER, ata2: device 0, wait 1
> ata_tf_load_mmio: hob: feat 0x0 nsect 0x0, lba 0x0 0x0 0x0
> ata_tf_load_mmio: feat 0x0 nsect 0x8 lba 0x0 0x0 0x0
> ata_tf_load_mmio: device 0xE0
> ata_exec_command_mmio: ata2: cmd 0x25
> ata_scsi_translate: EXIT
> ata_scsi_error: ENTER
> ata_eng_timeout: ENTER
> ata_qc_timeout: ENTER
> ata2: command 0x25 timeout, stat 0x58 host_stat 0x2
> ata_sg_clean: unmapping 1 sg elements
> ata2: status=0x58 { DriveReady SeekComplete DataRequest }
> SCSI error : <1 0 0 0> return code = 0x8000002
> sda: Current: sense key: Aborted Command
> Additional sense: Scsi parity error
> end_request: I/O error, dev sda, sector 0
> Buffer I/O error on device sda, logical block 0
> ata_qc_complete: EXIT
> ata_qc_timeout: EXIT
> ata_eng_timeout: EXIT
> ata_scsi_error: EXIT
Your first DMA command failed. IIRC, there was one errata fix which
fixes a possible controller lock up problem on 3512 and 3114 but it only
happens under relatively heavy IO and 3112 isn't affected, so I don't
think you're experiencing that.
At the first glance, your hw seems to have a problem w/ PCI bus
mastering. Does any other device live on the same bus - a NIC maybe?
If so, can it do DMA okay?
--
tejun
next prev parent reply other threads:[~2006-08-11 16:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-11 8:30 Sil 3512 and Seagate ST3802110AS Harsha Padmanabha
2006-08-11 10:04 ` Erik Mouw
2006-08-11 15:59 ` Tejun Heo [this message]
2006-08-11 16:28 ` Harsha Padmanabha
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=44DCA97D.2070900@gmail.com \
--to=htejun@gmail.com \
--cc=harsha@purplevisiontech.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.