linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Re: Bug report for kernel v4.15-rc8+
@ 2021-12-17 13:31 blinkin
  0 siblings, 0 replies; 5+ messages in thread
From: blinkin @ 2021-12-17 13:31 UTC (permalink / raw)
  To: Thomas Gleixner; +Cc: linux-kernel, Rafael J. Wysocki, Len Brown, linux-acpi

hello, any news on this?

----- Messaggio originale -----
Da: "Thomas Gleixner" <tglx@linutronix.de>
A: blinkin@email.it
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>, "Rafael J. Wysocki" <rafael@kernel.org>, "Len Brown" <lenb@kernel.org>, linux-acpi@vger.kernel.org
Inviato: Mercoledì, 11 agosto 2021 16:20:41
Oggetto: Re: Bug report for kernel v4.15-rc8+

On Wed, Aug 11 2021 at 15:51, blinkin@email.it wrote:
> 1) You're booting with an out of tree module
>
>   Uninstalled virtualbox, reproduced same behavior without the module.
>   dmesg outputs attached with and without the workaround
>   (dmesg_novboxdrv_clean.txt and dmesg_novboxdrv_irqaffinity0.txt)

Ok.

> 2) Please provide information what is consuming 90% of a CPU
>
>   top shows a kworker process consistently at 50% without the
>   workaround, 60% with the workaround. No significant activity amounts
>   from other processes.  Sometimes that 50% is split between two
>   kworker processes for a short time.  CPU core #0 activity is a
>   constant 60% without the workaround, 90% with the workaround

That's broken. /proc/interrupts gives some hint:

1) Stock kernel

>             CPU0       CPU1       CPU2       CPU3       
>    0:         10          0          0          0  IR-IO-APIC    2-edge      timer
>    1:          0          0          0          9  IR-IO-APIC    1-edge      i8042
>    8:          0          1          0          0  IR-IO-APIC    8-edge      rtc0
>    9:          0     923411          0          0  IR-IO-APIC    9-fasteoi   acpi

900k ACPI interrupts right after boot

>             CPU0       CPU1       CPU2       CPU3       
>    0:         10          0          0          0  IR-IO-APIC    2-edge      timer
>    1:          0          0          0         11  IR-IO-APIC    1-edge      i8042
>    8:          0          1          0          0  IR-IO-APIC    8-edge      rtc0
>    9:          0    4869059          0          0  IR-IO-APIC    9-fasteoi   acpi

One minute later it's 4.8M

With affinity forced to CPU0 it's even more:

>             CPU0       CPU1       CPU2       CPU3       
>    0:         10          0          0          0  IR-IO-APIC    2-edge      timer
>    1:          9          0          0          0  IR-IO-APIC    1-edge      i8042
>    8:          1          0          0          0  IR-IO-APIC    8-edge      rtc0
>    9:    7576456          0          0          0  IR-IO-APIC    9-fasteoi   acpi

7.5M right after boot

>             CPU0       CPU1       CPU2       CPU3       
>    0:         10          0          0          0  IR-IO-APIC    2-edge      timer
>    1:         11          0          0          0  IR-IO-APIC    1-edge      i8042
>    8:          1          0          0          0  IR-IO-APIC    8-edge      rtc0
>    9:   10992420          0          0          0  IR-IO-APIC    9-fasteoi   acpi

10.9M after one minute. Though the delta between right after boot and 1
minute later is in the same ballpark.

Cc'ed the ACPI people for clues.

Thanks,

        tglx

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Bug report for kernel v4.15-rc8+
  2022-06-10  9:52 blinkin
