On Fri, 14 Jul 2006, Mark Lord wrote:
Justin Piszcz wrote:They are Western Digital 400* drives. [4294678.049000] Vendor: ATA Model: WDC WD4000KD-00N Rev: 01.0 [4294678.050000] Vendor: ATA Model: WDC WD4000KD-00N Rev: 01.0On a SiL controller, it also happens when they are on a promise controller too.On Fri, 14 Jul 2006, Mark Lord wrote:Justin Piszcz wrote:opcode=0x35 & opcode=0xcaThose are non-DMA WRITE opcodes. Using PIO for I/O is pretty rare these days,so I'm betting that this is not a hard disk device -- compactflash?Okay. So why are we issuing PIO WRITE commands to drives that obviously should only be sent DMA commands by libata? Perhaps that's the bug.
Jeff/Alan -- ? Could this be it? - 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/
- References:
- Re: LibPATA code issues / 2.6.15.4
- From: Jeff Garzik <[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: Justin Piszcz <[email protected]>
- Re: LibPATA code issues / 2.6.15.4 (found the opcode=0x35)!
- From: Justin Piszcz <[email protected]>
- Re: LibPATA code issues / 2.6.15.4 (found the opcode=0x35)!
- From: Justin Piszcz <[email protected]>
- Re: LibPATA code issues / 2.6.15.4 (found the opcode=0x35)!
- From: Justin Piszcz <[email protected]>
- Re: LibPATA code issues / 2.6.15.4 (found the opcode=0x35)!
- From: Justin Piszcz <[email protected]>
- Follow up? LibPATA code issues / 2.6.15.4 (found the opcode=0x35)!
- From: Justin Piszcz <[email protected]>
- Re: Follow up? LibPATA code issues / 2.6.15.4 (found the opcode=0x35)!
- From: Alan Cox <[email protected]>
- Re: Follow up? LibPATA code issues / 2.6.15.4 (found the opcode=0x35)!
- From: Justin Piszcz <[email protected]>
- LibPATA code issues / 2.6.17.3 (What is the next step?)
- From: Justin Piszcz <[email protected]>
- Re: LibPATA code issues / 2.6.17.3 (What is the next step?)
- From: Mark Lord <[email protected]>
- Re: LibPATA code issues / 2.6.17.3 (What is the next step?)
- From: Justin Piszcz <[email protected]>
- Re: LibPATA code issues / 2.6.17.3 (What is the next step?)
- From: Mark Lord <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- Prev by Date: Re: Follow up? LibPATA code issues / 2.6.15.4 (found the opcode=0x35)!
- Next by Date: RE: Athlon64 + Nforce4 MCE panic
- Previous by thread: Re: LibPATA code issues / 2.6.17.3 (What is the next step?)
- Next by thread: Re: LibPATA code issues / 2.6.17.3 (What is the next step?)
- Index(es):