From: Paolo Pisati <p.pisati@gmail.com>
To: linux-m68k <linux-m68k@lists.linux-m68k.org>
Subject: Amiga, serial and SYSRQ
Date: Sat, 18 May 2024 20:17:49 +0200 [thread overview]
Message-ID: <ZkjwzVwYeQtyAPrL@amaterasu.local> (raw)
Hi,
what's the key sequence to trigger SYSRQ on Amiga? And what's the sequence if
i'm redirecting the console via serial?
Some context: i'm trying to collect a backtrace from my Amiga 1200 + Warp
1260[1] + flicker fixer that refuses to boot and shows a solid grey screen.
By using a serial, i've seen it booting up to:
ABCDGHIJK
Linux version 6.6.30-amiga-00006-g809aa9a54cba (flag@amaterasu.local) (m68k-linux-gcc (GCC) 13.1.0, GNU ld (GNU Binutils) 4
Saving 454 bytes of bootinfo
printk: console [debug0] enabled
printk: Too late to register bootconsole debug-1
Amiga hardware found: [A1200] VIDEO BLITTER AUDIO FLOPPY A1200_IDE KEYBOARD MOUSE SERIAL PARALLEL A2000_CLK CHIP_RAM PAULA
Zone ranges:
DMA [mem 0x0000000040000000-0x000004dfffffffff]
Normal empty
Movable zone start for each node
Early memory node ranges
node 0: [mem 0x0000000040000000-0x000000004dffffff]
Initmem setup node 0 [mem 0x0000000040000000-0x000000004dffffff]
pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
pcpu-alloc: [0] 0
Kernel command line: root=/dev/sda4 debug=ser earlyprintk console=ttyS0,9600n8
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes, linear)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes, linear)
Sorting __ex_table...
Built 1 zonelists, mobility grouping on. Total pages: 56840
mem auto-init: stack:all(zero), heap alloc:off, heap free:off
Memory: 221284K/229376K available (3753K kernel code, 472K rwdata, 1184K rodata, 172K init, 149K bss, 8092K reserved, 0K c)
SLUB: HWalign=16, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
start_kernel::941
start_kernel::976
NR_IRQS: 32
clocksource: ciab: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 2694272661900 ns
start_kernel::990
start_kernel::994
start_kernel::998
start_kernel::1000
start_kernel::1006
start_kernel::1009
I've added some printk around init/main.c::start_kernel() and it *appears* to be
hanging in "local_irq_enable();".
I've tried all stable LTS kernels from 4.4.y to 6.6.y, and they all shows the same
exact symptoms.
Hope it rings a bell.
1: https://amigawarp.eu/product/warp-1260-board-for-amiga-1200/
--
bye,
p.
next reply other threads:[~2024-05-18 18:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-18 18:17 Paolo Pisati [this message]
2024-05-19 7:36 ` Amiga, serial and SYSRQ 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
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=ZkjwzVwYeQtyAPrL@amaterasu.local \
--to=p.pisati@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).