Windows 10 IoT ent, Verifier low resource simulation not functional?

Tried both, systematic and random, seperately and together, and I would normally expect to see an immediate driver load error, then add device failures etc as normal, but on Windows 10 IoT enterprise no resource request is being denied.

Is there any trick to get this working?

On Feb 2, 2017, at 6:51 AM, xxxxx@hotmail.com wrote:

Tried both, systematic and random, seperately and together, and I would normally expect to see an immediate driver load error, then add device failures etc as normal, but on Windows 10 IoT enterprise no resource request is being denied.

Is there any trick to get this working?

The low resource simulation doesn’t start right away. It gives the driver a chance to get going before it starts random failures. Is your device making multiple memory requests after it gets going?

Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

Yes.

Last time I used this (on wiondows 7 AFAIR) the driver immediately failed to load because of an alocation fail in driver entry.

Next time that ran through and add decvice failed.

ie it was progressive, and immediate.

On windows 10 so far it has failed one allocation (thats in about 4 hours of testing).

I really thought it wasnt going to do anything, as it is it isnt particularly lively.

You might already know this, but you CAN control a bunch of stuff about Low Resource Simulation these days… including the probability of getting a failure. The settability is in response to people’s complaints that it didn’t wait long enough, or it failed too much, or whatever.

It defaults to failing some small number like 5% probability, IIRC.

Is the Verifier app available on IoT Ent?

Peter
OSR
@OSRDrivers

Dont know Peter, never heard of it. Can I crank up the failure rate with it?

Have to say I find it odd that people complained about its resource failure being too quick. It was ideal IMO, at every request the driver made it would be sequentially failed. Within a few hours you could verify all the fauilure paths from your code. Now its going to take days, and interfere with functional testing.

Yup. See, the section headed “Customizing the Settings”:

https:

Peter
OSR
@OSRDrivers</https:>

Thats 404ing for me PEter.

I assume you mean the new UI that pops up after you select the verifier settings and click next? The one with the 4 radio buttons?

Whats the value to put in the failure probability, .95? 95?

I’ll have another troll through the MSDN see if I can find anythgni on it, last time I looked at ‘whats new for windows 10’ in respect of verifier it didnt mention it at all.

Systematic low resource doesnt appear to do anything Peter. According to the documentation if it comes across a stck it hasnt seen before it will fail requests, thus it progressively works through a driver.

Well, it doesnt work through anything since after ten minutes the driver is still fully functional (yes, I did replug it many many times). Is there any magic trick to get this to work like it used to?

Seems the other low resource probability setting is 'number of chances in 10,000 ’ OK, that was intuitive… :wink:

Anyway, lets hope it works…

it’s not clear to me that low resource simulation in an embedded system
makes a whole lot of sense. Not a gp os. You have to have enough memory for
your purpose.

Mark Roddy

On Tue, Feb 7, 2017 at 8:51 AM, wrote:

> Systematic low resource doesnt appear to do anything Peter. According to
> the documentation if it comes across a stck it hasnt seen before it will
> fail requests, thus it progressively works through a driver.
>
> Well, it doesnt work through anything since after ten minutes the driver
> is still fully functional (yes, I did replug it many many times). Is there
> any magic trick to get this to work like it used to?
>
> Seems the other low resource probability setting is 'number of chances in
> 10,000 ’ OK, that was intuitive… :wink:
>
> Anyway, lets hope it works…
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list online at: http:> showlists.cfm?list=ntdev>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer&gt;
></http:></http:>

Well, its called embedded, its actually Enterprise, ie, WIndows 10 desktop rebranded as IoT as a marketing gimmick. Put it this way, its massive, and you cant trim the OS down like Win7 embedded.

Anyway, as always I am trying to test my driver completely, but verifiers low resource simulation just isnt any where near as good on windows as the last time I used it. (probably win 7)

OK, so this low resource simulation, it has failed the same memory allocation in Add Device 18 times in a row.

This is neither random nor systematic. (I set the probablility to 9000)