Re: ndtest.exe hangs when doing 1c_InitTIme variation 11 (HCT 11.2)
From: RonM (doldrum_at_post.com)
Date: 08/26/04
- Next message: Mitesh Desai [MSFT]: "Re: Help:XP HCT11.2 NDIS WHQLConfigCheck.wsf different PCI bus Failed"
- Previous message: Robby Tanner: "Serial.sys"
- In reply to: Mitesh Desai [MSFT]: "Re: ndtest.exe hangs when doing 1c_InitTIme variation 11 (HCT 11.2)"
- Next in thread: Mitesh Desai [MSFT]: "Re: ndtest.exe hangs when doing 1c_InitTIme variation 11 (HCT 11.2)"
- Reply: Mitesh Desai [MSFT]: "Re: ndtest.exe hangs when doing 1c_InitTIme variation 11 (HCT 11.2)"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 26 Aug 2004 16:47:00 -0700
>>1. Have you tried this on a fresh OS install (clean install)? Maybe
registry
>>is left in a bad state and causing this?
Yes We have ghost images of XP-plain, XP-SP1, XP-checked
I understand as re-ghosting has cured problems in the past.
>>2. Are there any entries in the event viewer that suggest what is wrong?
I saw nothing interesting
>>3. Can you check the registry key at:
>>HKLM\SYSTEM\CurrentControlSet\Control\Network\{4D36E972-E325-11CE-BFC1-080
02
>>BE10318} to see if everything looks okay & all network cards on your
machine
We show up like other wireless cardbus cards
>>4. Is there any kind of user mode application (eg. wireless connectivity
>>monitoring application) running?
We don't turn that on for NDTEST.exe as NDTEST runs the show.
Also just running on XP I have plugged in the card, NOT run our APP,
therefore
not associated with any access point and just did the remove card and still
got the 30 second
delay before Device Manager screen updates.
>>5. Besides the halt taking too long, does everything else work ok (Do you
>>get an IP address)?
Well, NDTEST hangs while running 1c_InitTime variation 11 so we can't pass
WHQL
but yes we can ping and web browse and FTP and download movie trailers etc.
"Mitesh Desai [MSFT]" <miteshd@online.microsoft.com> wrote in message
news:eSa58sxiEHA.1432@TK2MSFTNGP09.phx.gbl...
> I cant think of anything obvious that maybe causing this. Some questions
for
> you:
>
> 1. Have you tried this on a fresh OS install (clean install)? Maybe
registry
> is left in a bad state and causing this?
> 2. Are there any entries in the event viewer that suggest what is wrong?
> 3. Can you check the registry key at:
>
HKLM\SYSTEM\CurrentControlSet\Control\Network\{4D36E972-E325-11CE-BFC1-08002
> BE10318} to see if everything looks okay & all network cards on your
machine
> show up there? Do you remember if the {E6C25F2E... GUID from below
belonged
> to your adapter or?
> 4. Is there any kind of user mode application (eg. wireless connectivity
> monitoring application) running?
> 5. Besides the halt taking too long, does everything else work ok (Do you
> get an IP address)?
>
> Mitesh
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "RonM" <doldrum@post.com> wrote in message
> news:%23PJdUktiEHA.3416@TK2MSFTNGP09.phx.gbl...
> > Yes I saw the halt called and watched it deallocate memory interrupt
etc.
> > and I saw it exit. The reason that I am specifically running 1c_InitTime
> is
> > that when running with XP when we try to remove the device we also see
> > the halt enter and exit and then the OS or NDIS delays 30 seconds before
> > updating the Device Manager screen. After the 30 second delay I get this
> > printout in debugview:
> > 00000377 35.79937310 [792] NETCFG *ERROR*: HrPnpInstanceIdFromGuid
failed
> > getting id for {E6C25F2E-88FC-441D-B26A-D9F564EB1156} [The system cannot
> > find the file specified.] Win32=2,0x00000002 hr=0x80070002
> > File:d:\xpsp1\net\config\common\nclan\lancmn.cpp,619:
> > 00000378 35.79979467 [792] NETCFG *ERROR*: HrGetPnpDeviceStatus [The
> system
> > cannot find the file specified.] Win32=2,0x00000002 hr=0x80070002
> > File:d:\xpsp1\net\config\common\nclan\lancmn.cpp,685
> > 00000379 35.90013982 [792] NETCFG *ERROR*: LanEventWorkItem [The system
> > cannot find the file specified.] Win32=2,0x00000002 hr=0x80070002
> > File:d:\xpsp1\net\config\netman\conman\event.cpp,285:
> > Which seems to be why the delay happened but I have no clue what it
means.
> > I agree that it is our driver that causes the 30 second delay, but I
don't
> > know why.
> > I am sure that whatever our driver is doing to cause the 30 second delay
> is
> > also responsible for the ndtest.exe hang, but again I am looking for
clues
> > as to
> > what we are doing wrong. We ran the checked build to get the above error
> > messages
> > but NDIS specifically did not print out any info.
> >
> > "Mitesh Desai [MSFT]" <miteshd@online.microsoft.com> wrote in message
> > news:uZl4qNtiEHA.3928@TK2MSFTNGP11.phx.gbl...
> > > The Stop driver spew is written when NDISTest is trying to Halt your
> > > miniport. Most likely the script has called the OS to disable your
> > miniport
> > > and the OS hasnt returned. Do you have a debugger attached so you can
> > check
> > > if the miniport halt was called and if the halt returned?
> > >
> > > Mitesh
> > > --
> > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > >
> > >
> > > "RonM" <doldrum@post.com> wrote in message
> > > news:umjrLxsiEHA.2696@TK2MSFTNGP11.phx.gbl...
> > > > Yes I caught the popup window. That happened in variation 10. I got
a
> > > > legitimate error that our driver reported that it was still
associated
> > > even
> > > > when we followed the popup instruction and unplugged the access
point.
> > > > I looked in the log and ndtest printed a few things pertaining to
> > > variation
> > > > 11 and just sat there for 16 hours. The rest of the system was not
> hung,
> > > > just the app. Clicking on abort tests had no effect. The last thing
in
> > the
> > > > log is:
> > > >
> > > > StopDriver
> > > > DriverName = {E22F6B05-C441-4261-9490-02BEDD5F6CAC}
> > > >
> > > > Devnode status = 0x00000000
> > > >
> > > > DN_DRIVER_LOADED
> > > >
> > > > DN_STARTED
> > > >
> > > > DN_DISABLEABLE
> > > >
> > > > DN_REMOVABLE
> > > >
> > > > DN_NT_ENUMERATOR
> > > >
> > > > DN_NT_DRIVER
> > > >
> > > >
> > > > "Mitesh Desai [MSFT]" <miteshd@online.microsoft.com> wrote in
message
> > > > news:OPfBsQsiEHA.3564@TK2MSFTNGP10.phx.gbl...
> > > > > Can you do an ALT+Tab to check if there are any popup windows.
> > > 1c_InitTime
> > > > > throws a couple of popups asking the user to unplug/replug the
cable
> > (or
> > > > > power off/power on the AP). Sometimes these popups go behind the
> > > > ndtest.exe
> > > > > window giving the appearance of the app being hung.
> > > > >
> > > > > Mitesh
> > > > > --
> > > > > This posting is provided "AS IS" with no warranties, and confers
no
> > > > rights.
> > > > >
> > > > > "RonM" <doldrum@post.com> wrote in message
> > > > > news:%23xGvPPiiEHA.4020@TK2MSFTNGP10.phx.gbl...
> > > > > > I let it sit there over night and the app is just hung. It's
kinda
> > > hard
> > > > > > to get an idea of what is wrong with our driver because I get no
> > > > > > error or timeout etc. Our driver had two failures before this
> > > > > > particular test which may contribute to the problem.
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
- Next message: Mitesh Desai [MSFT]: "Re: Help:XP HCT11.2 NDIS WHQLConfigCheck.wsf different PCI bus Failed"
- Previous message: Robby Tanner: "Serial.sys"
- In reply to: Mitesh Desai [MSFT]: "Re: ndtest.exe hangs when doing 1c_InitTIme variation 11 (HCT 11.2)"
- Next in thread: Mitesh Desai [MSFT]: "Re: ndtest.exe hangs when doing 1c_InitTIme variation 11 (HCT 11.2)"
- Reply: Mitesh Desai [MSFT]: "Re: ndtest.exe hangs when doing 1c_InitTIme variation 11 (HCT 11.2)"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
