topic Betreff: Re:Assert failed while running Profiler 2020 Update 2 in Analyzers

Assert failed while running Profiler 2020 Update 2

Mentopolis — Thu, 03 Sep 2020 10:43:22 GMT

Hello,

while running our C++ application in Profiler 2020 update 2 we get in most runs a assertation. The program abort and no performance report is created. Without profiler no such error appears.

Assertion failed: thread_manager_impl:1332: (threads_count != (tpss_u32_t)(-1)) : . Please contact the technical support.

regards

Markus

Re: Assert failed while running Profiler 2020 Update 2

JananiC_Intel — Fri, 04 Sep 2020 06:42:19 GMT

Hi,

Thanks for posting in Intel forums.

Please let us know the platform details so that we can try from our side.Also run the self checker script which is located in <install_dir>/bin64 .This script is used to validate your installation and system setup,so run this script and let us know the result.

Re: Assert failed while running Profiler 2020 Update 2

Mentopolis — Fri, 04 Sep 2020 11:18:47 GMT

Hello,

Computer is a Intel (R) Core (TM) I7-2760QM CPU with 2.40 Ghz

when running the checker script in Admin mode i get a Blue-Screen with "SYSTEM_SERVICE_EXCEPTION" .. in common i can run in Admin mode but sometimes i also get a bluenscreen when set samples lower than 10 ms

when running the checker in normal user mode i get :

Intel(R) VTune(TM) Profiler Self Check Utility
Copyright (C) 2009-2019 Intel Corporation. All rights reserved.
Build Number: 610396

Instrumentation based analysis check
Example of analysis types: Hotspots with default knob sampling-mode=sw, Threading with default knob sampling-and-waits=sw
Collection: Ok
vtune: Warning: Hardware collection of CPU events is not possible on this system. Microarchitecture performance insights will not be available.
vtune: Warning: To collect microarchitecture performance insights, run the product as administrator.
Finalization: Ok...
Report: Ok

HW event-based analysis check
Example of analysis types: Hotspots with knob sampling-mode=hw, HPC Performance Characterization, etc.
Collection: Fail
vtune: Error: Cannot enable Hardware Event-based Sampling due to a problem with the driver (sep*/sepdrv*). Check that the driver is running and the driver group is in the current user group list. See the "Sampling Drivers" help topic for further details.
vtune: Error: To collect hardware events, run the product as administrator.

HW event-based analysis check
Example of analysis types: Microarchitecture Exploration
Collection: Fail
vtune: Error: Cannot enable Hardware Event-based Sampling due to a problem with the driver (sep*/sepdrv*). Check that the driver is running and the driver group is in the current user group list. See the "Sampling Drivers" help topic for further details.
vtune: Error: To collect hardware events, run the product as administrator.

HW event-based analysis with uncore events
Example of analysis types: Memory Access
Collection: Fail
vtune: Error: Cannot enable Hardware Event-based Sampling due to a problem with the driver (sep*/sepdrv*). Check that the driver is running and the driver group is in the current user group list. See the "Sampling Drivers" help topic for further details.
vtune: Error: To collect hardware events, run the product as administrator.

HW event-based analysis with stacks
Example of analysis types: Hotspots with knob sampling-mode=hw and knob enable-stack-collection=true, etc.
Collection: Fail
vtune: Error: Cannot enable Hardware Event-based Sampling due to a problem with the driver (sep*/sepdrv*). Check that the driver is running and the driver group is in the current user group list. See the "Sampling Drivers" help topic for further details.
vtune: Error: To collect hardware events, run the product as administrator.

HW event-based analysis with context switches
Example of analysis types: Threading with knob sampling-and-waits=hw
Collection: Fail
vtune: Error: Cannot enable Hardware Event-based Sampling due to a problem with the driver (sep*/sepdrv*). Check that the driver is running and the driver group is in the current user group list. See the "Sampling Drivers" help topic for further details.
vtune: Error: To collect hardware events, run the product as administrator.

The check observed a product failure on your system.
Review errors in the output above to fix a problem or contact Intel technical support.

Log location: C:\Users\mzajc\AppData\Local\Temp\vtune-tmp-mzajc\self-checker-2020.09.04_13.10.12\log.txt

the checker Tool output looks like this

Re: Assert failed while running Profiler 2020 Update 2

JananiC_Intel — Tue, 08 Sep 2020 06:18:44 GMT

Hi,

We are forwarding your case to Subject Matter Experts.

Thanks

Re: Assert failed while running Profiler 2020 Update 2

Vinutha_SV — Thu, 17 Sep 2020 16:23:06 GMT

What analysis are you trying to run? Looks like SEP drivers are not installed. Please make sure the drivers are installed and then try H/W events based sampling collection.

Re: Assert failed while running Profiler 2020 Update 2

Mentopolis — Sat, 19 Sep 2020 18:52:49 GMT

Just reinstall the software from scratch.. the same result as in the first comment. Are there custom steps needed for setup this driver ?

Re: Assert failed while running Profiler 2020 Update 2

Vinutha_SV — Fri, 09 Oct 2020 15:11:01 GMT

Looking at the logs, it is clear that SEP driver is not installed and so h/w event based sampling is failing.

You can install SEP drivers on windows, please refer to below link:

https://software.intel.com/content/www/us/en/develop/documentation/vtune-help/top/set-up-analysis-target/windows-targets/installing-the-sampling-drivers-for-windows-targets.html

Re:Assert failed while running Profiler 2020 Update 2

Vinutha_SV — Thu, 22 Oct 2020 16:18:37 GMT

Can you please attach the logs and the result directory to work on the issue?

Re:Assert failed while running Profiler 2020 Update 2

Vinutha_SV — Thu, 19 Nov 2020 16:40:43 GMT

Hi,

Since I have not heard from you since 2 weeks, I will be closing this thread in next 2 days.

Betreff: Re:Assert failed while running Profiler 2020 Update 2

Mentopolis — Fri, 20 Nov 2020 08:02:40 GMT

sorry for the delay the first mail was gone into the Spam folder.

It seems to work after this steps. Even the hardware based sampling does not show an Bluescreen.

thank you for your support

Re:Assert failed while running Profiler 2020 Update 2

Vinutha_SV — Fri, 20 Nov 2020 08:57:36 GMT

Good to know that. I will be closing this thread.