Re: `do_IRQ: 1.55 No irq handler for vector` on ASRock E350M1

+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" wrote: Dear Yazen, Eric, Tom, On 02/26/18 17:42, Tom Lendacky wrote: > On 2/26/2018 10:37 AM,

Re: `do_IRQ: 1.55 No irq handler for vector` on ASRock E350M1

+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" 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

Re: `do_IRQ: 1.55 No irq handler for vector` on ASRock E350M1

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

Re: `do_IRQ: 1.55 No irq handler for vector` on ASRock E350M1

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

Re: `do_IRQ: 1.55 No irq handler for vector` on ASRock E350M1

Hi Tom & Thomas, On Feb 27, 2018, at 12:42 AM, Tom Lendacky wrote: On 2/26/2018 10:37 AM, Morton, Eric wrote: Thomas, 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

Re: `do_IRQ: 1.55 No irq handler for vector` on ASRock E350M1

Hi Tom & Thomas, On Feb 27, 2018, at 12:42 AM, Tom Lendacky wrote: On 2/26/2018 10:37 AM, Morton, Eric wrote: Thomas, 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

Re: `do_IRQ: 1.55 No irq handler for vector` on ASRock E350M1

On 2/26/2018 10:37 AM, Morton, Eric wrote: > Thomas, > > 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. Thanks, Tom > > Eric > > On 2/26/18, 10:31 AM, "Borislav

Re: `do_IRQ: 1.55 No irq handler for vector` on ASRock E350M1

On 2/26/2018 10:37 AM, Morton, Eric wrote: > Thomas, > > 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. Thanks, Tom > > Eric > > On 2/26/18, 10:31 AM, "Borislav

Re: `do_IRQ: 1.55 No irq handler for vector` on ASRock E350M1

On 2/26/2018 10:31 AM, Borislav Petkov wrote: > On Mon, Feb 26, 2018 at 10:14:10AM -0600, Tom Lendacky wrote: >> On 2/24/2018 2:59 AM, Thomas Gleixner wrote: >>> On Sat, 24 Feb 2018, Paul Menzel wrote: Am 23.02.2018 um 20:09 schrieb Borislav Petkov: > On Fri, Feb 23, 2018 at 07:18:34PM

Re: `do_IRQ: 1.55 No irq handler for vector` on ASRock E350M1

On 2/26/2018 10:31 AM, Borislav Petkov wrote: > On Mon, Feb 26, 2018 at 10:14:10AM -0600, Tom Lendacky wrote: >> On 2/24/2018 2:59 AM, Thomas Gleixner wrote: >>> On Sat, 24 Feb 2018, Paul Menzel wrote: Am 23.02.2018 um 20:09 schrieb Borislav Petkov: > On Fri, Feb 23, 2018 at 07:18:34PM

Re: `do_IRQ: 1.55 No irq handler for vector` on ASRock E350M1

Thomas, Yazen dug out PLAT-21393 as sounding like this issue. I haven't had a chance to digest it. Eric On 2/26/18, 10:31 AM, "Borislav Petkov" wrote: On Mon, Feb 26, 2018 at 10:14:10AM -0600, Tom Lendacky wrote: > On 2/24/2018 2:59 AM, Thomas Gleixner wrote: > >

Re: `do_IRQ: 1.55 No irq handler for vector` on ASRock E350M1

Thomas, Yazen dug out PLAT-21393 as sounding like this issue. I haven't had a chance to digest it. Eric On 2/26/18, 10:31 AM, "Borislav Petkov" wrote: On Mon, Feb 26, 2018 at 10:14:10AM -0600, Tom Lendacky wrote: > On 2/24/2018 2:59 AM, Thomas Gleixner wrote: > > On Sat, 24 Feb

Re: `do_IRQ: 1.55 No irq handler for vector` on ASRock E350M1

On Mon, Feb 26, 2018 at 10:14:10AM -0600, Tom Lendacky wrote: > On 2/24/2018 2:59 AM, Thomas Gleixner wrote: > > On Sat, 24 Feb 2018, Paul Menzel wrote: > >> Am 23.02.2018 um 20:09 schrieb Borislav Petkov: > >>> On Fri, Feb 23, 2018 at 07:18:34PM +0100, Thomas Gleixner wrote: > Borislav is

