Re: ACPI timeouts when enabling KASAN

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Apr 15, 2024 at 2:52 PM Igor Mammedov <imammedo@xxxxxxxxxx> wrote:
>
> On Sun, 14 Apr 2024 04:37:24 -0400
> "Michael S. Tsirkin" <mst@xxxxxxxxxx> wrote:
>
> > On Fri, Apr 12, 2024 at 11:43:22PM +0200, Ricardo Ribalda wrote:
> > > Hi
> > >
> > > I am using virtme to do some CI around linux-media.
> > >
> > > Everything works as expected, but when I enable KASAN, I am starting
> > > to get a lot of timeouts when the Method _PRT is executed. Eg:
> > >
> > > [   56.335875] ACPI Error: Aborting method \_SB.PCI0._PRT due to
> > > previous error (AE_AML_LOOP_TIMEOUT) (20230628/psparse-529)
> > > [   56.529826] ACPI Error: Method execution failed \_SB.PCI0._PRT due
> > > to previous error (AE_AML_LOOP_TIMEOUT) (20230628/uteval-68)
> > > [   56.532391] virtio-pci 0000:00:02.0: can't derive routing for PCI INT A
> > > [   56.532823] virtio-pci 0000:00:02.0: PCI INT A: no GSI
> > > [   86.877471] ACPI Error: Aborting method \_SB.PCI0._PRT due to
> > > previous error (AE_AML_LOOP_TIMEOUT) (20230628/psparse-529)
> > > [   87.073854] ACPI Error: Method execution failed \_SB.PCI0._PRT due
> > > to previous error (AE_AML_LOOP_TIMEOUT) (20230628/uteval-68)
> > > [   87.075550] virtio-pci 0000:00:04.0: can't derive routing for PCI INT A
> > > [   87.075810] virtio-pci 0000:00:04.0: PCI INT A: no GSI
> > >
> > > 0000:00:04.0 and 0000:00:02.0 are virtio devices (console and 9p-filesystem)
> > >
> > > If I increase the timeout (ACPI_MAX_LOOP_TIMEOUT), then the Method is
> > > always executed, but it is very annoying that I have to wait more than
> > > 5 minutes to start the vm.
> > >
> > > Despite not having kvm enabled, the machine is quite decent, so I
> > > would expect that it could run that method relatively fast.
> > >
> > > Do you have any hint of what I should be looking at?
>
> The way QEMU generates _PRT haven't been changed for ages,
> it's not likely to be a culprit.
>
> CCing Rafael who might have an idea why ACPI misbehaves.

It looks like the method evaluation time increases with KASAN enabled
and it gets aborted due to exceeding the evaluation time limit.

Thanks!





[Index of Archives]     [KVM Development]     [Libvirt Development]     [Libvirt Users]     [CentOS Virtualization]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux