From: Jeff Garzik <jeff@garzik.org>
To: gshan <gshan@alcatel-lucent.com>
Cc: linux-kernel@vger.kernel.org,
Linux IDE mailing list <linux-ide@vger.kernel.org>
Subject: Re: PIIX4: DMA timeout issue
Date: Tue, 29 Jul 2008 09:34:36 -0400 [thread overview]
Message-ID: <488F1C6C.9000002@garzik.org> (raw)
In-Reply-To: <488ED837.2060509@alcatel-lucent.com>
gshan wrote:
> Hello, I sent mails on this issue before, but nobody made response.
> There are 2 types of board for me. The hardware configuration for
> those 2 boards are almost same except that one of them has 100GB
> harddisk, and another type of board has 60GB harddisk. All harddisk
> was access through PIIX4. I found this issue on board with 60GB
> disk, but can't reproduce it on that with 100GB disk.
>
> When I uncompressed a large file (600MB) to a logic partition with 8GB
> size, following errors was report on middle way (5 minutes about from
> start).
> Anybody has ideas?
>
> hdc: dma_timer_expiry: dma status == 0x21
> hdc: DMA timeout error
> hdc: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest }
> ide: failed opcode was: unknown
> hdc: DMA disabled
> ide1: reset: success
Can you try disabling the IDE driver (CONFIG_IDE) and enabling the newer
libata driver? (CONFIG_ATA)
Jeff
next prev parent reply other threads:[~2008-07-29 13:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 8:43 PIIX4: DMA timeout issue gshan
2008-07-29 13:34 ` Jeff Garzik [this message]
[not found] ` <200807291713.29580.bzolnier@gmail.com>
2008-07-30 0:57 ` gshan
2008-07-30 19:43 ` Bartlomiej Zolnierkiewicz
2008-07-31 1:00 ` gshan
2008-07-30 0:58 ` gshan
2008-07-30 9:04 ` gshan
2008-07-30 10:49 ` Alan Cox
2008-07-31 4:30 ` gshan
2008-08-01 7:43 ` Tejun Heo
2008-08-01 8:38 ` gshan
2008-08-01 8:54 ` gshan
2008-08-03 14:10 ` Gavin Shan
2008-08-03 14:10 ` Gavin Shan
2008-08-05 3:41 ` gshan
2008-10-24 6:09 ` gshan
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=488F1C6C.9000002@garzik.org \
--to=jeff@garzik.org \
--cc=gshan@alcatel-lucent.com \
--cc=linux-ide@vger.kernel.org \
--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 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.