[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3aec44983d0ca0b57bb03dfa677a2a695f1e707b.camel@infradead.org>
Date: Wed, 18 Nov 2020 10:52:32 +0000
From: David Woodhouse <dwmw2@...radead.org>
To: Suravee Suthikulpanit <suravee.suthikulpanit@....com>,
Tom Lendacky <thomas.lendacky@....com>,
Thomas Gleixner <tglx@...utronix.de>,
Borislav Petkov <bp@...en8.de>
Cc: linux-kernel@...r.kernel.org, x86 <x86@...nel.org>,
Qian Cai <cai@...hat.com>, Joerg Roedel <joro@...tes.org>
Subject: Re: [EXTERNAL] [tip: x86/apic] x86/io_apic: Cleanup
trigger/polarity helpers
On Wed, 2020-11-18 at 17:29 +0700, Suravee Suthikulpanit wrote:
> I might need your help debugging this issue. I'm seeing the following error:
>
> [ 14.005937] irq 29, desc: 00000000d200500b, depth: 0, count: 0, unhandled: 0
> [ 14.006234] ->handle_irq(): 00000000eab4b6eb, handle_bad_irq+0x0/0x230
Where's that line coming from?
> [ 14.006234] ->irq_data.chip(): 000000001cce6d6b, intcapxt_controller+0x0/0x120
> [ 14.006234] ->action(): 0000000083bfd734
> [ 14.006234] ->action->handler(): 0000000094806345, amd_iommu_int_handler+0x0/0x10
> [ 14.006234] unexpected IRQ trap at vector 1d
>
> Do you have any idea what might have gone wrong here?
Hm, vector 0x1d is vector 29. It's also IRQ 29. I wonder if that's a coincidence.
Can you make intcapxt_irqdomain_activate() print the 64-bit value that
it's writing to the intcapxt registers?
Download attachment "smime.p7s" of type "application/x-pkcs7-signature" (5174 bytes)
Powered by blists - more mailing lists