-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
INVARIANTS panic in intel_engine_init_cmd_parser #282
Comments
The panic is from
which has been there since f9e90c24737f9 |
Panic does not occur with emaste@b6ecd6f applied. I assume this code has just not been run w/ INVARIANTS previously. |
Mhm weird, is kmalloc supposed to bzero in linux ? |
So having looked at the Linux code it seems that they don't check this, also hash_add seems to use hlist and not the hash rcu ones that we do use. |
Linux has |
hash_add_rcu asserted that the node's prev pointer was NULL in an attempt to detect addition of a node already on a list, but the caller is not required to provide a zeroed node. Reported in freebsd/drm-kmod#282 Reviewed by: bz, manu Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D43645
Fixed by freebsd/freebsd-src@7e77089 |
hash_add_rcu asserted that the node's prev pointer was NULL in an attempt to detect addition of a node already on a list, but the caller is not required to provide a zeroed node. Reported in freebsd/drm-kmod#282 Reviewed by: bz, manu Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D43645 (cherry picked from commit 7e77089)
hash_add_rcu asserted that the node's prev pointer was NULL in an attempt to detect addition of a node already on a list, but the caller is not required to provide a zeroed node. Reported in freebsd/drm-kmod#282 Reviewed by: bz, manu Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D43645 (cherry picked from commit 7e77089)
hash_add_rcu asserted that the node's prev pointer was NULL in an attempt to detect addition of a node already on a list, but the caller is not required to provide a zeroed node. Reported in freebsd/drm-kmod#282 Reviewed by: bz, manu Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D43645
Describe the bug
panic: node is already on list or was not zeroed
immediately upon bootFreeBSD version
FreeBSD 15.0-CURRENT wipbsd-n267714-217416d818df GENERIC amd64
(This is my WIP branch with a number of changes but should not be related; this is the same kernel as in #280 which worked until
sysctl -a
)PCI Info
DRM KMOD version
From git, 1af4c68
To Reproduce
kldload i915kms
Screenshots
N/A
Additional context
Note this is GENERIC with INVARIANTS
The text was updated successfully, but these errors were encountered: