This looks like a kernel bug but regardless I see a lockup when I
attempt to do certain operations :
phobos#
phobos# ls -1trb ..
linux-5.7-rc2.compile.log
linux-5.7-rc2.make_modules.log
linux-5.7-rc2.make_modules_install.log
linux-5.7-rc2.make_install.log
linux-5.7-rc2
linux-5.7-rc2.make_install.log2
linux-5.7-rc2.env
phobos#
phobos#
phobos# /usr/bin/time -p /usr/bin/nice -n +15 make install 2>&1 | \
> tee ../linux-5.7-rc2.make_install.log3
sh ./arch/sparc/boot/install.sh 5.7.0-rc2 arch/sparc/boot/zImage \
System.map "/boot"
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc2
/boot/vmlinuz-5.7.0-rc2
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc2
/boot/vmlinuz-5.7.0-rc2
update-initramfs: Generating /boot/initrd.img-5.7.0-rc2
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 5.7.0-rc2
/boot/vmlinuz-5.7.0-rc2
[ 1319.107865] watchdog: BUG: soft lockup - CPU#0 stuck for 22s!
[grub-probe:2025]
[ 1319.204084] Modules linked in: sg(E) envctrl(E) display7seg(E)
flash(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E)
jbd2(E) crc32c_generic(E) sd_mod(E) ata_generic(E) pata_cmd64x(E)
sym53c8xx(E) libata(E) scsi_transport_spi(E) scsi_mod(E) sunhme(E)
[ 1319.516550] CPU: 0 PID: 2025 Comm: grub-probe Tainted: G E
5.5.0-2-sparc64 #1 Debian 5.5.17-1
[ 1319.645861] TSTATE: 0000009911001603 TPC: 00000000008804e0 TNPC:
00000000008804e4 Y: 00000000 Tainted: G E
[ 1319.793536] TPC: <misc_open+0x40/0x180>
[ 1319.843923] g0: 0000000000000000 g1: 000000001000a838 g2:
0000000000000000 g3: 0000000000c43720
[ 1319.958414] g4: fffff8003beb3240 g5: 0000000000000038 g6:
fffff800343e4000 g7: 000000000e596bf0
[ 1320.072894] o0: 0000000000d9c458 o1: fffff800343e790c o2:
fffff8003a2559d0 o3: 0000000000000000
[ 1320.187374] o4: 0000000000000000 o5: 0000000000000000 sp:
fffff800343e6fa1 ret_pc: 00000000008804c0
[ 1320.306434] RPC: <misc_open+0x20/0x180>
[ 1320.356848] l0: 0000000000d9c400 l1: 0000000000000000 l2:
000000000063a500 l3: 00000000eff80000
[ 1320.471339] l4: 0000000000000000 l5: ffffffffffffff9c l6:
fffff800343e4000 l7: 0000000000632b60
[ 1320.585819] i0: fffff800347c3018 i1: fffff80037c1b300 i2:
0000000000d9c400 i3: 0000000000d9c470
[ 1320.700299] i4: 00000000000000ec i5: 000000001000a820 i6:
fffff800343e7051 i7: 000000000063b0f8
[ 1320.814784] I7: <chrdev_open+0x78/0x160>
[ 1320.866335] Call Trace:
[ 1320.898369] [000000000063b0f8] chrdev_open+0x78/0x160
[ 1320.965978] [0000000000631398] do_dentry_open+0x158/0x440
[ 1321.038119] [00000000006326e8] vfs_open+0x28/0x40
[ 1321.101142] [0000000000646658] path_openat+0x4d8/0x1420
[ 1321.171006] [00000000006486b0] do_filp_open+0x50/0xc0
[ 1321.238588] [0000000000632a30] do_sys_open+0x170/0x260
[ 1321.307317] [0000000000632b80] sys_openat+0x20/0x40
[ 1321.372626] [0000000000406154] linux_sparc_syscall+0x34/0x44
This is completely repeatable when I try to install a new initrd image.
I will try to manually hack the grub.cfg and see if I can boot the
linux 5.7-rc2 initrd and other goodness.
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional
