sing-box 升级后无法运行
Open
Nobody has claimed this yet.
bug
- Dominant language
- Go
- Stars
- 38.1k
- Forks
- 4.6k
- Avg merge
- 19d 15h
- Merged PRs (30d)
- 1
Description
Operating system
Linux
System version
Linux onecloud 6.12.58-current-meson #1 SMP Thu Nov 13 20:34:41 UTC 2025 armv7l GNU/Linux
Installation type
Original sing-box Command Line
If you are using a graphical client, please provide the version of the client.
No response
Version
apt上安装的版本是1.13.7 和 sing-box-beta_1.14.0~alpha.4_armhf.deb
Description
1.12.23
Reproduction
在玩客云的armbian系统上使用手动安装
sudo mkdir -p /etc/apt/keyrings &&
sudo curl -fsSL https://sing-box.app/gpg.key -o /etc/apt/keyrings/sagernet.asc &&
sudo chmod a+r /etc/apt/keyrings/sagernet.asc &&
echo '
Types: deb
URIs: https://deb.sagernet.org/
Suites: *
Components: *
Enabled: yes
Signed-By: /etc/apt/keyrings/sagernet.asc
' | sudo tee /etc/apt/sources.list.d/sagernet.sources &&
sudo apt-get update &&
sudo apt-get install sing-box # or sing-box-beta
安装后运行命令报错
$ sing-box version
SIGILL: illegal instruction
PC=0x387fc3c m=0 sigcode=1
instruction bytes: 0x13 0xf2 0x33 0xe7 0x1 0x30 0x43 0xe2 0x4 0x0 0x53 0xe1 0x1 0x30 0x44 0xa2
goroutine 0 gp=0x39a8df0 m=0 mp=0x39a9860 [idle]:
runtime: g 0 gp=0x39a8df0: unknown pc 0x387fc3c
stack: frame={sp:0xbea8e2d8, fp:0x0} stack=[0x3f4,0xbea8e49c)
0xbea8e258: 0x00000000 0x00000000 0x00000001 0x039d7180
0xbea8e268: 0x00000044 0x0000000f 0x00000001 0x00000000
0xbea8e278: 0x00000000 0xb6ccb700 0x01b9b93c <runtime.(*pageAlloc).alloc+0x0000013c> 0x039b0638
0xbea8e288: 0x03c80000 0x00000004 0x00000101 0x00000004
0xbea8e298: 0xb6cec904 0x00076000 0x00000004 0x00000004
0xbea8e2a8: 0x01b96268 <runtime.(*mheap).allocNeedsZero+0x00000088> 0x01b96c90 <runtime.(*mheap).initSpan+0x00000048> 0x00000000 0x00000002
0xbea8e2b8: 0x039f9058 0x00001000 0x039ceb00 0x00000017
0xbea8e2c8: 0x00000023 0x00000000 0x00000002 0x0387f990
0xbea8e2d8: <0xffffffff 0x039d1801 0x00000000 0x00000000
0xbea8e2e8: 0x000007f0 0x00000fe0 0x000007ec 0x00000053
0xbea8e2f8: 0x01b9613c <runtime.(*mheap).allocManual+0x00000040> 0x00000002 0x039f9040 0x00a55424
0xbea8e308: 0x039ceb00 0x00000013 0x0000001f 0x00000017
0xbea8e318: 0x000007ec 0x0387fcfc 0xffffffff 0x13c912f4
0xbea8e328: 0x702ca3e3 0x7fffffff 0x000003f0 0x000007e0
0xbea8e338: 0x000003ec 0x0000004f 0x00008000 0x00000002
0xbea8e348: 0x039f9028 0x00a55424 0x039ceb00 0x0000000f
runtime: g 0 gp=0x39a8df0: unknown pc 0x387fc3c
stack: frame={sp:0xbea8e2d8, fp:0x0} stack=[0x3f4,0xbea8e49c)
0xbea8e258: 0x00000000 0x00000000 0x00000001 0x039d7180
0xbea8e268: 0x00000044 0x0000000f 0x00000001 0x00000000
0xbea8e278: 0x00000000 0xb6ccb700 0x01b9b93c <runtime.(*pageAlloc).alloc+0x0000013c> 0x039b0638
0xbea8e288: 0x03c80000 0x00000004 0x00000101 0x00000004
0xbea8e298: 0xb6cec904 0x00076000 0x00000004 0x00000004
0xbea8e2a8: 0x01b96268 <runtime.(*mheap).allocNeedsZero+0x00000088> 0x01b96c90 <runtime.(*mheap).initSpan+0x00000048> 0x00000000 0x00000002
0xbea8e2b8: 0x039f9058 0x00001000 0x039ceb00 0x00000017
0xbea8e2c8: 0x00000023 0x00000000 0x00000002 0x0387f990
0xbea8e2d8: <0xffffffff 0x039d1801 0x00000000 0x00000000
0xbea8e2e8: 0x000007f0 0x00000fe0 0x000007ec 0x00000053
0xbea8e2f8: 0x01b9613c <runtime.(*mheap).allocManual+0x00000040> 0x00000002 0x039f9040 0x00a55424
0xbea8e308: 0x039ceb00 0x00000013 0x0000001f 0x00000017
0xbea8e318: 0x000007ec 0x0387fcfc 0xffffffff 0x13c912f4
0xbea8e328: 0x702ca3e3 0x7fffffff 0x000003f0 0x000007e0
0xbea8e338: 0x000003ec 0x0000004f 0x00008000 0x00000002
0xbea8e348: 0x039f9028 0x00a55424 0x039ceb00 0x0000000f
goroutine 1 gp=0x3c02128 m=0 mp=0x39a9860 [running]:
runtime.systemstack_switch()
runtime/asm_arm.s:272 +0x4 fp=0x3c687a8 sp=0x3c687a4 pc=0x1bf048c
runtime.main()
runtime/proc.go:173 +0x64 fp=0x3c687ec sp=0x3c687a8 pc=0x1bacf48
runtime.goexit({})
runtime/asm_arm.s:877 +0x4 fp=0x3c687ec sp=0x3c687ec pc=0x1bf2168
trap 0x6
error 0x0
oldmask 0x0
r0 0xb6caa000
r1 0x1000
r2 0x7f0
r3 0xff0
r4 0x2
r5 0x39f9058
r6 0x1
r7 0x39ceb00
r8 0x17
r9 0x23
r10 0x0
fp 0x1000
ip 0x7f
sp 0xbea8e2d8
lr 0x387f990
pc 0x387fc3c
cpsr 0x80000010
fault 0x0
怀疑 https://deb.sagernet.org/ 上的 armhf 包上传错了, 历史版本 1.12.23 版本可以正常使用。
Logs
Supporter
- I am a sponsor
Integrity requirements
- I confirm that I have read the documentation, understand the meaning of all the configuration items I wrote, and did not pile up seemingly useful options or default values.
- I confirm that I have provided the server and client configuration files and process that can be reproduced locally, instead of a complicated client configuration file that has been stripped of sensitive data.
- I confirm that I have provided the simplest configuration that can be used to reproduce the error I reported, instead of depending on remote servers, TUN, graphical interface clients, or other closed-source software.
- I confirm that I have provided the complete configuration files and logs, rather than just providing parts I think are useful out of confidence in my own intelligence.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the installed armhf packages for versions 1.12.23, 1.13.7, and 1.14.0~alpha.4 on the reported Linux armv7l system, then run sing-box version to reproduce the SIGILL. Done means the relevant package starts successfully on this system without the illegal-instruction crash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, linux
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100