Hi All,
I am checking my driver with the tool that comes with the ddk called driver verifier and pnp driver test.
when i am doing stress testing for pnp and then check the result of driver verifier its showing faults injected =3.
What that mean by faults injected.
in my case its 3 if there is any problem how can i determine where is the problem and how i should proceed for finding where the actual problem lies.
i will be very thankfull for your help.
Regards
Get the new Windows Live Messenger!
http://get.live.com/messenger/overview
nayan kumar wrote:
I am checking my driver with the tool that comes with the
ddk called driver verifier and pnp driver test.
when i am doing stress testing for pnp and then check the result of
driver verifier its showing faults injected =3.
What that mean by faults injected.
It means you turned on ALL of the options to driver verifier. When you
do that, Driver Verifier will randomly cause some of your memory
allocations to fail. In your case, it did that 3 times.
For ordinary testing, you can turn that off. However, you should be
congratulated that your driver survived that without crashing. You’re
ahead of the curve.
in my case its 3 if there is any problem how can i determine where is
the problem and how i should proceed for finding where the actual
problem lies.
It’s not a problem.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Hi Tim,
Thaks for the feedback.
But why windows put yellow mark on the driver .that we usually see when while installing driver it fails.
is it ok even if windows is showing the yellow mark after stress testing.
Regards
Search from any Web page with powerful protection. Get the FREE Windows Live Toolbar Today!
http://toolbar.live.com/?mkt=en-in
Successfully passing Driver Verifier, though a significant achievement,
makes not comment on installation in this regard. If you want your
driver to pass WHQL, then the installation issue will present a problem.
Otherwise, while it certainly would be better to fix it, if it is
doing what you wish, then so bet it.
I am confused, however, because it sounds like you’re saying your device
fails to install most of the time. If you’re interested in
investigating the problem, what’s the error code it gives you when
installation fails - 10, 31, et. c.? Also, after you perform the
installation, what does setuapi.log (\Windows) have to say about the
situation?
Good luck,
mm
nayan kumar wrote:
Hi Tim,
Thaks for the feedback.
But why windows put yellow mark on the driver .that we usually see when
while installing driver it fails.
is it ok even if windows is showing the yellow mark after stress testing.
Regards
Search from any Web page with powerful protection. Get the FREE Windows
Live Toolbar Today! Try it now! http:</http:>
nayan kumar wrote:
But why windows put yellow mark on the driver .that we usually see
when while installing driver it fails.
is it ok even if windows is showing the yellow mark after stress testing.
If you shut off the memory failure injection and you STILL see the
yellow mark, then there’s a problem.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Good point. I missed the part about the issue occurring during stress
testing.
Tim Roberts wrote:
nayan kumar wrote:
> But why windows put yellow mark on the driver .that we usually see
> when while installing driver it fails.
>
> is it ok even if windows is showing the yellow mark after stress testing.
If you shut off the memory failure injection and you STILL see the
yellow mark, then there’s a problem.
PNP operations like AddDevice or IRP_MJ_START_DEVICE typically require you to allocate some resources. So it’s entirely possible they could fail under low resource simulation (or under a real low-resource condition). When they fail you want to be sure the system doesn’t crash or hang and that you haven’t leaked memory. But it’s okay to fail to start the device. If that happens then the PNP manager will put a yellow ! on the device and this is expected.
It’s good to try PNP operations under low resource simulation, but make sure you test with low-resource simulation turned on and turned off so that you exercise as much of your driver as possible. You can use verifier.exe to configure which verifier tests/settings are enabled for your driver.
-p
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of nayan kumar
Sent: Wednesday, October 24, 2007 6:09 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] how can i determine what is the problem from driver verifier result
Hi Tim,
Thaks for the feedback.
But why windows put yellow mark on the driver .that we usually see when while installing driver it fails.
is it ok even if windows is showing the yellow mark after stress testing.
Regards
Search from any Web page with powerful protection. Get the FREE Windows Live Toolbar Today! Try it now!http:
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer</http:>
Hi All,
Thanks all for your input.
Driver installation and uninstallation is working properly in normal case. no problem at all in normal case.
I performed stress testing with the help of PnpDriverTestTool and driver verifier with and without low resource simulation option.
There is no any problem if i am performing test without low resource simulation .Niether winow is putting yellow mark on driver icon nor driver is crashing or failing.
if i am performing test with low resource simulation then winow is putting yellow mark on driver icon .
If i want to solve that problem how i can find where the actual problem is .any kind of tutorial or link that throw some light about how to find the problem in this kind of situation .
if reason will be known it would be very easy to solve the problem.
Regards
Get the new Windows Live Messenger!
http://get.live.com/messenger/overview
To reiterate what peter Wieland said, having a !'ed out device in device manager when you turn on driver verifier, esp low resource simulation is not a failure or bad result, it is to be expected many times. If you want to find the exact point of failure in your driver, you need to log this yourself.
d
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of nayan kumar
Sent: Thursday, October 25, 2007 6:03 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] how can i determine what is the problem from driver verifier result
Hi All,
Thanks all for your input.
Driver installation and uninstallation is working properly in normal case. no problem at all in normal case.
I performed stress testing with the help of PnpDriverTestTool and driver verifier with and without low resource simulation option.
There is no any problem if i am performing test without low resource simulation .Niether winow is putting yellow mark on driver icon nor driver is crashing or failing.
if i am performing test with low resource simulation then winow is putting yellow mark on driver icon .
If i want to solve that problem how i can find where the actual problem is .any kind of tutorial or link that throw some light about how to find the problem in this kind of situation .
if reason will be known it would be very easy to solve the problem.
Regards
Get the new Windows Live Messenger! Try it!http:
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer</http:>
nayan kumar wrote:
Driver installation and uninstallation is working properly in normal
case. no problem at all in normal case.
I performed stress testing with the help of PnpDriverTestTool and
driver verifier with and without low resource simulation option.
There is no any problem if i am performing test without low resource
simulation .Niether winow is putting yellow mark on driver icon nor
driver is crashing or failing.
if i am performing test with low resource simulation then winow is
putting yellow mark on driver icon .
If i want to solve that problem how i can find where the actual
problem is .any kind of tutorial or link that throw some light about
how to find the problem in this kind of situation .
if reason will be known it would be very easy to solve the problem.
It’s not a problem. That’s what we are trying to tell you. The low
resources simulation is there to make sure your driver fails gracefully
when memory requests fail. The yellow bang is an indication of a
graceful failure (as opposed to a blue screen), so you are doing exactly
what you are supposed to do.
Be happy!
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.