On Mon, 16 Jul 2007 12:22:20 +0300 Boaz Harrosh wrote: > If you could do some testing it is grate. The first 3 patches do not > need scsi-misc specifically. Any post 2.6.20 tree will do. The last patch > could be done together with attached patch on any 2.6.22 tree. > (Apply attached patch anywhere before the last patch (4/4) of the patchset) > Though I do recommend scsi-misc tree. I took 2.6.22, backed out Christoph's aha152x.c patch (using completion for timeouts), added your 5 patches, and then tested. Does that sound OK? > Testing: > Doing a regular Mount, FS testing is good for checking the last (4/4) > patch, and it would be good news if it works, but ... > I'm afraid that it will not exercise the code change all that much, > since my patches touch the Error-handling and Reset code paths. > > Maybe someone can help: > How can we cause an ->eh_device_reset_handler() call from scsi-ml? > > As for the patch 3/4 we need a SAM_STAT_CHECK_CONDITION return > from a device. If you have a device with known bad sectors than > a dd over the bad block should exercise that. Again anyone can > think of an easy way to exercise a Status==SAM_STAT_CHECK_CONDITION? > > Thanks for any testing you can do. Even if it's only the first 3 > it could be nice I booted/tested 4 times. 2 Oopsen and 2 of could-never-mount-the-device-due-to-reset-problems. Log is attached. --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code ***
Attachment:
aha152xb.logs
Description: Binary data
