Description of problem: when I dmesg to see a recent system stuff log I see something like tpm2-abrmd us going crazy in log producing too many entries : 2105.343807] traps: tpm2-abrmd[32056] trap int3 ip:7fe18ba94755 sp:7fe18b59bb40 error:0 in libglib-2.0.so.0.6200.4[7fe18ba59000+83000] [ 2110.832149] traps: tpm2-abrmd[32106] trap int3 ip:7f6adc280755 sp:7f6adbd87b40 error:0 in libglib-2.0.so.0.6200.4[7f6adc245000+83000] [ 2116.337903] traps: tpm2-abrmd[32182] trap int3 ip:7fb911d02755 sp:7fb911809b40 error:0 in libglib-2.0.so.0.6200.4[7fb911cc7000+83000] [ 2121.832676] traps: tpm2-abrmd[32239] trap int3 ip:7fc7586b7755 sp:7fc7581beb40 error:0 in libglib-2.0.so.0.6200.4[7fc75867c000+83000] [ 2127.331619] traps: tpm2-abrmd[32289] trap int3 ip:7f837927d755 sp:7f8378d84b40 error:0 in libglib-2.0.so.0.6200.4[7f8379242000+83000] [ 2132.833817] traps: tpm2-abrmd[32344] trap int3 ip:7fce374c9755 sp:7fce36fd0b40 error:0 in libglib-2.0.so.0.6200.4[7fce3748e000+83000] [ 2138.333485] traps: tpm2-abrmd[32407] trap int3 ip:7f9d34b34755 sp:7f9d3463bb40 error:0 in libglib-2.0.so.0.6200.4[7f9d34af9000+83000] [ 2143.831239] traps: tpm2-abrmd[32463] trap int3 ip:7fd1dff48755 sp:7fd1dfa4fb40 error:0 in libglib-2.0.so.0.6200.4[7fd1dff0d000+83000] [ 2149.341527] traps: tpm2-abrmd[32532] trap int3 ip:7f62a2cd5755 sp:7f62a27dcb40 error:0 in libglib-2.0.so.0.6200.4[7f62a2c9a000+83000] [ 2154.845002] traps: tpm2-abrmd[32618] trap int3 ip:7fd11c291755 sp:7fd11bd98b40 error:0 in libglib-2.0.so.0.6200.4[7fd11c256000+83000] ... dont know what that means, but it's like hundreds lines so far. This morning I found the system in read-only state, and I suspect tpm2-abrmd to fill to much the filesystem. Version-Release number of selected component (if applicable): tpm2-abrmd-selinux-2.1.0-3.fc31.noarch tpm2-abrmd-2.2.0-2.fc31.x86_64 Fedora release 31 (Thirty One) Using latest kernel: 5.4.8-200.fc31.x86_64 (system is totally up-to-date by time of filing this bug How reproducible: I dont know :/ I think It started to appear during last few kernel updates. havent seen that before, maybe 14 days back. Steps to Reproduce: 1. :( 2. 3. Actual results: :( Expected results: I think something is wrong with the component Additional info: My sysinfo might by helpful: https://paste.centos.org/view/4e96b6bf
Known issue(rhbz#1772899). Fixes just landed on upstream, and new RPM 2.2.0-4 for F31 with fixes included is available here: https://koji.fedoraproject.org/koji/buildinfo?buildID=1428972 With this the issue is supposed to be fixed. Please help to verify. If issue fixed please help to add "Karma +1" at: https://bodhi.fedoraproject.org/updates/FEDORA-2020-fbf5351fe3 which could speed up the new RPM availalbe for F31 stable. Thanks.
thx, works for me. Karma+1
Thanks for the verification. Is it to close this ticket now?