On 3/1/06, Jeff Garzik <jgarzik@xxxxxxxxx> wrote: > Eric D. Mudama wrote: > > On 3/1/06, Jeff Garzik <jgarzik@xxxxxxxxx> wrote: > > > >>This also begs the question... what controller was being used, when the > >>single Maxtor device listed in the blacklist was added? Perhaps it was > >>a problem with the controller, not the device. > >> > >> Jeff > > > > > > As reported here: > > > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=177951 > > > > the controller was a 3114, and the bug was "fixed" by blacklisting his > > Maxtor drive's FUA support. I'd like Maxtor drives to be > > un-blacklisted if possible. > > If its 3114 I agree un-blacklisting is the way to go... but its not > clear to me whether the problematic configuration included sata_sil or > sata_nv. Since I'm apparently blind :) which part of the bug points > conclusively to sata_sil? > > Jeff The "failing dmesg" has the plextor connected to sata_nv, and the two Maxtor drives connected to sata_sil, if I read it correctly. They're ata5/ata6 ports, mapped as sda/sdb. Nicolas' comment in the thread "Re: LibPATA code issues / 2.6.15.4" seemed to say it was the same adapter: http://marc.theaimsgroup.com/?l=linux-kernel&m=114123989405668&w=2 --eric - : 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