@ 2022-06-10 13:17 ` Rafael J. Wysocki
  0 siblings, 0 replies; 5+ messages in thread
From: Rafael J. Wysocki @ 2022-06-10 13:17 UTC (permalink / raw)
  To: blinkin
  Cc: Thomas Gleixner, linux-kernel, Rafael J. Wysocki, Len Brown, linux-acpi

On Fri, Jun 10, 2022 at 11:52 AM <blinkin@email.it> wrote:
>
> hello, any news on this?
>
> ----- Messaggio originale -----
> Da: "Thomas Gleixner" <tglx@linutronix.de>
> A: blinkin@email.it
> Cc: "linux-kernel" <linux-kernel@vger.kernel.org>, "Rafael J. Wysocki" <rafael@kernel.org>, "Len Brown" <lenb@kernel.org>, linux-acpi@vger.kernel.org
> Inviato: Mercoledì, 11 agosto 2021 16:20:41
> Oggetto: Re: Bug report for kernel v4.15-rc8+
>
> On Wed, Aug 11 2021 at 15:51, blinkin@email.it wrote:
> > 1) You're booting with an out of tree module
> >
> >   Uninstalled virtualbox, reproduced same behavior without the module.
> >   dmesg outputs attached with and without the workaround
> >   (dmesg_novboxdrv_clean.txt and dmesg_novboxdrv_irqaffinity0.txt)
>
> Ok.
>
> > 2) Please provide information what is consuming 90% of a CPU
> >
> >   top shows a kworker process consistently at 50% without the
> >   workaround, 60% with the workaround. No significant activity amounts
> >   from other processes.  Sometimes that 50% is split between two
> >   kworker processes for a short time.  CPU core #0 activity is a
> >   constant 60% without the workaround, 90% with the workaround
>
> That's broken. /proc/interrupts gives some hint:
>
> 1) Stock kernel
>
> >             CPU0       CPU1       CPU2       CPU3
> >    0:         10          0          0          0  IR-IO-APIC    2-edge      timer
> >    1:          0          0          0          9  IR-IO-APIC    1-edge      i8042
> >    8:          0          1          0          0  IR-IO-APIC    8-edge      rtc0
> >    9:          0     923411          0          0  IR-IO-APIC    9-fasteoi   acpi
>
> 900k ACPI interrupts right after boot
>
> >             CPU0       CPU1       CPU2       CPU3
> >    0:         10          0          0          0  IR-IO-APIC    2-edge      timer
> >    1:          0          0          0         11  IR-IO-APIC    1-edge      i8042
> >    8:          0          1          0          0  IR-IO-APIC    8-edge      rtc0
> >    9:          0    4869059          0          0  IR-IO-APIC    9-fasteoi   acpi
>
> One minute later it's 4.8M
>
> With affinity forced to CPU0 it's even more:
>
> >             CPU0       CPU1       CPU2       CPU3
> >    0:         10          0          0          0  IR-IO-APIC    2-edge      timer
> >    1:          9          0          0          0  IR-IO-APIC    1-edge      i8042
> >    8:          1          0          0          0  IR-IO-APIC    8-edge      rtc0
> >    9:    7576456          0          0          0  IR-IO-APIC    9-fasteoi   acpi
>
> 7.5M right after boot
>
> >             CPU0       CPU1       CPU2       CPU3
> >    0:         10          0          0          0  IR-IO-APIC    2-edge      timer
> >    1:         11          0          0          0  IR-IO-APIC    1-edge      i8042
> >    8:          1          0          0          0  IR-IO-APIC    8-edge      rtc0
> >    9:   10992420          0          0          0  IR-IO-APIC    9-fasteoi   acpi
>
> 10.9M after one minute. Though the delta between right after boot and 1
> minute later is in the same ballpark.
>
> Cc'ed the ACPI people for clues.

Looks like a GPE storm to me.

I would look into /sys/firmware/acpi/interrupts/* for hints.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Bug report for kernel v4.15-rc8+
@ 2022-06-10  9:52 blinkin
  2022-06-10 13:17 ` Rafael J. Wysocki
  0 siblings, 1 reply; 5+ messages in thread
From: blinkin @ 2022-06-10  9:52 UTC (permalink / raw)
  To: Thomas Gleixner; +Cc: linux-kernel, Rafael J. Wysocki, Len Brown, linux-acpi

hello, any news on this?

----- Messaggio originale -----
Da: "Thomas Gleixner" <tglx@linutronix.de>
A: blinkin@email.it
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>, "Rafael J. Wysocki" <rafael@kernel.org>, "Len Brown" <lenb@kernel.org>, linux-acpi@vger.kernel.org
Inviato: Mercoledì, 11 agosto 2021 16:20:41
Oggetto: Re: Bug report for kernel v4.15-rc8+

On Wed, Aug 11 2021 at 15:51, blinkin@email.it wrote:
> 1) You're booting with an out of tree module
>
>   Uninstalled virtualbox, reproduced same behavior without the module.
>   dmesg outputs attached with and without the workaround
>   (dmesg_novboxdrv_clean.txt and dmesg_novboxdrv_irqaffinity0.txt)

Ok.

> 2) Please provide information what is consuming 90% of a CPU
>
>   top shows a kworker process consistently at 50% without the
>   workaround, 60% with the workaround. No significant activity amounts
>   from other processes.  Sometimes that 50% is split between two
>   kworker processes for a short time.  CPU core #0 activity is a
>   constant 60% without the workaround, 90% with the workaround

That's broken. /proc/interrupts gives some hint:

1) Stock kernel

