At this point it safe to say that it was a cable related issue. I swapped it to be sure and i haven't had issues since. Sincerely, Maarten Maathuis. On 9/5/07, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote: > > On Tue, 28 Aug 2007 16:06:41 +0200 "Maarten Maathuis" <madman2003@xxxxxxxxx> wrote: > > I have not had any issues, i swapped the cable because a while ago i > > had to check the connection of the drive after the bios failed to > > detect the drive. That is why i considered that a posibility. Kernel > > 2.6.18 does not have NCQ support for nvidia chipsets, so that cannot > > be it. > > > > Maarten. > > > > On 8/28/07, Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx> wrote: > > > > > > On Aug 25 2007 15:37, Maarten Maathuis wrote: > > > > > > > >A broken cable seems like a realistic possibility, so i swapped it for > > > >another cable. I will try if that solves the problem. > > > > > > Hi, did you have any success/failure, other updates? > > > I am facing a similar problem (just posted to linux-ide@xxxxxxxxxxxxxxx), > > > but also with 2.6.18, and it does not look like an NCQ or loose cable problem (got a > > > backplane, and sda is working normal). > > > > > This is a rather comedic email thread, with people top-posting, others > leaving others off the cc list, Robert's MUA reliably and inexplicably > mangling both In-Reply-To: and References: thus breaking threading, no > visible sign of how Jan got involved and no linux-ide cc's. > > Enough time has passed for everyone to forget all about this. So Maarten, > if you still believe that this is still a kernel bug then please update us > on its status and provide a full description for linux-ide.. Please use > reply-to-all for that. > > Thanks. > - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
