Tzachi Dar wrote: > I'll try to test it with the wix installer next week and see if it > still happens.
If a BOOT_START version of the HCA driver has been installed, regardless of how, the install will not require a reboot. > > By the way can you try a manual install of the driver and see if you > still need a reboot? Will do. > >> "The forced reboot occurs on the 1st time a BOOT_START driver is >> loaded." > > what do you mean by that? Let's look at the following sequence: > 1) Install (and reboot) > 2) uninstall. > 3) install again: > > Will the install again force a reboot? No, only occurs after the 1st install. > > Another question is this, after the first install does the driver load > OK? If it does than the mlx4_hca and ipoib will also load and the boot > process has finished completely, but if it doesn't than the install > will only finish after the boot (which is even more ugly). I believe the HCA & IPoIB drivers are up and functioning correctly prior to the reboot. The problem with validating this reboot behavior is it requires a re-install of Windows in order to get the behavior. Hugely time consuming. > > Thanks > Tzachi > > > > > -----Original Message----- > From: Smith, Stan [mailto:[email protected]] > Sent: Thursday, December 17, 2009 7:24 PM > To: Tzachi Dar; [email protected] > Subject: RE: [ofw] [ANNOUNCE] WinOF 2.2 RC0 available > > Hello, > Comments inline. > > > Tzachi Dar wrote: >> I must say that we haven't seen this on our systems. > > Are you using the WinOF 2.2 RC0 installer? > >> >> You are talking about the changes to the mlx4_bus and mlx4_hca right? > > I have tracked the issue down to the change of start_type from > DEMAND_START to BOOT_START in mthca.inf & mlx4_hca.inf. > >> >> Does it always happen or does it only happen after the first install >> on the machine? > > The forced reboot occurs on the 1st time a BOOT_START driver is > loaded. Once Windows has loaded/unloaded the driver, subsequent loads > do not require a system reboot after driver load. > My guess is a registry entry Ids the BOOT_START driver although I > could not find a specific reg entry which contained BOOT_START and > the HCA driver name? > >> >> Can that be related to the fact that you have replaced the WDK >> version > >> (which changes WDF version as a side affect)? > > Possible but doubtful as I was building & installing with the newer > WDK version prior to the BOOT_START .inf changes and did not see this > reboot behavior. > > It is possible this is an artifact of newer Windows installer versions > and their behavior being driven by WIX3, although there is no specific > WIX3 code which forces a reboot. > > From a 10,000 foot view, rebooting after installing a BOOT_START > driver install does make some sense if indeed the driver could be > used to boot from. > What I do know, is that something below the WIX3 install level (my > guess is PNP) has decided the system needs a reboot after installing a > BOOT_START driver. > By the time control returns to the Windows installer from loading the > driver store and PNP checking for a driver store VEN/DEV ID match to > install, the installer property FORCEREBOOT has been set; consequently > the Windows installer sez OK and forces the reboot. > Reset start_type from BOOT_START to DEMAND_SART and the behavior does > not occur. > > Stan. > >> >> Thanks >> Tzachi >> >> >>> **** Known Issues **** >>> >>> HCA drivers are reclassified as BOOT_START drivers to support >>> booting > >>> from an SRP IOC. An unfortunate side-effect is when WinOF 2.2 is >>> installed on a system for the first time, after installation a >>> mandatory reboot is Required by Windows. _______________________________________________ ofw mailing list [email protected] http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw
