From nobody Sat Nov 26 23:49:51 2022 X-Original-To: freebsd-questions@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 4NKTpm70xRz4jSnd for ; Sun, 27 Nov 2022 00:23:28 +0000 (UTC) (envelope-from pprocacci@gmail.com) Received: from mail-oa1-x33.google.com (mail-oa1-x33.google.com [IPv6:2001:4860:4864:20::33]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4NKTpm6ZlKz3D6H for ; Sun, 27 Nov 2022 00:23:28 +0000 (UTC) (envelope-from pprocacci@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-oa1-x33.google.com with SMTP id 586e51a60fabf-1322d768ba7so9198849fac.5 for ; Sat, 26 Nov 2022 16:23:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=5fDlTf0x2OuPqJIOfu/nx851Cvx5DoXfnucq0vjGMNE=; b=DjWRBMq19LgzugAnWtGNokzjAS6fbkZQeIyHfnflQOgLN7QOMo/fVZWA36LBEQXFHW ZAxWx/g2mtZlP+BcxXP2WuSY+yPgK7BVWbd28C3/NPZ2wGfgZcFk7lEk606+RY2yQuHi HrlOXmt5pg8LZ7AnkSBbomtz8MltfgYcbFqADwOtMkTS5STuFI4fCgLJtBynLYDppSaY wwpRJE9+VD5yriN4KmMLze3K9j4BQybePHVmq9HnAs3+uQGCV85AAuL02MEQBb5x7Nvp hZ0PXFV3Ftxdq/y1wa4FSWbl47h0y4J33/yonq37KOZjzlAp5RnxM8dTy13HOEQyg7lK zM6A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=5fDlTf0x2OuPqJIOfu/nx851Cvx5DoXfnucq0vjGMNE=; b=Rxm9ig3g77wm+pSsOoKVRhM5DClGPBdlsxSbB9bWzUgukOiYF4buYE6rzghkewpNe8 7Z0e1RDWDabY6/0Abhgew1FJZH5ItTQm1PcVy2WyaV8fU8R/8kQVqjcchl8Qi9QszBkI 6F9WQd7abwBwnvd0Ha82DRO+58QVhCFpndBVd736mkFB5hs8IqLp8uFF2mHi0ujR6jkl JjQqcnQNWS3nOgJxfLTROINhJobZ2NaM0RyJo/0Whf1Djq7FnjvCpW7iVujQwn3F54Ok EWJvA4O8IqAHo/CpVkMlch06ujYahThVv+imKGRaBvV2OMAr3lLF1OcyjbXued4qVI7r YUpA== X-Gm-Message-State: ANoB5pnhHKz46WYJXI0Zv8K1fF7XgDZeL4xr9qZ4t1NMYXKdWAG89LQ2 e0fVVoFU8iEaHaoU3rhOtrOfUtkTJMY3aZaLEdWJg/A= X-Google-Smtp-Source: AA0mqf7pbHEEZjZ02luq7vJvcYHioSsYAMUESiH6KSlHZ7a9TXbAXAVG/3Frlmdcs1/+Hpakv1aQHVkLcieDfthXriw= X-Received: by 2002:a05:6870:7b89:b0:13c:e644:d7a9 with SMTP id jf9-20020a0568707b8900b0013ce644d7a9mr26846809oab.148.1669506603284; Sat, 26 Nov 2022 15:50:03 -0800 (PST) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Paul Procacci Date: Sat, 26 Nov 2022 18:49:51 -0500 Message-ID: Subject: Re: High CPU usage / high number of interrupts To: 0x1eef <0x1eef@protonmail.com> Cc: "freebsd-questions@freebsd.org" Content-Type: multipart/alternative; boundary="00000000000009fdfb05ee684c05" X-Rspamd-Queue-Id: 4NKTpm6ZlKz3D6H X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2001:4860:4864::/48, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --00000000000009fdfb05ee684c05 Content-Type: text/plain; charset="UTF-8" Can you determine if irq 128 is being shared by any devices? Usually this information can be found in `dmesg' or '/var/run/dmesg.boot'. vmstat indeed shows a device but it sometimes doesn't show all the devices sharing that IRQ. It's possible you're being misled by vmstat. Just trying to get the complete picture here of devices. ;) Thanks, Paul Procacci On Sat, Nov 26, 2022 at 6:21 PM 0x1eef <0x1eef@protonmail.com> wrote: > Hi ! > > > Out of curiosity, have you pulled a usb device one by one until the > interrupts disappear? > > I have three USB devices connected: mouse, keyboard, and an ethernet > adapter. > I tried to remove each one by one, and I did not see the interrupt rate > change. > I have also tried a cold boot without any USB devices connected, and the > interrupt rate was about the same too. > > I don't know if it could be related, but there's a trackpad connected to > the laptop that does not work. Maybe it has no relation to the issue, but > setting "hw.psm.synaptics_support" to "0" also did not help. > > When Chromium loses focus, CPU usage usually drops to 0% and does not go > above 10% - for as long as I am not using Chromium. I am using the i915 / > drm kernel modules.. I saw another report of high CPU usage related to > using those two kernel modules, but I wasn't able to identify that as the > problem in my case. > > Thanks for the help. > > Sent with Proton Mail secure email. > > ------- Original Message ------- > On Saturday, November 26th, 2022 at 8:06 PM, Paul Procacci < > pprocacci@gmail.com> wrote: > > Hey, > > Not sure of the problem, but I don't see the correlation between Chrome > and any usb driver. > Out of curiosity, have you pulled a usb device one by one until the > interrupts disappear? > > I'd be curious to know which device is slamming the system. > > Thanks, > Paul > > On Sat, Nov 26, 2022 at 6:02 PM 0x1eef <0x1eef@protonmail.com> wrote: > >> Hi, everyone! >> >> When I use Chromium, I see a high rate of CPU usage across all four >> cores. The rate can be anywhere from 20% to 50%, even above that. I am not >> doing anything intensive, just browsing twitter, reddit, YouTube or GitHub. >> It has been like this since I installed FreeBSD, but since it's not a >> blocker I have been lazy about looking into it. >> >> I don't know why it happens. I can see that there are a high number of >> interrupts on 'xhci0', and that seems to carry over to each CPU core as >> well: >> >> # vmstat -i >> interrupt total rate >> irq1: atkbd0 50 0 >> irq9: acpi0 403 0 >> cpu0:timer 30716618 98 >> cpu1:timer 25457926 81 >> cpu2:timer 34344531 109 >> cpu3:timer 25542867 81 >> irq128: xhci0 328107434 1044 >> irq130: nvme0:admin 15 0 >> irq131: nvme0:io0 701041 2 >> irq132: nvme0:io1 692045 2 >> irq133: nvme0:io2 792760 3 >> irq134: nvme0:io3 693091 2 >> irq135: hdac0 1718425 5 >> irq136: vgapci0 6273295 20 >> Total 455040501 1448 >> >> >> # dmesg | grep xhci0 >> xhci0: mem 0x95110000-0x9511ffff >> at device 20.0 on pci0 >> xhci0: 32 bytes context size, 64-bit DMA >> usbus0 on xhci0 >> >> It might also be helpful to know that I tried OpenBSD on the same >> computer but it was unusable for a similar reason: 95%+ interrupts on CPU. >> The impact that had made all tasks extremely slow. On FreeBSD it is not as >> bad, but I still think think it is not normal. >> >> Can anyone suggest what might be wrong, tips to debug, etc ? If more >> information is needed, please let me know. Thanks for your time. >> >> Best, >> 0x1eef >> >> >> > > -- > __________________ > > :(){ :|:& };: > > > -- __________________ :(){ :|:& };: --00000000000009fdfb05ee684c05 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Can you determine if irq 128 is being shared by = any devices?
Usually this information can be found in `dmesg' = or '/var/run/dmesg.boot'.

vmstat indeed shows a d= evice but it sometimes doesn't show all the devices sharing that IRQ.= =C2=A0 It's possible you're being misled by vmstat.
Just = trying to get the complete picture here of devices.=C2=A0 ;)

<= div>Thanks,
Paul Procacci

On Sat, Nov 26, 2022 at 6:21 P= M 0x1eef <0x1eef@protonmail.com= > wrote:
=
Hi !

> Out of curiosity, have you pulled a usb device one by one until the= interrupts disappear?

I hav= e three USB devices connected: mouse, keyboard, and an ethernet adapter.=C2= =A0
I tried to remove = each one by one, and I did not see the interrupt rate change.
I have also tried a cold boot witho= ut any USB devices connected, and the interrupt rate was about the same too= .

I don't know if it could be relat= ed, but there's a trackpad connected to the laptop that does not work. = Maybe it has no relation to the issue, but setting "hw.psm.synap= tics_support" to "0" also did not help.

When Chromium loses focus, CPU = usage usually drops to 0% and does not go above 10% - for as long as I am n= ot using Chromium. I am using the i915 / drm kernel modules.. I saw another= report of high CPU usage related to using those two kernel modules, but I = wasn't able to identify that as the problem in my case.

Thanks for the help.=C2=A0

=20
=20
Sent with Proton Mail secure email.

------- Original Message -------
On Saturday, November 26th, 2022 at 8:06 PM, Paul Procacci <pprocacci@gmail.com> wrote:

Hey,

Not sure of= the problem, but I don't see the correlation between Chrome and any us= b driver.
Out of curiosity, have you pulled a usb device one = by one until the interrupts disappear?

I'd be curious= to know which device is slamming the system.

Than= ks,
Paul

On Sat, Nov 26, 2022 at 6:02 PM 0x1eef <0x1eef@protonmail.com> wrote:
Hi, everyone!

When I use Ch= romium, I see a high rate of CPU usage across all four cores. The rate can = be anywhere from 20% to 50%, even above that. I am not doing anything inten= sive, just browsing twitter, reddit, YouTube or GitHub. It has been like th= is since I installed FreeBSD, but since it's not a blocker I have been = lazy about looking into it.

<= div style=3D"line-height:1.5">I don't know why it happens. I can see th= at there are a high number of interrupts on 'xhci0', and that seems= to carry over to each CPU core as well:

# vmstat -i
interrupt total rate
irq1: atkbd0 50 0
irq9: acpi0 403 0
cpu0:timer 30716618 98
cpu1:timer 25457926 81
cpu2:timer 34344531 109
cpu3:timer 25542867 81
irq128: xhci0 328107434 1044
irq130: nvme0:admin 15 0
irq131: nvme0:io0 701041 2
irq132: nvme0:io1 692045 2
irq133: nvme0:io2 792760 3
irq134: nvme0:io3 693091 2
irq135: hdac0 1718425 5
irq136: vgapci0 6273295 20
Total 455040501 1448

# dmesg | grep xhci0
xhci0: = <Intel Ice Lake-LP USB 3.1 controller> mem 0x95110000-0x9511ffff at d= evice 20.0 on pci0
xhci0: 32 bytes context size, 64-= bit DMA
usbus0 on xhci0

It might also be hel= pful to know that I tried OpenBSD on the same computer but it was unusable = for a similar reason: 95%+ interrupts on CPU. The impact that had made all = tasks extremely slow. On FreeBSD it is not as bad, but I still think think= it is not normal.

Can anyone suggest what might be wrong, tips to debug,= etc ? If more information is needed, please let me know. Thanks for your t= ime.

Best,
0x1eef




--
__________= ________

:(){ :|:& };:



--
__________________

:(){ :|:& };:
--00000000000009fdfb05ee684c05--