When enabling the driver verifier and rebooting the machine (done
automatically for some tests by DTM), the machine is hanging during the
reboot. I can reproduce the problem also by doing the same thing manually
(without DTM). I have Windbg attached and it seems the system is hanging at
the very beginning: it seems the driver under test is not loaded yet, the
last messages from windbg are "kernel debugger connection established", some
stuff about symbol paths and "system uptime: not available" as last message.
I'm only able to break into the debugger until after a very long time (more
than 10 minutes). The strange thing is that I do not see the problem on all
my test machines. I'm currently using 2 machines: the one which has the
problem is a single-processor machine, the other one, which is a
multi-processor machine, does not have the problem. Another difference
between them is that the one with the problem has both XP and Vista installed
on it while the other has only Vista installed. Both are 32-bit machines.
Has anybody already seen this problem before or does anybody have
suggestions to debug this problem?

Thanks,
Jeroen

Re: machine hanging after reboot when enabling driver verifier by Don

Don
Fri Feb 02 10:24:23 CST 2007

Does WinDBG think it should set any breakpoints? The latest WinDBG can
slow down computers by 3 orders of magnitude in some cases when a
breakpoint is set that is inappropriate (sorry to be vague, I am still
trying to understand this myself).


--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
http://www.windrvr.com
Remove StopSpam from the email to reply



"Jeroen" <Jeroen@discussions.microsoft.com> wrote in message
news:9AD61D03-0AE9-40D7-A62B-2CFA51249FF1@microsoft.com...
> When enabling the driver verifier and rebooting the machine (done
> automatically for some tests by DTM), the machine is hanging during the
> reboot. I can reproduce the problem also by doing the same thing manually
> (without DTM). I have Windbg attached and it seems the system is hanging
> at
> the very beginning: it seems the driver under test is not loaded yet, the
> last messages from windbg are "kernel debugger connection established",
> some
> stuff about symbol paths and "system uptime: not available" as last
> message.
> I'm only able to break into the debugger until after a very long time
> (more
> than 10 minutes). The strange thing is that I do not see the problem on
> all
> my test machines. I'm currently using 2 machines: the one which has the
> problem is a single-processor machine, the other one, which is a
> multi-processor machine, does not have the problem. Another difference
> between them is that the one with the problem has both XP and Vista
> installed
> on it while the other has only Vista installed. Both are 32-bit machines.
> Has anybody already seen this problem before or does anybody have
> suggestions to debug this problem?
>
> Thanks,
> Jeroen



Re: machine hanging after reboot when enabling driver verifier by Jeroen

Jeroen
Fri Feb 02 10:38:01 CST 2007

Well, the breakpoint list is empty (using the "bl" command), so I guess not.
When I don't attach the debugger, I see the same problem.

"Don Burn" wrote:

> Does WinDBG think it should set any breakpoints? The latest WinDBG can
> slow down computers by 3 orders of magnitude in some cases when a
> breakpoint is set that is inappropriate (sorry to be vague, I am still
> trying to understand this myself).
>
>
> --
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> http://www.windrvr.com
> Remove StopSpam from the email to reply
>
>
>
> "Jeroen" <Jeroen@discussions.microsoft.com> wrote in message
> news:9AD61D03-0AE9-40D7-A62B-2CFA51249FF1@microsoft.com...
> > When enabling the driver verifier and rebooting the machine (done
> > automatically for some tests by DTM), the machine is hanging during the
> > reboot. I can reproduce the problem also by doing the same thing manually
> > (without DTM). I have Windbg attached and it seems the system is hanging
> > at
> > the very beginning: it seems the driver under test is not loaded yet, the
> > last messages from windbg are "kernel debugger connection established",
> > some
> > stuff about symbol paths and "system uptime: not available" as last
> > message.
> > I'm only able to break into the debugger until after a very long time
> > (more
> > than 10 minutes). The strange thing is that I do not see the problem on
> > all
> > my test machines. I'm currently using 2 machines: the one which has the
> > problem is a single-processor machine, the other one, which is a
> > multi-processor machine, does not have the problem. Another difference
> > between them is that the one with the problem has both XP and Vista
> > installed
> > on it while the other has only Vista installed. Both are 32-bit machines.
> > Has anybody already seen this problem before or does anybody have
> > suggestions to debug this problem?
> >
> > Thanks,
> > Jeroen
>
>
>