Re: ndtest.exe hangs when doing 1c_InitTIme variation 11 (HCT 11.2)

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Mitesh Desai [MSFT] (miteshd_at_online.microsoft.com)
Date: 09/04/04

  • Next message: Jonathan Morrison [MSFT]: "Re: When KeEnterCriticalRegion ?" 
    Date: Fri, 3 Sep 2004 18:38:44 -0700

    I could not spot anything wrong with the log. I cannot think of anything
    else to suggest.

    Mitesh 

    -- 
This posting is provided "AS IS" with no warranties, and confers no rights.
"RonM" <doldrum@post.com> wrote in message
news:OLgZZ%23ekEHA.3536@TK2MSFTNGP12.phx.gbl...
> I just looked at setupapi.log and wow I never knew that file existed!
> I have a snippet of the install of our driver and there are problems
> but I do not understand all the lines and lines of info. I will attach
> a txt file with the snippet of our install. Maybe you can spot something.
> There are complaints about "unsigned" (yes we are working on it)
> and "no default" (this is truly a new device) I don't understand much
else.
> -Ron-
>
> "Mitesh Desai [MSFT]" <miteshd@online.microsoft.com> wrote in message
> news:uOJq$JekEHA.3556@TK2MSFTNGP12.phx.gbl...
> > RemoveSubTree succeeded prints after control returns from the PNP api
NDTest
> > uses to disable your adapter (and DN_DRIVER_LOADED, etc is just before
the
> > API call) The hang there is consistent with the (short) hang that you
get
> > when you disable through device manager. It doesnt give us more
information.
> >
> > Have you looked at the %WINDIR%\setupapi.log to see if there is more
> > information in there?
> >
> > Mitesh
> > -- 
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "RonM" <doldrum@post.com> wrote in message
> > news:ecCQKzVkEHA.3152@TK2MSFTNGP12.phx.gbl...
> > > We ran a commercial card through 1c_InitTime and kept the log.
> > > I can see where the other card passes and we hang. It is in
> > > variation 11. Here is a snippet of the log file 1c_InitTime.htm.
> > >
> > > ==== begin snip ====
> > >
> > > StopDriver
> > > DriverName = {B20AE927-6B73-47FC-BD8C-C8C8FF6EC92E}
> > >
> > > Devnode status = 0x00000000
> > >
> > > DN_DRIVER_LOADED
> > >
> > > DN_STARTED
> > >
> > > DN_DISABLEABLE
> > >
> > > DN_NT_ENUMERATOR
> > >
> > > DN_NT_DRIVER
> > >
> > > <------ We hang here
> > > <------ Other card continues
> > > RemoveSubTree succeeded
> > >
> > > ==== end snip ===
> > >
> > > So what is this "RemoveSubTree "?
> > > Like I mentioned before our driver exits halt and the Device Manager
> > > GUI hangs for 30 seconds before displaying our device as disabled.
> > > And here we get started in some "RemoveSubTree " whatever that
> > > is and NDTEST.EXE hangs permanently. We are causing something
> > > and in NDTEST it has something to do with "RemoveSubTree "
> > > after STOPDRIVER.
> > > Does this help any?
> > >
> > >
> > > "Mitesh Desai [MSFT]" <miteshd@online.microsoft.com> wrote in message
> > > news:OE$FtsEkEHA.1996@TK2MSFTNGP09.phx.gbl...
> > > > Unfortunately I cant think of anything else that maybe causing this.
> > Some OS
> > > > component is probably waiting for an event. Unless we know which
> > component
> > > > is waiting, it would be very difficult to figure out what is
happening.
> > > >
> > > > Have you tried simplifying your inf file to the bare minimum to see
if
> > maybe
> > > > something is wrong in there? If the delay happens after the driver
has
> > > > halted it could also be because of a support component like inf,
> > > > coinstaller, etc.
> > > >
> > > > Mitesh
> > > > -- 
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > >
> > > >
> > > > "RonM" <doldrum@post.com> wrote in message
> > > > news:O$jVUkrjEHA.2412@TK2MSFTNGP15.phx.gbl...
> > > > > Yikes! That sounds rather intimidating! I'm having enough
challenge
> > > > forward engineering
> > > > > our driver. I'm not really ready to reverse engineer Windows!
> > > > >
> > > > > "Mitesh Desai [MSFT]" <miteshd@online.microsoft.com> wrote in
message
> > > > > news:OOayqI9iEHA.1432@TK2MSFTNGP09.phx.gbl...
> > > > > > When the 1c_InitTime script is stuck can you break into the
debugger
> > to
> > > > try
> > > > > > and find what the test is stuck waiting for (looking at all
stacks
> > in
> > > > the
> > > > > > process)? The test runs in a wscript.exe process. Also look at
the
> > > > system
> > > > > > process to see if there is any networking thread stuck.
> > > > > >
> > > > > > Mitesh
> > > > > > -- 
> > > > > > This posting is provided "AS IS" with no warranties, and confers
no
> > > > rights.
> > > > > >
> > > > > > "RonM" <doldrum@post.com> wrote in message
> > > > > > news:%23HfX8b8iEHA.4044@tk2msftngp13.phx.gbl...
> > > > > > > >>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: Jonathan Morrison [MSFT]: "Re: When KeEnterCriticalRegion ?"

    Relevant Pages