Analyzers
Community support for Analyzers (Intel VTune™ Profiler, Intel Advisor, Intel Inspector)
4963 Discussions

[VTUNE] sep5.service failed: 236/SMACK_PROCESS_LABEL

Bram_S_
New Contributor I
1,561 Views

After installing intel-oneapi-vtune (2023.1.0-44286) on Ubuntu 23.04: 

$ sudo systemctl status sep5
× sep5.service - systemd script to load sep5 driver at boot time
     Loaded: loaded (/lib/systemd/system/sep5.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Thu 2023-04-27 12:50:19 PDT; 6min ago
    Process: 261391 ExecStart=/usr/local/sbin/sep5-load.sh start (code=exited, status=236/SMACK_PROCESS_LABEL)
   Main PID: 261391 (code=exited, status=236/SMACK_PROCESS_LABEL)
        CPU: 62ms

Apr 27 12:50:19 deca systemd[1]: Starting sep5.service - systemd script to load sep5 driver at boot time...
Apr 27 12:50:19 deca sep5-load.sh[261391]: Loading the sep5 driver:
Apr 27 12:50:19 deca groupmod[261445]: group changed in /etc/group (group vtune/1002)
Apr 27 12:50:19 deca sep5-load.sh[261392]: The sep5 driver is already loaded!  Use ./rmmod-sep to unload it.
Apr 27 12:50:19 deca systemd[1]: sep5.service: Main process exited, code=exited, status=236/SMACK_PROCESS_LABEL
Apr 27 12:50:19 deca systemd[1]: sep5.service: Failed with result 'exit-code'.
Apr 27 12:50:19 deca systemd[1]: Failed to start sep5.service - systemd script to load sep5 driver at boot time.
$

OS: Ubuntu 23.04

CPU: i12600k

 

0 Kudos
7 Replies
Bram_S_
New Contributor I
1,526 Views

Rebooting gave me a working sep5 service.

 

But the vtune-self-test.sh crashes my kernel in 50% or so of its runs.


From my system log:

Apr 28 13:08:51 deca kernel: BUG: scheduling while atomic: sep/25740/0x00000002

 

So there is something wrong in the sep5 module.

 

The loading of the sep5 module seems to be fine:

Apr 28 13:11:02 deca kernel: vtsspp: PERFMONv5: fixed events: 3, generic counters: 6
Apr 28 13:11:02 deca kernel: vtsspp: Kernel: KPTI detected
Apr 28 13:11:02 deca kernel: vtsspp: Kernel: KASLR detected
Apr 28 13:11:02 deca kernel: vtsspp: Driver has been loaded
Apr 28 13:11:02 deca sep5-load.sh[1123]: Checking for socwatch driver ... not detected.
Apr 28 13:11:02 deca sep5-load.sh[2413]: Executing: insmod ./socwatch/drivers/socwatch2_15-x32_64-6.2.0-20-genericsmp.ko
Apr 28 13:11:02 deca kernel: socwatch2_15: -----------------------------------------
Apr 28 13:11:02 deca kernel: socwatch2_15: OK: LOADED SoC Watch Driver
Apr 28 13:11:02 deca kernel: socwatch2_15: -----------------------------------------
Apr 28 13:11:03 deca sep5-load.sh[2413]: Setting group ownership of device file to group "vtune" ... done.
Apr 28 13:11:03 deca sep5-load.sh[2413]: Setting file permissions of device file to "660" ... done.
Apr 28 13:11:03 deca sep5-load.sh[2413]: The socwatch2_15-x32_64-6.2.0-20-genericsmp driver has been successfully loaded.
Apr 28 13:11:03 deca sep5-load.sh[2413]: NOTE:
Apr 28 13:11:03 deca sep5-load.sh[2413]: The driver is accessible only to users under the group 'vtune'.
Apr 28 13:11:03 deca sep5-load.sh[2413]: Please add the users to the group 'vtune' to use the tool.
Apr 28 13:11:03 deca sep5-load.sh[2413]: To change driver access group, reinstall the driver using -g <desired_group> option.
Apr 28 13:11:03 deca sep5-load.sh[1123]: NOTE:
Apr 28 13:11:03 deca sep5-load.sh[1123]: The driver is accessible only to users under the group vtune.
Apr 28 13:11:03 deca sep5-load.sh[1123]: Please add the users to the group vtune to use the tool.
Apr 28 13:11:03 deca sep5-load.sh[1123]: To change driver access group, reload the driver using -g <desired_group> option.
Apr 28 13:11:03 deca systemd[1]: Finished sep5.service - systemd script to load sep5 driver at boot time.

 

OS: Ubuntu 23.04

CPU: Intel Alderlake 12600k

GPU: Intel AlderLake-S GT1

vtune: 2023.1.0-44286

0 Kudos
AlekhyaV_Intel
Moderator
1,448 Views

Hi,

 

Thank you for posting in Intel Communities. We tried reproducing your issue. Please find our observations below:

 

Issue 1: Failed sep5 service

We got the same error i.e. ERROR: sep5 driver "sep5-x32_64-6.2.0-20-genericsmp.ko" while building drivers. So, we tried to set the driver access group ownership to determine which set of users can perform the collection on the system. You may set your own group during installation in the Advanced options or change it manually after installation by executing: ./boot-script -–group <your_group> from the <install-dir>/sepdk/src directory. I have tried to set the permissions to root with the below command:

 

./boot-script --group root

 

AlekhyaV_Intel_0-1683036439882.png

 

Issue 2: vtune-self-test.sh crashes my kernel in 50% or so of its runs

We tried running vtune-self-checker.sh script from <vtune-installed-directory>/bin64 folder, we didn't observe any crash on kernel. It worked fine and we got the expected results as follows:

 

./vtune-self-checker.sh

 

AlekhyaV_Intel_1-1683036489653.png

 

Here's my kernel version: 6.2.0-20-generic

OS: Ubuntu 23.04

CPU: Intel Alder Lake-P

 

Could you please share the crash log and kernel version so that we can debug further?

 

Regards,

Alekhya

 

 

 

0 Kudos
Bram_S_
New Contributor I
1,436 Views

There is no way to get the logs from vtune, because my machine hard freezes, and I can only get out of that with powercycle or hard-reset.

 

The kernel does capture the kernel crash in the logs, fortunately.

 


May 02 09:19:31 deca kernel: vtsspp: Kernel: KPTI disabled
May 02 09:19:31 deca kernel: vtsspp: Transport per-process size: 8192 pages
May 02 09:19:31 deca kernel: vtsspp: PEBS: record size: 0xc8, mask: 0xf000000ff, counters: 12
May 02 09:19:31 deca kernel: vtsspp: PEBS: record size: 0xc8, mask: 0x70000003f, counters: 9
May 02 09:19:31 deca kernel: vtsspp: PMU: uploading 18 core events
May 02 09:19:31 deca kernel: vtsspp: PMU: uploading 4 atom events
May 02 09:19:31 deca kernel: vtsspp: Registered NMI handler
May 02 09:19:31 deca kernel: vtsspp: Registered 'sched_process_fork' tracepoint
May 02 09:19:31 deca kernel: vtsspp: Registered 'sched_process_exec' tracepoint
May 02 09:19:31 deca kernel: vtsspp: Registered 'sched_process_exit' tracepoint
May 02 09:19:31 deca kernel: vtsspp: Registered 'sched_switch' tracepoint
May 02 09:19:31 deca kernel: vtsspp: Registered 'vma_store' tracepoint
May 02 09:19:31 deca kernel: vtsspp: Trace flags: 0x872e
May 02 09:19:31 deca kernel: vtsspp: Active CPU mask: 0-15
May 02 09:19:31 deca kernel: vtsspp: Time source: TSC
May 02 09:19:31 deca kernel: vtsspp: Collection started
May 02 09:19:31 deca kernel: vtsspp: Attached to 'matrix' (pid: 23619)
May 02 09:19:35 deca kernel: vtsspp: Collection stopped
May 02 09:19:35 deca kernel: vtsspp: Memory used: 34MB
May 02 09:19:35 deca kernel: vtsspp: Collection duration: 4 sec
May 02 09:19:35 deca kernel: vtsspp: Transport shutdown: 31 msec
May 02 09:19:40 deca kernel: vtsspp: Kernel: KPTI disabled
May 02 09:19:40 deca kernel: vtsspp: Transport per-process size: 8192 pages
May 02 09:19:40 deca kernel: vtsspp: PEBS: record size: 0xc8, mask: 0xf000000ff, counters: 12
May 02 09:19:40 deca kernel: vtsspp: PEBS: record size: 0xc8, mask: 0x70000003f, counters: 9
May 02 09:19:40 deca kernel: vtsspp: PMU: uploading 6 core events
May 02 09:19:40 deca kernel: vtsspp: PMU: uploading 4 atom events
May 02 09:19:40 deca kernel: vtsspp: Registered NMI handler
May 02 09:19:40 deca kernel: vtsspp: Registered 'sched_process_fork' tracepoint
May 02 09:19:40 deca kernel: vtsspp: Registered 'sched_process_exec' tracepoint
May 02 09:19:40 deca kernel: vtsspp: Registered 'sched_process_exit' tracepoint
May 02 09:19:40 deca kernel: vtsspp: Registered 'sched_switch' tracepoint
May 02 09:19:40 deca kernel: vtsspp: Registered 'vma_store' tracepoint
May 02 09:19:40 deca kernel: vtsspp: Trace flags: 0x832f
May 02 09:19:40 deca kernel: vtsspp: Active CPU mask: 0-15
May 02 09:19:40 deca kernel: vtsspp: Time source: TSC
May 02 09:19:40 deca kernel: vtsspp: Collection started
May 02 09:19:40 deca kernel: vtsspp: Attached to 'matrix' (pid: 23747)
May 02 09:19:43 deca kernel: vtsspp: Collection stopped
May 02 09:19:43 deca kernel: vtsspp: Memory used: 34MB
May 02 09:19:43 deca kernel: vtsspp: Collection duration: 4 sec
May 02 09:19:43 deca kernel: vtsspp: Transport shutdown: 27 msec
May 02 09:19:50 deca kernel: BUG: scheduling while atomic: matrix.dpcpp/23977/0x00000002
May 02 09:19:50 deca kernel: Modules linked in: tls nvme_fabrics socwatch2_15(OE) vtsspp(OE) sep5(OE) socperf3(OE) snd_seq_dummy snd_hrtimer pax(OE) binfmt_misc snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci_intel_tg>
May 02 09:19:50 deca kernel:  polyval_clmulni videobuf2_vmalloc videobuf2_memops polyval_generic cec ghash_clmulni_intel snd_rawmidi videobuf2_v4l2 sha512_ssse3 rc_core videodev snd_seq aesni_intel drm_kms_helper crypto_simd >
May 02 09:19:50 deca kernel: CPU: 4 PID: 23977 Comm: matrix.dpcpp Tainted: G           OE      6.2.0-20-generic #20-Ubuntu
May 02 09:19:50 deca kernel: Hardware name: ASUS System Product Name/PRIME Z690M-PLUS D4, BIOS 2212 12/13/2022
May 02 09:19:50 deca kernel: Call Trace:
May 02 09:19:50 deca kernel:  <TASK>
May 02 09:19:50 deca kernel:  dump_stack_lvl+0x48/0x70
May 02 09:19:50 deca kernel:  dump_stack+0x10/0x20
May 02 09:19:50 deca kernel:  __schedule_bug+0x64/0x80
May 02 09:19:50 deca kernel:  __schedule+0x4f6/0x610
May 02 09:19:50 deca kernel:  schedule+0x63/0x110
May 02 09:19:50 deca kernel:  schedule_preempt_disabled+0x15/0x30
May 02 09:19:50 deca kernel:  rwsem_down_read_slowpath+0x284/0x4d0
May 02 09:19:50 deca kernel:  down_read+0x48/0xc0
May 02 09:19:50 deca kernel:  UTILITY_down_read_mm+0x12/0x20 [sep5]
May 02 09:19:50 deca kernel:  linuxos_Exec_Unmap_Notify+0xbd/0x180 [sep5]
May 02 09:19:50 deca kernel:  ? __vm_munmap+0x1/0x1a0
May 02 09:19:50 deca kernel:  kprobe_ftrace_handler+0x113/0x1e0
May 02 09:19:50 deca kernel:  ? __vm_munmap+0x5/0x1a0
May 02 09:19:50 deca kernel:  0xffffffffc04de0f7
May 02 09:19:50 deca kernel: RIP: 0010:__vm_munmap+0x1/0x1a0
May 02 09:19:50 deca kernel: Code: c9 31 f6 31 ff 45 31 c0 45 31 c9 c3 cc cc cc cc 66 0f 1f 84 00 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 e8 <ab> 44 71 24 55 48 89 e5 41 57 41 56 41 89 d6 41 55 4c 8d 6d 80>
May 02 09:19:50 deca kernel: RSP: 0018:ffff9b00477f7ea8 EFLAGS: 00000202 ORIG_RAX: 0000000000000000
May 02 09:19:50 deca kernel: RAX: ffffffff9bdc9d30 RBX: ffff9b00477f7f58 RCX: 0000000000000000
May 02 09:19:50 deca kernel: RDX: 0000000000000001 RSI: 0000000000001000 RDI: 00007f553559c000
May 02 09:19:50 deca kernel: RBP: ffff9b00477f7eb0 R08: 0000000000000000 R09: 0000000000000000
May 02 09:19:50 deca kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
May 02 09:19:50 deca kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
May 02 09:19:50 deca kernel:  ? __pfx___x64_sys_munmap+0x10/0x10
May 02 09:19:50 deca kernel:  ? __vm_munmap+0x5/0x1a0
May 02 09:19:50 deca kernel:  ? __x64_sys_munmap+0x1b/0x30
May 02 09:19:50 deca kernel:  ? __vm_munmap+0x5/0x1a0
May 02 09:19:50 deca kernel:  ? __x64_sys_munmap+0x1b/0x30
May 02 09:19:50 deca kernel:  do_syscall_64+0x58/0x90
May 02 09:19:50 deca kernel:  ? do_syscall_64+0x67/0x90
May 02 09:19:50 deca kernel:  ? __task_pid_nr_ns+0x6c/0xc0
May 02 09:19:50 deca kernel:  ? __task_pid_nr_ns+0x6c/0xc0
May 02 09:19:50 deca kernel:  ? exit_to_user_mode_prepare+0x30/0xb0
May 02 09:19:50 deca kernel:  ? syscall_exit_to_user_mode+0x29/0x50
May 02 09:19:50 deca kernel:  ? do_syscall_64+0x67/0x90
May 02 09:19:50 deca kernel:  ? do_syscall_64+0x67/0x90
May 02 09:19:50 deca kernel:  entry_SYSCALL_64_after_hwframe+0x72/0xdc
May 02 09:19:50 deca kernel: RIP: 0033:0x7f5539915a8b
May 02 09:19:50 deca kernel: Code: 8b 15 91 03 0e 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 ff 25 7a e5 a9 04 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 5d 03 0e 00 f7 d8 64 89 01>
May 02 09:19:50 deca kernel: RSP: 002b:00007ffecf3ec8b8 EFLAGS: 00000206 ORIG_RAX: 000000000000000b
May 02 09:19:50 deca kernel: RAX: ffffffffffffffda RBX: 00000000024f10b0 RCX: 00007f5539915a8b
May 02 09:19:50 deca kernel: RDX: 00007f553559b000 RSI: 0000000000001000 RDI: 00007f553559c000
May 02 09:19:50 deca kernel: RBP: 00007ffecf3ec950 R08: 00007f55399f6c88 R09: 00007f553559b000
May 02 09:19:50 deca kernel: R10: 0000000000000000 R11: 0000000000000206 R12: 00007ffecf3eca10
May 02 09:19:50 deca kernel: R13: 00000000024f0ff0 R14: 00000000024c1e20 R15: 0000000000001000
May 02 09:19:50 deca kernel:  </TASK>
0 Kudos
Bram_S_
New Contributor I
1,435 Views

NOTE: From that log, I see that matrix.dpcpp is the trigger of the kernel crash:

May 02 09:19:50 deca kernel: BUG: scheduling while atomic: matrix.dpcpp/23977/0x00000002

 

0 Kudos
AlekhyaV_Intel
Moderator
1,396 Views

Hi,


Thank you for sharing your log files. As your system's operating system and kernel is not in the lists of supported operating systems and supported kernels, it may/may not work.


Could you please try the same in any supported operating systems(https://www.intel.com/content/www/us/en/developer/articles/system-requirements/vtune-profiler-system-requirements.html) and check if the issue still persists?


Regards,

Alekhya


0 Kudos
AlekhyaV_Intel
Moderator
1,234 Views

Hi,


We have not heard back from you. Could you please give us an update regarding this issue?


Regards,

Alekhya


0 Kudos
AlekhyaV_Intel
Moderator
1,199 Views

Hi,


We have not heard back from you, so we will close this thread. If you need any further assistance, please post a new question as this thread will no longer be monitored by Intel.


Regards,

Alekhya



0 Kudos
Reply