From: xulu on 7 Aug 2007 04:54 We have developed a virtual SCSI miniport driver, which has been working under 2k/xp/2k3. The problem occurs when we put it on some servers with SAS disks. There are two servers: S1: IBM server with Xeon CPU and 1GB RAM equipped; S2: AMD server with AMD 64 CPU and 4GB RAM equipped. Windows we have installed is Windows 2003(32bits). When we load our driver on both servers, the driver is unloaded immediately after findadapter is finished. On server S1, we modified AlignmentMask in ConfigurationInfo structure to 0x1 (0x3 was the original value), the problem on S1 is gone. On server S2, we took off 2GB RAM from the server, the problem is gone, and the driver runs very happily. If we add 2GB RAM back (now 4GB RAM in total), the problem comes back. We also tested the driver on servers without SAS disks running 2k3, it was no problem at all. We also run the driver on server S2 without using SAS disks running XP, it was no problem at all. From what we have collected, could you get some idea about the source of the problem? -- xulu ------------------------------------------------------------------------ Posted via http://www.codecomments.com ------------------------------------------------------------------------
From: Gary G. Little on 7 Aug 2007 10:24 Have you stepped into the driver with the debugger? Why is FindAdapter failing? -- The personal opinion of Gary G. Little "xulu" <xulu.2uxttw(a)mail.codecomments.com> wrote in message news:xulu.2uxttw(a)mail.codecomments.com... > > We have developed a virtual SCSI miniport driver, which has been working > under 2k/xp/2k3. The problem occurs when we put it on some servers with > SAS disks. > > There are two servers: > > S1: IBM server with Xeon CPU and 1GB RAM equipped; > S2: AMD server with AMD 64 CPU and 4GB RAM equipped. > > Windows we have installed is Windows 2003(32bits). > > When we load our driver on both servers, the driver is unloaded > immediately after findadapter is finished. > > On server S1, we modified AlignmentMask in ConfigurationInfo structure > to 0x1 (0x3 was the original value), the problem on S1 is gone. > > On server S2, we took off 2GB RAM from the server, the problem is gone, > and the driver runs very happily. If we add 2GB RAM back (now 4GB RAM in > total), the problem comes back. > > We also tested the driver on servers without SAS disks running 2k3, it > was no problem at all. > > We also run the driver on server S2 without using SAS disks running XP, > it was no problem at all. > > From what we have collected, could you get some idea about the source > of the problem? > > > > -- > xulu > ------------------------------------------------------------------------ > Posted via http://www.codecomments.com > ------------------------------------------------------------------------ >
|
Pages: 1 Prev: TDI and IPv6 Next: regarding the smart card reader driver not getting any IOCTL calls. |