From nobody Mon Jan 30 14:27:30 2023 X-Original-To: freebsd-stable@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P59WN0PVhz3bL3r for ; Mon, 30 Jan 2023 14:27:44 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P59WM3bBVz3kJJ for ; Mon, 30 Jan 2023 14:27:43 +0000 (UTC) (envelope-from nvass@gmx.com) Authentication-Results: mx1.freebsd.org; none Received: from [5.203.213.109] ([5.203.213.109]) by web-mail.gmx.net (3c-app-mailcom-bs15.server.lan [172.19.170.183]) (via HTTP); Mon, 30 Jan 2023 15:27:30 +0100 List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 Message-ID: From: Nikos Vassiliadis To: Nikos Vassiliadis Cc: Mike Karels , freebsd-stable@freebsd.org Subject: Re: Kernel is using a lot of CPU (was: Re: test) Content-Type: text/plain; charset=UTF-8 Date: Mon, 30 Jan 2023 15:27:30 +0100 Importance: normal Sensitivity: Normal In-Reply-To: References: X-UI-Message-Type: mail X-Priority: 3 X-Provags-ID: V03:K1:qQ7JCrxja3mRRL6LG6WnTSIPMOmlHthfJKQXZ1BiAbgdEniO6YBTEMKi+dxhbHUkyPbXZ fvaSgbHdl+CATnSi7oqi7KaYaE/BEPBim62xqL6ZLIUxJDNwsOw90j2dg8CsPsgKFbGJ0yoldLQ3 jymFWTxI6uUry+el83STJruMOr0r/JjwYXmBgL38alVsHW/XEUVUE9nNTCcHD06WhzWGqgPZ9FBt 6efs/Cz70DgIqFKgROxNbLBNRVsZHvaYa9UGFulmiSPTsCiz0hubpWrfJvxFn8rBGLKzDELAHUAB MY= X-Spam-Flag: NO UI-OutboundReport: notjunk:1;M01:P0:+CSQBZAQ2MM=;ScIJrpLZwxOyEqEVB5XtPHQe37X cESrGEZ24fOy5LmFNr+E+nH5LjTrNOUoraZctqjbiZcF5lr+RTPj+DZZhibqPaK2WVFcHySv4 eZl0J+DCz8vpfuydePP1nGf1LYx4PZQIfkJbgWWT/ZToLy1x53wtZhy74PCjgKsG+ilK7jV9H +9kJdTZGVPgIkGa0hh00shV84x0WfxpWSd0ZE7nFF8a5WTHal8R41xShPLAmYko0N1twS6Zuf 7Dswgdhd19FPikH+JEEv8LONrSmrOM45q+Ewx87tne5avBFH91vaQAD7E3M0Tcw5Oeh/+p/ds cnOiY2nqXTYilHic8TOTLcq7IqPfDnNgpTonm9PLZQ7ZdYOaJYsGqyXkzUa+sF92djApH44SA oc+N6Cw1SDQxB6klZ5lY/dwreU3sI31neFcR05odvneTbRjSQH8ngpuQM2GzOOYGatzlXy2Pr H7knLxym/amO+bzHpu57v6X0kqEjwIggmmI0U66nta1PYs78rGrdahF7w+zNpz12/JxnizDq5 43Knx1j9n74GT1/wTJcA0IALlw/JmkyhnyvjsuTc+1fMlaUqv12eXsTLGETC/pSQsttRQgO02 3nT1VQrMmLn5ANBHPziFlgfz3AsFmRdBm1BoqhX7j8M8OrWKE2Pm7y+UILvX/x1ewW9r5ILZo 75eWrrQFWM349aU9Z2Z9nu6aE9PjBpA98n7It5wlJg89YXF81Jx7gw/xELayBeJusGaxZRRIP OHmJxPMaypKVe9ngPVMddP/jaiGnNRWIk9J4hPimhTTYPrmhhkPWRtd8Pd5ixaizQvDJE1FXK sTQnVzRPfQuP1diHEDiU0lCg== X-Rspamd-Queue-Id: 4P59WM3bBVz3kJJ X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N > Sent: Monday, January 30, 2023 at 3:37 PM > From: "Nikos Vassiliadis" > To: "Mike Karels" > Cc: freebsd-stable@freebsd.org > Subject: Re: Kernel is using a lot of CPU (was: Re: test) > > > > > Sent: Monday, January 30, 2023 at 3:27 PM > > From: "Mike Karels" > > To: "Nikos Vassiliadis" > > Cc: freebsd-stable@freebsd.org > > Subject: Re: Kernel is using a lot of CPU (was: Re: test) > > > > On 30 Jan 2023, at 5:03, Nikos Vassiliadis wrote: > > > > >> Hi, > > >> > > >> I just rebooted a system of mine and it seems that the kernel is constantly doing something. How could I debug this? > > >> I am thinking of rebooting it tonight > > >> > > >> root@aurora:~ # top -S -b > > >> last pid: 2196; load averages: 1.00, 1.00, 1.00 up 0+01:54:34 12:41:35 > > >> 72 processes: 2 running, 69 sleeping, 1 waiting > > >> CPU: 0.0% user, 0.0% nice, 24.6% system, 0.0% interrupt, 75.3% idle > > >> Mem: 46M Active, 171M Inact, 1429M Wired, 14G Free > > >> ARC: 919M Total, 354M MFU, 487M MRU, 6912K Anon, 8726K Header, 63M Other > > >> 234M Compressed, 610M Uncompressed, 2.60:1 Ratio > > >> Swap: 16G Total, 16G Free > > >> > > >> PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND > > >> 11 root 4 155 ki31 0B 64K RUN 0 345:06 314.31% idle > > >> 0 root 49 -16 - 0B 784K swapin 1 112:27 99.85% kernel > > >> 30 root 319 -16 - 0B 5120K spa->s 3 0:06 0.00% zpool-aurora-os > > >> 1157 root 1 20 0 176M 150M select 2 0:05 0.00% smbd > > >> 1154 root 1 20 0 175M 150M select 2 0:05 0.00% smbd > > >> > > >> This is a 12.4-RELEASE system. > > >> > > >> Thanks for any ideas, > > >> Nikos > > >> > > >> > > >> > > > > > > Sending the email again with the correct subject > > > > You could add -H to the top command, which will show kernel threads within > > the kernel process. > > > > Mike > > > > > > Thanks Mike, > > A kernel thread named acpi_task_n seems to be the source of the problem. This system is rather old and was ok running 12.2-REL. Maybe some update to the ACPI code?. What could I try next? > > nik@aurora:~ % top -H -S -b > last pid: 2529; load averages: 1.03, 1.03, 1.00 up 0+04:43:45 15:30:46 > 840 threads: 6 running, 820 sleeping, 14 waiting > CPU: 0.0% user, 0.0% nice, 24.6% system, 0.0% interrupt, 75.3% idle > Mem: 29M Active, 192M Inact, 1717M Wired, 13G Free > ARC: 1182M Total, 475M MFU, 608M MRU, 7744K Anon, 12M Header, 79M Other > 312M Compressed, 782M Uncompressed, 2.51:1 Ratio > Swap: 16G Total, 16G Free > > PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU COMMAND > 11 root 155 ki31 0B 64K CPU3 3 272:53 100.00% idle{idle: cpu3} > 11 root 155 ki31 0B 64K RUN 0 260:10 81.15% idle{idle: cpu0} > 0 root 8 - 0B 784K - 3 141:30 76.76% kernel{acpi_task_2} > 11 root 155 ki31 0B 64K CPU1 1 212:51 74.66% idle{idle: cpu1} > 11 root 155 ki31 0B 64K RUN 2 108:52 51.86% idle{idle: cpu2} > 0 root 8 - 0B 784K CPU2 2 116:25 24.27% kernel{acpi_task_0} > 2324 root 20 0 177M 151M select 3 0:03 0.10% smbd{smbd} > 0 root 8 - 0B 784K - 0 21:08 0.00% kernel{acpi_task_1} > 0 root -16 - 0B 784K swapin 2 0:53 0.00% kernel{swapper} > > > > > > 12.4 autoloaded acpi_wmi with dubious results: Autoloading module: acpi_wmi acpi_wmi0: on acpi0 acpi_wmi0: cannot find EC device device_attach: acpi_wmi0 attach returned 6 acpi_wmi0: on acpi0 acpi_wmi0: cannot find EC device device_attach: acpi_wmi0 attach returned 6 12.2 did not autoload it.