On Tuesday, August 07, 2012 10:11:01 AM Mike Tancsa wrote: > On 8/3/2012 5:26 PM, John Baldwin wrote: > >> If there's a tool for poking at the drives/controller, I would use > >> that, plus camcontrol. Of course you want a data intensive workload > > > > (iometer/iozone/xdd with async and sync mode, random reads and sequential > > reads, etc), and maybe resort to manual testing like pulling drives > > (power, data) if you don't mind creating failures. If you have some > > failed/failing drives kicking around, that would be a good test as well > > (see that all/some of the failure paths are properly stimulated). > > > > 3dm2 testing would be good for the ioctl handling, but the most critical > > tests are basic I/O. > > Looks like it breaks 3dm2 and the tw_cli. With the patch, I am not able > to see the 8006 controller I added.
Ugh, ok. A few questions: 1) Does the driver see any attached drives/volumes? 2) If it does, does basic I/O to the drives work? 3) Can you add some debugging printfs to twe_ioctl() to see what, if anything, fails in that routine when tw_cli makes a request? Thanks. -- John Baldwin _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
