From: "Morton, Eric" <Eric.Morton@amd.com>
To: Paul Menzel <pmenzel+linux-irq@molgen.mpg.de>,
"Lendacky, Thomas" <Thomas.Lendacky@amd.com>,
Borislav Petkov <bp@alien8.de>,
"Ghannam, Yazen" <Yazen.Ghannam@amd.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Gorishek, Frank" <Frank.Gorishek@amd.com>
Subject: Re: `do_IRQ: 1.55 No irq handler for vector` on ASRock E350M1
Date: Thu, 29 Mar 2018 20:57:35 +0000 [thread overview]
Message-ID: <F2FE7773-77E5-450A-BD27-CEF1A592D06D@amd.com> (raw)
In-Reply-To: <81178e95-6aa4-69c9-4557-ba8bf929c8ff@molgen.mpg.de>
+Frank G.
Eric
By reading this e-mail, you are consenting to agree with the opinions disclosed within.
On 3/29/18, 3:29 AM, "Paul Menzel" <pmenzel+linux-irq@molgen.mpg.de> wrote:
Dear Yazen, Eric, Tom,
On 02/26/18 17:42, Tom Lendacky wrote:
> On 2/26/2018 10:37 AM, Morton, Eric wrote:
>> Yazen dug out PLAT-21393 as sounding like this issue. I haven't had
>> a chance to digest it.
>
> Yes, internally to AMD, that was the bug that tracked the issue I
> was referring to.
If you could point me to more details how to fix this in AGESA, I could
probably fix the version in coreboot to fix the issue.
Kind regards,
Paul
next prev parent reply other threads:[~2018-03-29 20:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 15:29 `do_IRQ: 1.55 No irq handler for vector` on ASRock E350M1 Paul Menzel
2018-02-23 18:18 ` Thomas Gleixner
2018-02-23 19:09 ` Borislav Petkov
2018-02-24 8:06 ` Paul Menzel
2018-02-24 8:59 ` Thomas Gleixner
2018-02-26 16:14 ` Tom Lendacky
2018-02-26 16:31 ` Borislav Petkov
2018-02-26 16:37 ` Morton, Eric
2018-02-26 16:42 ` Tom Lendacky
2018-03-29 7:21 ` Kai Heng Feng
2018-03-29 8:29 ` Paul Menzel
2018-03-29 20:57 ` Morton, Eric [this message]
2018-02-26 16:39 ` Tom Lendacky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F2FE7773-77E5-450A-BD27-CEF1A592D06D@amd.com \
--to=eric.morton@amd.com \
--cc=Frank.Gorishek@amd.com \
--cc=Thomas.Lendacky@amd.com \
--cc=Yazen.Ghannam@amd.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pmenzel+linux-irq@molgen.mpg.de \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox