Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shinjuku initialization function 'init_hw' getting stuck #8

Open
xudongliao opened this issue May 1, 2023 · 0 comments
Open

Shinjuku initialization function 'init_hw' getting stuck #8

xudongliao opened this issue May 1, 2023 · 0 comments

Comments

@xudongliao
Copy link

Hello,

I am currently experiencing an issue while attempting to run Shinjuku. Specifically, it is getting stuck when running the initialization function init_hw located here:

ret = pthread_create(&tid, NULL, start_cpu, (void *)(unsigned long) i);

I am running Shinjuku on Ubuntu 18.04 with a 4.4.100 kernel.

Upon investigation, I noticed that the thread was not able to be created. The kernel threw a bug, indicating that it was unable to perform a context switch on CPU#0. After investigating the issue, I noticed that the thread was not able to be created. The kernel threw an error indicating that it was unable to perform a context switch on CPU#0. I suspect that this may be the reason why the newly created thread is unable to start. The kernel log is:

[ 1671.326255] vmx: created VCPU (VPID 1)
[ 1696.537625] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [shinjuku:18976]
[ 1696.540220] Modules linked in: dune(OE) uio_pci_generic uio vfio_pci vfio_iommu_type1 vfio_virqfd vfio cuse rdma_ucm(OE) ib_ipoib(OE) ib_umad(OE) x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass lpc_ich sm750fb(C) ioatdma input_leds 8250_fintek serio_raw sb_edac dca mei_me mei edac_core shpchp mac_hid binfmt_misc squashfs sch_fq_codel ib_iser(OE) rdma_cm(OE) iw_cm(OE) ib_cm(OE) configfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi knem(OE) sunrpc ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib(OE) ib_uverbs(OE) ib_core(OE) hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper
[ 1696.540265]  cryptd psmouse isci mpt3sas ahci mlx5_core(OE) tg3 libsas libahci mlxfw(OE) auxiliary(OE) raid_class mlx_compat(OE) ptp scsi_transport_sas pps_core wmi fjes [last unloaded: dune]
[ 1696.540276] CPU: 0 PID: 18976 Comm: shinjuku Tainted: G         C OEL  4.4.100 #2
[ 1696.540278] Hardware name: xxxxx Technologies Co., Ltd. RH1288 V2-4L/BC11SRSH1, BIOS RMIBV396 10/29/2014
[ 1696.540280] task: ffff880824fda940 ti: ffff8808220f8000 task.ti: ffff8808220f8000
[ 1696.540281] RIP: 0010:[<ffffffffc07d4d66>]  [<ffffffffc07d4d66>] vmx_launch+0x17f6/0x1c80 [dune]
[ 1696.540289] RSP: 0018:ffff8808220fbd38  EFLAGS: 00000086
[ 1696.540290] RAX: ffff8808220fbd38 RBX: 0000000000000001 RCX: 000000000000b3a0
[ 1696.540291] RDX: ffffffff8183b3a0 RSI: ffffffff00000000 RDI: 00007f41afff3000
[ 1696.540292] RBP: ffff8808220fbdc0 R08: 00000000ffffffff R09: 0000000000000000
[ 1696.540293] R10: 00007f41afff2000 R11: 0000000000000007 R12: ffff880032eec400
[ 1696.540294] R13: 0000000080000000 R14: ffff8808220fc000 R15: 00000000fffffff7
[ 1696.540296] FS:  00007f61cadce000(0000) GS:ffff88085e000000(0000) knlGS:0000000000000000
[ 1696.540297] CS:  0010 DS: 002b ES: 002b CR0: 0000000080050033
[ 1696.540298] CR2: 00007f41b07f2da0 CR3: 0000000852b0e000 CR4: 00000000001426f0
[ 1696.540299] Stack:
[ 1696.540300]  00007f61c8d72a80 ffff880824fda940 ffff8808220fbdd0 ffff8808220fbdd0
[ 1696.540302]  ffff8808220fbd64 0000000200000000 ffffffffffffff57 ffffffff00000000
[ 1696.540304]  0000000000000000 0000000179a9b800 ffff88083c672a40 082460bf65c8856b
[ 1696.540306] Call Trace:
[ 1696.540310]  [<ffffffffc07d2347>] dune_dev_ioctl+0x77/0x1c0 [dune]
[ 1696.540314]  [<ffffffff81227485>] do_vfs_ioctl+0x315/0x500
[ 1696.540318]  [<ffffffff8121503e>] ? ____fput+0xe/0x10
[ 1696.540321]  [<ffffffff810a0750>] ? task_work_run+0x80/0xa0
[ 1696.540323]  [<ffffffff812276df>] SyS_ioctl+0x6f/0x90
[ 1696.540327]  [<ffffffff8183a6b2>] entry_SYSCALL_64_fastpath+0x16/0x71
[ 1696.540328] Code: 0f b7 09 48 c1 e2 10 48 c1 e6 20 48 09 f2 48 09 ca 3d f2 00 00 00 0f 84 fb 02 00 00 48 89 e0 48 83 e4 f0 6a 18 50 9c 6a 10 ff d2 <e9> f2 f5 ff ff 85 c0 0f 89 d6 f5 ff ff cd 02 e9 cf f5 ff ff 41

Do you have any ideas on how to resolve this issue? Any assistance would be greatly appreciated. Thank you in advance.

@xudongliao xudongliao changed the title Shinjuku get stuck Shinjuku initialization function 'init_hw' getting stuck May 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant