linux-kernel - Re: FreeNAS VM disk access errors, bisected to commit 6f1a4891a592

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Sat, 18 Apr 2020 11:44:55 +0200
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Marc Dionne <marc.c.dionne@...il.com>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        x86@...nel.org
Subject: Re: FreeNAS VM disk access errors, bisected to commit 6f1a4891a592

Marc,

Marc Dionne <marc.c.dionne@...il.com> writes:
> On Fri, Apr 17, 2020 at 5:19 PM Thomas Gleixner <tglx@...utronix.de> wrote:
>> That makes me assume that the staged approach of changing affinity for
>> this non-maskable MSI mess makes your particular hypervisor unhappy.
>>
>> Are there any messages like this:
>>
>>  "do_IRQ: 0.83 No irq handler for vector"
>
> I haven't seen those although I only have a VNC console that scrolls
> by rather fast.
> I did see a report from someone running Ubuntu 18.04 which had this
> after the initial errors:
>
>   do_IRQ: 2.35 No irq handler for vector
>   ata1.00: revalidation failed (error=-5)

I expected that and it points to an issue on the HV side either in
affinity management or in the local APIC emulation. 

Thanks,

        tglx