>             CPU0       CPU1       CPU2       CPU3       
>    0:         10          0          0          0  IR-IO-APIC    2-edge      timer
>    1:          0          0          0          9  IR-IO-APIC    1-edge      i8042
>    8:          0          1          0          0  IR-IO-APIC    8-edge      rtc0
>    9:          0     923411          0          0  IR-IO-APIC    9-fasteoi   acpi

900k ACPI interrupts right after boot

>             CPU0       CPU1       CPU2       CPU3       
>    0:         10          0          0          0  IR-IO-APIC    2-edge      timer
>    1:          0          0          0         11  IR-IO-APIC    1-edge      i8042
>    8:          0          1          0          0  IR-IO-APIC    8-edge      rtc0
>    9:          0    4869059          0          0  IR-IO-APIC    9-fasteoi   acpi

One minute later it's 4.8M

With affinity forced to CPU0 it's even more:

>             CPU0       CPU1       CPU2       CPU3       
>    0:         10          0          0          0  IR-IO-APIC    2-edge      timer
>    1:          9          0          0          0  IR-IO-APIC    1-edge      i8042
>    8:          1          0          0          0  IR-IO-APIC    8-edge      rtc0
>    9:    7576456          0          0          0  IR-IO-APIC    9-fasteoi   acpi

7.5M right after boot

>             CPU0       CPU1       CPU2       CPU3       
>    0:         10          0          0          0  IR-IO-APIC    2-edge      timer
>    1:         11          0          0          0  IR-IO-APIC    1-edge      i8042
>    8:          1          0          0          0  IR-IO-APIC    8-edge      rtc0
>    9:   10992420          0          0          0  IR-IO-APIC    9-fasteoi   acpi

10.9M after one minute. Though the delta between right after boot and 1
minute later is in the same ballpark.

Cc'ed the ACPI people for clues.

Thanks,

        tglx

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Bug report for kernel v4.15-rc8+
  2021-08-11 14:20         ` Thomas Gleixner
@ 2021-09-24 10:23           ` blinkin
  0 siblings, 0 replies; 5+ messages in thread
From: blinkin @ 2021-09-24 10:23 UTC (permalink / raw)
  To: Thomas Gleixner; +Cc: linux-kernel, Rafael J. Wysocki, Len Brown, linux-acpi

hello, any news on this?

----- Messaggio originale -----
Da: "Thomas Gleixner" <tglx@linutronix.de>
A: blinkin@email.it
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>, "Rafael J. Wysocki" <rafael@kernel.org>, "Len Brown" <lenb@kernel.org>, linux-acpi@vger.kernel.org
Inviato: Mercoledì, 11 agosto 2021 16:20:41
Oggetto: Re: Bug report for kernel v4.15-rc8+

On Wed, Aug 11 2021 at 15:51, blinkin@email.it wrote:
> 1) You're booting with an out of tree module
>
>   Uninstalled virtualbox, reproduced same behavior without the module.
>   dmesg outputs attached with and without the workaround
>   (dmesg_novboxdrv_clean.txt and dmesg_novboxdrv_irqaffinity0.txt)

Ok.

> 2) Please provide information what is consuming 90% of a CPU
>
>   top shows a kworker process consistently at 50% without the
>   workaround, 60% with the workaround. No significant activity amounts
>   from other processes.  Sometimes that 50% is split between two
>   kworker processes for a short time.  CPU core #0 activity is a
>   constant 60% without the workaround, 90% with the workaround

That's broken. /proc/interrupts gives some hint:

1) Stock kernel

>             CPU0       CPU1       CPU2       CPU3       
>    0:         10          0          0          0  IR-IO-APIC    2-edge      timer
>    1:          0          0          0          9  IR-IO-APIC    1-edge      i8042
>    8:          0          1          0          0  IR-IO-APIC    8-edge      rtc0
>    9:          0     923411          0          0  IR-IO-APIC    9-fasteoi   acpi

900k ACPI interrupts right after boot

>             CPU0       CPU1       CPU2       CPU3       
>    0:         10          0          0          0  IR-IO-APIC    2-edge      timer
>    1:          0          0          0         11  IR-IO-APIC    1-edge      i8042
>    8:          0          1          0          0  IR-IO-APIC    8-edge      rtc0
>    9:          0    4869059          0          0  IR-IO-APIC    9-fasteoi   acpi

One minute later it's 4.8M

With affinity forced to CPU0 it's even more:

>             CPU0       CPU1       CPU2       CPU3       
>    0:         10          0          0          0  IR-IO-APIC    2-edge      timer
>    1:          9          0          0          0  IR-IO-APIC    1-edge      i8042
>    8:          1          0          0          0  IR-IO-APIC    8-edge      rtc0
>    9:    7576456          0          0          0  IR-IO-APIC    9-fasteoi   acpi

