From: Paolo Pisati <p.pisati@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Paolo Pisati <p.pisati@gmail.com>,
linux-m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: Amiga, serial and SYSRQ
Date: Mon, 20 May 2024 19:17:33 +0200 [thread overview]
Message-ID: <ZkuFrTQDw6iM9Z7K@amaterasu.local> (raw)
In-Reply-To: <CAMuHMdXnsXk+MuGUCnPcQVbOdSGJAHiK6TBZE2r5_h15qs_azg@mail.gmail.com>
On Sun, May 19, 2024 at 04:58:17PM +0200, Geert Uytterhoeven wrote:
> Probably some of the Warp 1260 on-board hardware has its interrupt line
> asserted, causing an interrupt storm when Linux enables interrupts.
> Amiboot knows how to reset several boards to prevent this, but it
> doesn't support Warp 1260 yet.
>
> https://github.com/geertu/m68kboot/blob/master/common/amiga/linuxboot.c#L195
Doesn't the kernel print out something like "too many spurious interrupts etcetc" in
this case?
Anyhow, any debug option i could turn on? I've tried everything IRQ related, but
that didn't change a bit. I understand it requires a new fw from the board
manufacturer or a quirk in the bootloader, but i would like to get something more
verbose before i ping them.
--
bye,
p.
next prev parent reply other threads:[~2024-05-20 17:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-18 18:17 Amiga, serial and SYSRQ Paolo Pisati
2024-05-19 7:36 ` Michael Schmitz
2024-05-19 9:17 ` Geert Uytterhoeven
2024-05-19 19:22 ` Michael Schmitz
2024-05-19 20:09 ` Geert Uytterhoeven
2024-05-20 21:03 ` Michael Schmitz
2024-05-19 13:24 ` Paolo Pisati
2024-05-19 13:31 ` Geert Uytterhoeven
2024-05-19 13:54 ` Paolo Pisati
2024-05-19 19:12 ` Michael Schmitz
2024-05-20 17:08 ` Paolo Pisati
2024-05-19 14:58 ` Geert Uytterhoeven
2024-05-20 17:17 ` Paolo Pisati [this message]
2024-05-20 21:01 ` Michael Schmitz
2024-05-20 21:15 ` Andreas Schwab
2024-05-20 22:01 ` Michael Schmitz
2024-05-21 7:07 ` Geert Uytterhoeven
2024-05-21 17:56 ` Paolo Pisati
2024-05-21 21:11 ` Michael Schmitz
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=ZkuFrTQDw6iM9Z7K@amaterasu.local \
--to=p.pisati@gmail.com \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@lists.linux-m68k.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.