Mark Lord wrote:
Justin Piszcz wrote:Using 2.6.16-rc5-git4 and removing a directory of around 5.0GB of files while streaming a 1MB/s video stream on another (SATA disk), the I/O seemed to freeze up for a moment and I got this error:[4342671.839000] ata1: command 0x35 timeout, stat 0x50 host_stat 0x22 Only 1 in dmesg, any idea what causes this error?The drive it occured on was a 74GB raptor on an ICH5 controller. [4294673.245000] Vendor: ATA Model: WDC WD740GD-00FL Rev: 33.00000:00:1f.2 IDE interface: Intel Corporation 82801EB (ICH5) SATA Controller (rev 02)SCSI opcode 0x35 is SYNCHRONIZE_CACHE.
Oh, wait a sec.. on that path, libata actually does show the ATA opcode, which would have been WRITE_DMA_EXT. Not an FUA command. Dunno what it's complaining about, though. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: LibPATA code issues / 2.6.15.4
- From: Justin Piszcz <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- References:
- LibPATA code issues / 2.6.15.4
- From: Justin Piszcz <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: David Greaves <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Justin Piszcz <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Mark Lord <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: David Greaves <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Mark Lord <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Justin Piszcz <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Mark Lord <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: David Greaves <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Mark Lord <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: David Greaves <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Mark Lord <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Mark Lord <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Tejun Heo <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Mark Lord <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: David Greaves <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Mark Lord <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Jeff Garzik <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: David Greaves <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Mark Lord <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: David Greaves <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Mark Lord <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: David Greaves <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: David Greaves <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Justin Piszcz <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Justin Piszcz <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Mark Lord <[email protected]>
- LibPATA code issues / 2.6.15.4
- Prev by Date: Re: LibPATA code issues / 2.6.15.4
- Next by Date: Readahead value 128K? (was Re: Drastic Slowdown of 'fseek()' Calls From 2.4 to 2.6 -- VMM Change?)
- Previous by thread: Re: LibPATA code issues / 2.6.15.4
- Next by thread: Re: LibPATA code issues / 2.6.15.4
- Index(es):