Public bug reported:
While doing a test installation using stonking snapshot 1,
I noticed the following Call traces during boot up:
See 1) and 2) (happens twice during boot).
I was however able to complete and installation on an s390x LPAR (using
FCP/multipath).
[ 0.261295] Linux version 7.0.0-14-generic (buildd@bos03-s390x-009)
(s390x-linux-gnu-gcc (Ubuntu 15.2.0-16ubuntu1) 15.2.0, GNU ld (GNU Binutils for
Ubuntu) 2.46) #14-Ubuntu SMP PREEMPT Mon Apr 13 10:02:47 UTC 2026 (Ubuntu
7.0.0-14.14-generic 7.0.0)
[ 0.261297] setup: Linux is running natively in 64-bit mode
[ 0.265829] setup: The maximum memory size is 32768MB
[ 0.265830] setup: Relocating AMODE31 section of size 0x00003000
[ 0.265871] cpu: 8 configured CPUs, 0 standby CPUs
[ 0.265877] cpu: The CPU configuration topology of the machine is: 0 0 5 2 2
12 / 4
[ 0.266313] Write protected kernel read-only data: 26356k
[ 0.273786] Zone ranges:
[ 0.273787] DMA [mem 0x0000000000000000-0x000000007fffffff]
[ 0.273789] Normal [mem 0x0000000080000000-0x00000007ffffffff]
[ 0.273792] Device empty
[ 0.273793] Movable zone start for each node
[ 0.273793] Early memory node ranges
[ 0.273793] node 0: [mem 0x0000000000000000-0x00000007ffffffff]
[ 0.273796] Initmem setup node 0 [mem 0x0000000000000000-0x00000007ffffffff]
[ 0.475526] percpu: Embedded 56 pages/cpu s105216 r8192 d115968 u229376
[ 0.475793] Kernel command line: --- /dev/ram0 ro
[ 0.475793]
[ 0.475832] Unknown kernel command line parameters "--- /dev/ram0", will be
passed to user space.
[ 0.476168] random: crng init done
[ 0.476169] printk: log_buf_len individual max cpu contribution: 4096 bytes
...
1)
[ 249.400100] INFO: task modprobe:763 blocked for more than 122 seconds.
[ 249.400115] Not tainted 7.0.0-14-generic #14-Ubuntu
[ 249.400117] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[ 249.400118] task:modprobe state:D stack:0 pid:763 tgid:763
ppid:623 task_flags:0x400100 flags:0x00000000
[ 249.400124] Call Trace:
[ 249.400126] [<000002f3cff592ba>] __schedule+0x2fa/0x730
[ 249.400135] [<000002f3cff5972c>] schedule+0x3c/0xc0
[ 249.400138] [<000002f3cff6270c>] schedule_timeout+0xcc/0x140
[ 249.400141] [<000002f3cff5abf2>] wait_for_completion+0xb2/0x150
[ 249.400144] [<000002f34f373e16>] sclp_ftp_cmd+0x86/0x110 [hmcdrv]
[ 249.400153] [<000002f34f3735a0>] hmcdrv_cache_cmd+0x40/0xc0 [hmcdrv]
[ 249.400157] [<000002f34f372a02>] hmcdrv_ftp_do+0x62/0xf0 [hmcdrv]
[ 249.400160] [<000002f34f372c7a>] hmcdrv_ftp_probe+0x8a/0xc0 [hmcdrv]
[ 249.400165] [<000002f34f3b5022>] hmcdrv_mod_init+0x22/0x1000 [hmcdrv]
[ 249.400168] [<000002f3cefaac80>] do_one_initcall+0x40/0x2e0
[ 249.400173] [<000002f3cf15878a>] do_init_module+0xaa/0x2e0
[ 249.400177] [<000002f3cf15a5f4>] init_module_from_file+0xd4/0x160
[ 249.400180] [<000002f3cf15a7ee>] idempotent_init_module+0x16e/0x320
[ 249.400183] [<000002f3cf15aa2e>] __s390x_sys_finit_module+0x8e/0x120
[ 249.400186] [<000002f3cff54778>] __do_syscall+0x178/0x690
[ 249.400189] [<000002f3cff643da>] system_call+0x72/0x90
2)
[ 372.280096] INFO: task modprobe:763 blocked for more than 245 seconds.
[ 372.280110] Not tainted 7.0.0-14-generic #14-Ubuntu
[ 372.280113] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[ 372.280114] task:modprobe state:D stack:0 pid:763 tgid:763
ppid:623 task_flags:0x400100 flags:0x00000000
[ 372.280120] Call Trace:
[ 372.280122] [<000002f3cff592ba>] __schedule+0x2fa/0x730
[ 372.280131] [<000002f3cff5972c>] schedule+0x3c/0xc0
[ 372.280134] [<000002f3cff6270c>] schedule_timeout+0xcc/0x140
[ 372.280136] [<000002f3cff5abf2>] wait_for_completion+0xb2/0x150
[ 372.280139] [<000002f34f373e16>] sclp_ftp_cmd+0x86/0x110 [hmcdrv]
[ 372.280149] [<000002f34f3735a0>] hmcdrv_cache_cmd+0x40/0xc0 [hmcdrv]
[ 372.280153] [<000002f34f372a02>] hmcdrv_ftp_do+0x62/0xf0 [hmcdrv]
[ 372.280156] [<000002f34f372c7a>] hmcdrv_ftp_probe+0x8a/0xc0 [hmcdrv]
[ 372.280160] [<000002f34f3b5022>] hmcdrv_mod_init+0x22/0x1000 [hmcdrv]
[ 372.280163] [<000002f3cefaac80>] do_one_initcall+0x40/0x2e0
[ 372.280168] [<000002f3cf15878a>] do_init_module+0xaa/0x2e0
[ 372.280172] [<000002f3cf15a5f4>] init_module_from_file+0xd4/0x160
[ 372.280175] [<000002f3cf15a7ee>] idempotent_init_module+0x16e/0x320
[ 372.280178] [<000002f3cf15aa2e>] __s390x_sys_finit_module+0x8e/0x120
[ 372.280181] [<000002f3cff54778>] __do_syscall+0x178/0x690
[ 372.280184] [<000002f3cff643da>] system_call+0x72/0x90
** Affects: ubuntu-z-systems
Importance: Medium
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: s390x stonking
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2156537
Title:
Call Traces when booting stonking kernel 7.0.0-14 on s390x
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2156537/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
