![](https://seccdn.libravatar.org/avatar/77cb4da5f72bc176182dcc33f03a18f3.jpg?s=120&d=mm&r=g)
On 2023-01-24 04:15, David C. Rankin wrote:
On 1/23/23 05:49, Carlos E. R. wrote:
cer@Telcontar:~> sudo /usr/sbin/iotop -o -d 3.3333
Total DISK READ : 1169.77 K/s | Total DISK WRITE : 12.79 K/s Actual DISK READ: 1168.61 K/s | Actual DISK WRITE: 48.84 K/s TID PRIO USER DISK READ DISK WRITE SWAPIN IO> COMMAND 2041 be/4 news 490.70 K/s 0.00 B/s ?unavailable? texpire 9622 be/4 cer 0.00 B/s 6.98 K/s ?unavailable? firefox --sm-client-id 27~-9abbeba61260 [LS Thread] 8039 idle cer 679.07 K/s 0.00 B/s ?unavailable? tracker-miner-fs-3 12912 be/4 cer 0.00 B/s 5.81 K/s ?unavailable? firefox --sm-client-id 27~beba61260 [IndexedDB #45] * *
...
CONFIG_TASK_DELAY_ACCT not enabled in kernel, cannot determine SWAPIN and IO %
That is strange, confirmed with 5.14.21-150400.24.38-default as well on 15.4. Would be worth knowing whether enabling the option comes with any downside -- if not, why doesn't the kernel have it enabled?
Moreover, how did it go this long without being noticed?
Not that long, I know I used it maybe two months ago and it worked. I don't remember if that was on Leap 15.3 or 15.4, though. I will report in Bugzilla, time permitting. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)