Re: `do_IRQ: 1.55 No irq handler for vector` on ASRock E350M1

On Mon, Feb 26, 2018 at 10:14:10AM -0600, Tom Lendacky wrote: > On 2/24/2018 2:59 AM, Thomas Gleixner wrote: > > On Sat, 24 Feb 2018, Paul Menzel wrote: > >> Am 23.02.2018 um 20:09 schrieb Borislav Petkov: > >>> On Fri, Feb 23, 2018 at 07:18:34PM +0100, Thomas Gleixner wrote: > Borislav is

Re: `do_IRQ: 1.55 No irq handler for vector` on ASRock E350M1

On 2/24/2018 2:59 AM, Thomas Gleixner wrote: > On Sat, 24 Feb 2018, Paul Menzel wrote: >> Am 23.02.2018 um 20:09 schrieb Borislav Petkov: >>> On Fri, Feb 23, 2018 at 07:18:34PM +0100, Thomas Gleixner wrote: Borislav is seeing similar issues on larger AMD machines. The interrupt seems to

Re: `do_IRQ: 1.55 No irq handler for vector` on ASRock E350M1

On 2/24/2018 2:59 AM, Thomas Gleixner wrote: > On Sat, 24 Feb 2018, Paul Menzel wrote: >> Am 23.02.2018 um 20:09 schrieb Borislav Petkov: >>> On Fri, Feb 23, 2018 at 07:18:34PM +0100, Thomas Gleixner wrote: Borislav is seeing similar issues on larger AMD machines. The interrupt seems to

Re: `do_IRQ: 1.55 No irq handler for vector` on ASRock E350M1

On Sat, 24 Feb 2018, Paul Menzel wrote: > Am 23.02.2018 um 20:09 schrieb Borislav Petkov: > > On Fri, Feb 23, 2018 at 07:18:34PM +0100, Thomas Gleixner wrote: > > > Borislav is seeing similar issues on larger AMD machines. The interrupt > > > seems to come from BIOS/microcode during bringup of

Re: `do_IRQ: 1.55 No irq handler for vector` on ASRock E350M1

On Sat, 24 Feb 2018, Paul Menzel wrote: > Am 23.02.2018 um 20:09 schrieb Borislav Petkov: > > On Fri, Feb 23, 2018 at 07:18:34PM +0100, Thomas Gleixner wrote: > > > Borislav is seeing similar issues on larger AMD machines. The interrupt > > > seems to come from BIOS/microcode during bringup of

Re: `do_IRQ: 1.55 No irq handler for vector` on ASRock E350M1

On Fri, Feb 23, 2018 at 07:18:34PM +0100, Thomas Gleixner wrote: > Borislav is seeing similar issues on larger AMD machines. The interrupt > seems to come from BIOS/microcode during bringup of secondary CPUs and we > have no idea why. Paul, can you boot 4.14 and grep your dmesg for something

Re: `do_IRQ: 1.55 No irq handler for vector` on ASRock E350M1

On Fri, Feb 23, 2018 at 07:18:34PM +0100, Thomas Gleixner wrote: > Borislav is seeing similar issues on larger AMD machines. The interrupt > seems to come from BIOS/microcode during bringup of secondary CPUs and we > have no idea why. Paul, can you boot 4.14 and grep your dmesg for something

Re: `do_IRQ: 1.55 No irq handler for vector` on ASRock E350M1

Paul, On Fri, 23 Feb 2018, Paul Menzel wrote: > > On the ASRock E350M1 (AMD A50M), since Linux 4.15 I get the message below. > > do_IRQ: 1.55 No irq handler for vector Thanks for the report, but the single line of dmesg w/o any context is not really helpful. Can you please provide a larger

Re: `do_IRQ: 1.55 No irq handler for vector` on ASRock E350M1

Paul, On Fri, 23 Feb 2018, Paul Menzel wrote: > > On the ASRock E350M1 (AMD A50M), since Linux 4.15 I get the message below. > > do_IRQ: 1.55 No irq handler for vector Thanks for the report, but the single line of dmesg w/o any context is not really helpful. Can you please provide a larger