DING)
> + );
> +
> lapic_write_around(LAPIC_LVT1,
> (lapic_read_around(LAPIC_LVT1) &
> ~(LAPIC_LVT_MASKED | LAPIC_LVT_LEVEL_TRIGGER |
>
>
> ________________
> From: Zheng Bao
> Sent: Wednesday, May 6, 2020 8:14 AM
> To: Nico Huber ; coreboot
> Subject
From: Zheng Bao
Sent: Wednesday, May 6, 2020 8:14 AM
To: Nico Huber ; coreboot
Subject: [coreboot] Re: Linux kernel says "do_IRQ: 1.55 No irq handler for
vector"
The Payload I run between Coreboot and Linux is SeaBIOS. Do you mean SeaBIOS
should disable interrupt of all APs?
I che
Hi all,
On 03.05.2020 18:28, Nico Huber wrote:
Hi Zheng,
On 03.05.20 17:27, Zheng Bao wrote:
I am debugging the AMD Picasso board. When Linux kernel boots, there is some
error message in dmesg.
do_IRQ: 1.55 No irq handler for vector
We've noticed the same on PC Engines apu2, an older AMD
From: Nico Huber
Sent: Sunday, May 3, 2020 4:28 PM
To: Zheng Bao ; coreboot
Subject: Re: [coreboot] Linux kernel says "do_IRQ: 1.55 No irq handler for
vector"
Hi Zheng,
On 03.05.20 17:27, Zheng Bao wrote:
> I am debugging the AMD Picasso board. When Linux kernel boots,
Which board are you testing with? Picasso support is still undergoing
heavy development and we are working on getting parity with the
chromiumos fork:
https://source.chromium.org/chromiumos/chromiumos/codesearch/+/master:src/third_party/coreboot-zork/
On Sun, May 3, 2020 at 9:28 AM Zheng Bao
Hi Zheng,
On 03.05.20 17:27, Zheng Bao wrote:
> I am debugging the AMD Picasso board. When Linux kernel boots, there is some
> error message in dmesg.
> do_IRQ: 1.55 No irq handler for vector
>
> The kernel can still boot.
> What does this message mean? Can I just ignore this message?
well,
6 matches
Mail list logo
