Do you know the variation/subvariation of the test? Also, getting a
stack trace of the thread blocking would tell quite a bit.
Pete
–
Kernel Drivers
Windows File System and Device Driver Consulting www.KernelDrivers.com
866.263.9295
------ Original Message ------
From: xxxxx@gastecnologia.com.br
To: “Windows File Systems Devs Interest List” Sent: 3/22/2017 2:31:38 PM Subject: RE:[ntfsd] Re[2]: Re[2]: HLK oplock test hangs
>Yes, I think so. On version 1511 and 32-bit systems this individual >test takes seconds. >I’ve let the system run for an entire weekend and it was stuck on the >same place. > >— >NTFSD is sponsored by OSR > > >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:</http:></http:>
Peter,
The tests started to fail from variation 11.
The test that hangs is subvariation 6.
I’m using virtual machines and yesterday I did a test run using a physical machine and it worked.
I run the HLK tests on VMs without issue. Are you able to get a stack dump of the hung thread?
Pete
On March 23, 2017 5:11:27 AM PDT, xxxxx@gastecnologia.com.br wrote:
Peter,
The tests started to fail from variation 11.
The test that hangs is subvariation 6.
I’m using virtual machines and yesterday I did a test run using a
physical machine and it worked.
NTFSD is sponsored by OSR
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:
– Sent from my Android device with K-9 Mail. Please excuse my brevity.</http:></http:>
I would be interested in the stack as well. Can you please post the hung
thread along with a !stacks 2 <yourdriver.sys> ?
Cheers, Gabriel
On Thu, Mar 23, 2017 at 7:31 PM, Peter Scott wrote:
> > I run the HLK tests on VMs without issue. Are you able to get a stack dump > of the hung thread? > > Pete > > > On March 23, 2017 5:11:27 AM PDT, xxxxx@gastecnologia.com.br wrote: >> >> Peter, >> The tests started to fail from variation 11. >> The test that hangs is subvariation 6. >> I’m using virtual machines and yesterday I did a test run using a physical machine and it worked. >> >> — >> NTFSD is sponsored by OSR >> >> >> 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: >> >> > – > Sent from my Android device with K-9 Mail. Please excuse my brevity. > — > NTFSD is sponsored by OSR > > > 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> >
Well, just after this conversation I found that running on a new VM with just the bare minimum configuration for HLK did work (Guest user enabled and volumes for FS testing).
One important thing: turn on the test mode manually before using HLK. This way I found that one of the VMs still had Secure Boot enabled. Event tough I have disabled that they continued to fail, so I just switched to the new VMs and now everything is fine. I’ve found that when loading opkey.sys starting the manual test run.
I didn’t take the time to get the stack dump, sorry Grabriel.
Thanks for all your help guys, you’ve been great in these forums.
I know this is an ancient thread, but I found the reason why this happens, maybe this can help someone in the future.
So basically I got the same thing I was running Server 2016 which according to the documentation requires Secure Boot so I ran the test without testsigning. The issue was that even though opkey.sys was added as a service, it was never loaded and thats what caused the hang. I tested this in another VM, seems to be working only when the driver is loaded, without it, it hangs.