Alan/Jeff/Mark,Is there anything else I can do to further troubleshoot this problem now that we have the failed opcode(s)? Again, there is never any corruption on these drives, so it is more of an annoyance than anything else.
Other people also have this problem with these drives if you search Google but I am not sure they are aware of where to report their errors/problems.
opcode=0x35 & opcode=0xca Justin. - 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.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: Alan Cox <[email protected]>
- Re: LibPATA code issues / 2.6.17.3 (What is the next step?)
- 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]>
- Re: LibPATA code issues / 2.6.15.4
- Prev by Date: Re: [PATCH 00/10] Kernel memory leak detector 0.8
- Next by Date: RE: [discuss] Re: [PATCH] Allow all Opteron processors to change pstate at same time
- Previous by thread: Re: Follow up? LibPATA code issues / 2.6.15.4 (found the opcode=0x35)!
- Next by thread: Re: LibPATA code issues / 2.6.17.3 (What is the next step?)
- Index(es):