I have not tried to patch the 2.6.27-23 kernel. Given that the patches were against 31-RC1 I assumed that there would be other changes I would need to pull in. I have been looking at why the 31-RC1 was panicing as well as working with my EMC contacts to see if they already had a working 31-RC1 environment they could verify the patch in. Unfortunately I have been mostly in meetings... I will give it a try. I should have results in the morning. Eddie On Thu, 2009-07-09 at 12:55 -0700, Chandra Seetharaman wrote: > Did you try to port/apply my patches to the SLES11 tree and see if it > works ? > > On Tue, 2009-07-07 at 08:34 -0400, Eddie Williams wrote: > > I was testing with the SLES 11 kernel. Initially I was using > > 2.6.27.19-5 and also verified the same issue with their errata kernel > > 2.6.27.23-0.1. > > > > Eddie > > On Thu, 2009-07-02 at 13:47 -0700, Chandra Seetharaman wrote: > > > On Thu, 2009-07-02 at 16:29 -0400, Eddie Williams wrote: > > > > On Thu, 2009-07-02 at 15:34 -0400, Eddie Williams wrote: > > > > > I have tried to set this up but have run into a problem probably due to > > > > > my error. It has been a while since I have had to build kernels... > > > > > > > > > > I pulled 2.6.31-rc1, applied the two patches below and then applied the > > > > > 3 patches for the interface. The new kernel loads fine but when a > > > > > trespass command is sent I get an panic. I am looking though how I > > > > > built the kernel and perhaps build with your 3 patches to see if it > > > > > happened before. > > > > > > > > I backed out the 3 patches with the same panic. > > > > > > > Which version of the kernel were you originally testing with ? (when you > > > found the feature was gone). > > > > > > > -- > > To unsubscribe from this list: send the line "unsubscribe linux-scsi" in > > the body of a message to majordomo@xxxxxxxxxxxxxxx > > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
