On Sunday, August 07, 2005 8:30 AM, James Bottomley wrote: > On Sun, 2005-08-07 at 05:59 +0000, Holger Kiehl wrote: > > Thanks, removing those it compiles fine. This patch also > solves my problem, > > here the output of dmesg: > > Well ... the transport class was supposed to help diagnose the problem > rather than fix it. > > However, what it shows is that the original problem is in the fusion > internal domain validation somewhere, but that we still don't know > where... > > James > I was corresponding to Mr Holger Hiehl in private email. What I understood the problem to be was when he compiled the drivers into the kernel, instead of as modules, we would get some drives negotiating as asyn narrow on the 2nd channel. What I was trying to do was reproduce the issue here, and I was unable to. Has Mr Holger Hiehl tried compiling your patch with the drivers compiled statically into the kernel, instead of modules? Anyways - My last suggesting was that he change the scsi cable, and reset the parameters in the bios configuration utility. I don't believe that fixed it. Here's my next suggestion. Recompile the driver with domain validation debugging enabled. Then send me the output dmesg so I can analyze it. That is done by modifying the driver makefile, adding the following lines: CFLAGS_mptscsih.o += DMPT_DEBUG_DV CFLAGS_mptscsih.o += DMPT_DEBUG_NEGO - : 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
