From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 215445] AMDGPU -- UBSAN: invalid-load in amdgpu_dm.c:5882:84 - load of value 32 is not a valid value for type '_Bool'
Date: Wed, 12 Jan 2022 20:23:32 +0000 [thread overview]
Message-ID: <bug-215445-2300-mU7XfHVp9b@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215445-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215445
--- Comment #7 from Bogdan (bogdan.pylypenko107@gmail.com) ---
UBSAN <- Undefined Behaviour sanity checker
> Compile-time instrumentation is used to detect various undefined behaviours
> at runtime.
> For more details, see: Documentation/dev-tools/ubsan.rst
UBSAN is just a technology that help to detect various bugs, not a bug source.
I resolve problem by kernel rebuild:
- rebuild 5.15.12 with different kernel config - have no UBSAN warnings (big
changes made - can not detect which kernel config parameter resolve problem);
- update to 5.15.13 - have no UBSAN warnings, have single crash in amdgpu
driver with closing X subsystem (sysrq helps to restart display manager);
- update to 5.16.0 - have no UBSAN warnings, but have high latencies (12-15 ms)
in [drm_atomic_helper_wait_for_flip_done] in high loaded mode (detected by
latencytop program).
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2022-01-12 20:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 3:34 [Bug 215445] New: UBSAN: invalid-load in amdgpu_dm.c:5882:84 - load of value 32 is not a valid value for type '_Bool' bugzilla-daemon
2022-01-03 3:38 ` [Bug 215445] " bugzilla-daemon
2022-01-03 3:41 ` bugzilla-daemon
2022-01-03 3:54 ` [Bug 215445] AMDGPU -- " bugzilla-daemon
2022-01-05 12:45 ` bugzilla-daemon
2022-01-06 22:05 ` bugzilla-daemon
2022-01-11 10:25 ` bugzilla-daemon
2022-01-11 11:42 ` bugzilla-daemon
2022-01-12 20:23 ` bugzilla-daemon [this message]
2022-01-13 2:50 ` bugzilla-daemon
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=bug-215445-2300-mU7XfHVp9b@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.