From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] intel_reg_checker segment fault on x86_64
Date: Wed, 25 Nov 2020 05:21:44 +0100 [thread overview]
Message-ID: <20201125042144.kjGrdGHH5h6OO4Y9QTcgdAnl_r6tTEg-Ts5jrPJwOeo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26671@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 4317 bytes --]
Closed issue by tw4452852 on void-packages repository
https://github.com/void-linux/void-packages/issues/26671
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
Void 5.8.18_1 x86_64 GenuineIntel notuptodate rF
* package:
igt-gpu-tools-1.25_2
### Expected behavior
intel_reg_checker works w/o segment fault
### Actual behavior
intel_reg_checker segment fault with kernel msg:
```
[339369.109908] intel_reg_check[29631]: segfault at 1d3f6 ip 000000000001d3f6 sp 00007ffe69bfbcb8 error 14 in intel_reg_checker[55d66cf5c000+1000]
[339369.109920] Code: Unable to access opcode bytes at RIP 0x1d3cc.
```
I did some initial debugging, it seems there's something wrong with F16C cpu feature, here's call stack:
```
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x000000000001d3f6 in ?? ()
(gdb) bt
#0 0x000000000001d3f6 in ?? ()
#1 0x00007f0d0af06539 in resolve_half_to_float () at ../lib/igt_halffloat.c:210
#2 0x00007f0d0af8b25a in elf_machine_rela (skip_ifunc=<optimized out>, reloc_addr_arg=0x7f0d0af73550 <igt_half_to_float@got.plt>, version=<optimized out>, sym=<optimized out>, reloc=0x7f0d0aef0a80, map=0x7f0d0af78000)
at ../sysdeps/x86_64/dl-machine.h:330
#3 elf_dynamic_do_Rela (skip_ifunc=<optimized out>, lazy=<optimized out>, nrelative=<optimized out>, relsize=<optimized out>, reladdr=<optimized out>, map=0x7f0d0af78000) at do-rel.h:137
#4 _dl_relocate_object (l=l@entry=0x7f0d0af78000, scope=<optimized out>, reloc_mode=<optimized out>, consider_profiling=<optimized out>, consider_profiling@entry=0) at dl-reloc.c:254
#5 0x00007f0d0af82d4a in dl_main (phdr=<optimized out>, phnum=<optimized out>, user_entry=<optimized out>, auxv=<optimized out>) at rtld.c:2257
#6 0x00007f0d0af975af in _dl_sysdep_start (start_argptr=start_argptr@entry=0x7ffe1eb01d80, dl_main=dl_main@entry=0x7f0d0af813a0 <dl_main>) at ../elf/dl-sysdep.c:253
#7 0x00007f0d0af80f36 in _dl_start_final (arg=0x7ffe1eb01d80) at rtld.c:447
#8 _dl_start (arg=0x7ffe1eb01d80) at rtld.c:537
#9 0x00007f0d0af80098 in _start () from /lib/ld-linux-x86-64.so.2
#10 0x0000000000000001 in ?? ()
#11 0x00007ffe1eb02684 in ?? ()
#12 0x0000000000000000 in ?? ()
```
### Steps to reproduce the behavior
Just type `intel_reg_checker` in shell.
prev parent reply other threads:[~2020-11-25 4:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 4:43 [ISSUE] " tw4452852
2020-11-25 4:21 ` ericonr
2020-11-25 4:21 ` ericonr [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201125042144.kjGrdGHH5h6OO4Y9QTcgdAnl_r6tTEg-Ts5jrPJwOeo@z \
--to=ericonr@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).