Public bug reported:
I'm experience the same problem as these
https://askubuntu.com/questions/1231755/random-system-halt-crash-with-
ubuntu-20-04-on-raspberry-pi-4 https://askubuntu.com/questions/1235113
/hang-with-ubuntu-20-04-64-bit-on-raspberry-pi people describe.
When the system crashes it doesn't respond to ssh nor to ping.
The only thing I saw in logs is this:
Jul 19 13:40:02 kernel: [16676.063926] INFO: task journal-offline:885 blocked
for more than 120 seconds.
Jul 19 13:40:02 kernel: [16676.071182] Tainted: G C E
5.4.0-1013-raspi #13-Ubuntu
Jul 19 13:40:02 kernel: [16676.078082] "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jul 19 13:40:02 kernel: [16676.086032] journal-offline D 0 885 1
0x00000800
Jul 19 13:40:02 kernel: [16676.086038] Call trace:
Jul 19 13:40:02 kernel: [16676.086050] __switch_to+0x104/0x170
Jul 19 13:40:02 kernel: [16676.086057] __schedule+0x30c/0x7c0
Jul 19 13:40:02 kernel: [16676.086062] schedule+0x3c/0xb8
Jul 19 13:40:02 kernel: [16676.086067] jbd2_log_wait_commit+0xe4/0x188
Jul 19 13:40:02 kernel: [16676.086071] jbd2_complete_transaction+0x94/0xe8
Jul 19 13:40:02 kernel: [16676.086076] ext4_sync_file+0x35c/0x410
Jul 19 13:40:02 kernel: [16676.086081] vfs_fsync_range+0x4c/0x88
Jul 19 13:40:02 kernel: [16676.086085] do_fsync+0x48/0x88
Jul 19 13:40:02 kernel: [16676.086090] __arm64_sys_fsync+0x24/0x38
Jul 19 13:40:02 kernel: [16676.086094] el0_svc_common.constprop.0+0xe0/0x1e8
Jul 19 13:40:02 kernel: [16676.086098] el0_svc_handler+0x34/0xa0
Jul 19 13:40:02 kernel: [16676.086102] el0_svc+0x10/0x14
Jul 19 13:40:02 kernel: [16676.086117] INFO: task kworker/3:2:884 blocked for
more than 120 seconds.
Jul 19 13:40:02 kernel: [16676.093009] Tainted: G C E
5.4.0-1013-raspi #13-Ubuntu
Jul 19 13:40:02 kernel: [16676.099900] "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jul 19 13:40:02 kernel: [16676.107849] kworker/3:2 D 0 884 2
0x00000028
Jul 19 13:40:02 kernel: [16676.107871] Workqueue: events_freezable mmc_rescan
Jul 19 13:40:02 kernel: [16676.107875] Call trace:
Jul 19 13:40:02 kernel: [16676.107880] __switch_to+0x104/0x170
Jul 19 13:40:02 kernel: [16676.107885] __schedule+0x30c/0x7c0
Jul 19 13:40:02 kernel: [16676.107897] schedule+0x3c/0xb8
Jul 19 13:40:02 kernel: [16676.107903] __mmc_claim_host+0xe4/0x2f0
Jul 19 13:40:02 kernel: [16676.107907] mmc_get_card+0x38/0x48
Jul 19 13:40:02 kernel: [16676.107911] mmc_sd_detect+0x24/0x90
Jul 19 13:40:02 kernel: [16676.107916] mmc_rescan+0x37c/0x3f0
Jul 19 13:40:02 kernel: [16676.107921] process_one_work+0x1d0/0x430
Jul 19 13:40:02 kernel: [16676.107924] worker_thread+0x54/0x4a0
Jul 19 13:40:02 kernel: [16676.107929] kthread+0xfc/0x128
Jul 19 13:40:02 kernel: [16676.107934] ret_from_fork+0x10/0x1c
Jul 19 13:42:03 kernel: [16796.897856] INFO: task kworker/3:2:884 blocked for
more than 241 seconds.
Jul 19 13:42:03 kernel: [16796.904757] Tainted: G C E
5.4.0-1013-raspi #13-Ubuntu
Jul 19 13:42:03 kernel: [16796.911655] "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jul 19 13:42:03 kernel: [16796.919606] kworker/3:2 D 0 884 2
0x00000028
Jul 19 13:42:03 kernel: [16796.919631] Workqueue: events_freezable mmc_rescan
Jul 19 13:42:03 kernel: [16796.919636] Call trace:
Jul 19 13:42:03 kernel: [16796.919642] __switch_to+0x104/0x170
Jul 19 13:42:03 kernel: [16796.919649] __schedule+0x30c/0x7c0
Jul 19 13:42:03 kernel: [16796.919653] schedule+0x3c/0xb8
Jul 19 13:42:03 kernel: [16796.919658] __mmc_claim_host+0xe4/0x2f0
Jul 19 13:42:03 kernel: [16796.919662] mmc_get_card+0x38/0x48
Jul 19 13:42:03 kernel: [16796.919667] mmc_sd_detect+0x24/0x90
Jul 19 13:42:03 kernel: [16796.919671] mmc_rescan+0x37c/0x3f0
Jul 19 13:42:03 kernel: [16796.919676] process_one_work+0x1d0/0x430
Jul 19 13:42:03 kernel: [16796.919679] worker_thread+0x54/0x4a0
Jul 19 13:42:03 kernel: [16796.919684] kthread+0xfc/0x128
Jul 19 13:42:03 kernel: [16796.919689] ret_from_fork+0x10/0x1c
Jul 19 13:01:47 kernel: [ 0.000000] Booting Linux on physical CPU
0x0000000000 [0x410fd083]
Jul 19 13:01:47 kernel: [ 0.000000] Linux version 5.4.0-1013-raspi
(buildd@bos02-arm64-078) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2))
#13-Ubuntu SMP Mon Jun 15 03:17:37 UTC 2020 (Ubuntu 5.4.0-1013.13-raspi 5.4.44)
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-1013-raspi 5.4.0-1013.13
ProcVersionSignature: Ubuntu 5.4.0-1013.13-raspi 5.4.44
Uname: Linux 5.4.0-1013-raspi aarch64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: arm64
CasperMD5CheckResult: skip
Date: Sun Jul 19 18:40:08 2020
ImageMediaBuild: 20200423.1
ProcEnviron:
SHELL=/bin/bash
LANG=C.UTF-8
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
PATH=(custom, no user)
SourcePackage: linux-raspi
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: linux-raspi (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug arm64 focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888135
Title:
Ubuntu 20.04 server randomly crash on rpi 4
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1888135/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