7.5M right after boot

>             CPU0       CPU1       CPU2       CPU3       
>    0:         10          0          0          0  IR-IO-APIC    2-edge      timer
>    1:         11          0          0          0  IR-IO-APIC    1-edge      i8042
>    8:          1          0          0          0  IR-IO-APIC    8-edge      rtc0
>    9:   10992420          0          0          0  IR-IO-APIC    9-fasteoi   acpi

10.9M after one minute. Though the delta between right after boot and 1
minute later is in the same ballpark.

Cc'ed the ACPI people for clues.

Thanks,

        tglx

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Bug report for kernel v4.15-rc8+
       [not found]       ` <1437097118.2114098.1628689870926.JavaMail.zimbra@email.it>
@ 2021-08-11 14:20         ` Thomas Gleixner
  2021-09-24 10:23           ` blinkin
  0 siblings, 1 reply; 5+ messages in thread
From: Thomas Gleixner @ 2021-08-11 14:20 UTC (permalink / raw)
  To: blinkin; +Cc: linux-kernel, Rafael J. Wysocki, Len Brown, linux-acpi

On Wed, Aug 11 2021 at 15:51, blinkin@email.it wrote:
> 1) You're booting with an out of tree module
>
>   Uninstalled virtualbox, reproduced same behavior without the module.
>   dmesg outputs attached with and without the workaround
>   (dmesg_novboxdrv_clean.txt and dmesg_novboxdrv_irqaffinity0.txt)

Ok.

> 2) Please provide information what is consuming 90% of a CPU
>
>   top shows a kworker process consistently at 50% without the
>   workaround, 60% with the workaround. No significant activity amounts
>   from other processes.  Sometimes that 50% is split between two
>   kworker processes for a short time.  CPU core #0 activity is a
>   constant 60% without the workaround, 90% with the workaround

That's broken. /proc/interrupts gives some hint:

1) Stock kernel

>             CPU0       CPU1       CPU2       CPU3       
>    0:         10          0          0          0  IR-IO-APIC    2-edge      timer
>    1:          0          0          0          9  IR-IO-APIC    1-edge      i8042
>    8:          0          1          0          0  IR-IO-APIC    8-edge      rtc0
>    9:          0     923411          0          0  IR-IO-APIC    9-fasteoi   acpi

900k ACPI interrupts right after boot

>             CPU0       CPU1       CPU2       CPU3       
>    0:         10          0          0          0  IR-IO-APIC    2-edge      timer
>    1:          0          0          0         11  IR-IO-APIC    1-edge      i8042
>    8:          0          1          0          0  IR-IO-APIC    8-edge      rtc0
>    9:          0    4869059          0          0  IR-IO-APIC    9-fasteoi   acpi

One minute later it's 4.8M

With affinity forced to CPU0 it's even more:

>             CPU0       CPU1       CPU2       CPU3       
>    0:         10          0          0          0  IR-IO-APIC    2-edge      timer
>    1:          9          0          0          0  IR-IO-APIC    1-edge      i8042
>    8:          1          0          0          0  IR-IO-APIC    8-edge      rtc0
>    9:    7576456          0          0          0  IR-IO-APIC    9-fasteoi   acpi

7.5M right after boot

>             CPU0       CPU1       CPU2       CPU3       
>    0:         10          0          0          0  IR-IO-APIC    2-edge      timer
>    1:         11          0          0          0  IR-IO-APIC    1-edge      i8042
>    8:          1          0          0          0  IR-IO-APIC    8-edge      rtc0
>    9:   10992420          0          0          0  IR-IO-APIC    9-fasteoi   acpi

10.9M after one minute. Though the delta between right after boot and 1
minute later is in the same ballpark.

Cc'ed the ACPI people for clues.

Thanks,

        tglx

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2022-06-10 13:18 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-12-17 13:31 Bug report for kernel v4.15-rc8+ blinkin
  -- strict thread matches above, loose matches on Subject: below --
2022-06-10  9:52 blinkin
2022-06-10 13:17 ` Rafael J. Wysocki
     [not found] <629765464.1655403.1628264743080.JavaMail.zimbra@email.it>
     [not found] ` <87tujxssp2.ffs@tglx>
     [not found]   ` <217397770.2008922.1628604301644.JavaMail.zimbra@email.it>
     [not found]     ` <877dgtql9v.ffs@tglx>
     [not found]       ` <1437097118.2114098.1628689870926.JavaMail.zimbra@email.it>
2021-08-11 14:20         ` Thomas Gleixner
2021-09-24 10:23           ` blinkin

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).