请问bug type 210重启一般是什么原因导致的?
请问bug type 210重启一般是什么原因导致的?出现好几次了
[经过版主编辑]
iPhone 11, iOS 13
请问bug type 210重启一般是什么原因导致的?出现好几次了
[经过版主编辑]
iPhone 11, iOS 13
"bug_type":"210","timestamp":"2020-08-18 19:35:18.00 +0800","os_version":"iPhone OS 13.5.1 (17F80)","incident_id":"A3A4C10B-1B07-45F1-BADD-E0E3B9ADA39F"}
{
"build" : "iPhone OS 13.5.1 (17F80)",
"product" : "iPhone10,2",
"kernel" : "Darwin Kernel Version 19.5.0: Tue May 26 20:56:31 PDT 2020; root:xnu-6153.122.2~1\/RELEASE_ARM64_T8015",
"incident" : "A3A4C10B-1B07-45F1-BADD-E0E3B9ADA39F",
"crashReporterKey" : "c59c4e22f37b314bbdb5264bfb416de5ed446016",
"date" : "2020-08-18 19:35:10.55 +0800",
"panicString" : "panic(cpu 3 caller 0xfffffff01e5344fc): \"i2c2::_checkBusStatus Bus is still in a bad state; last write status 00010110 int shadow 00010100 xfer 00000000 fifo 00000000 for device audio-speaker-top\"@\/Library\/Caches\/com.apple.xbs\/Sources\/AppleS5L8940X\/AppleS5L8940X-169.0.1\/AppleS5L8940XI2C.cpp:351\nDebugger message: panic\nMemory ID: 0x6\nOS version: 17F80\nKernel version: Darwin Kernel Version 19.5.0: Tue May 26 20:56:31 PDT 2020; root:xnu-6153.122.2~1\/RELEASE_ARM64_T8015\nKernel UUID: ********-****-****-****-************\niBoot version: iBoot-5540.120.17\nsecure boot?: YES\nPaniclog version: 13\nKernel slide: 0x0000000015fd4000\nKernel text base: 0xfffffff01cfd8000\nmach_absolute_time: 0x4fa7dc8f0\nEpoch Time: sec usec\n Boot : 0x5f3bae42 0x00010e02\n Sleep : 0x5f3bbb97 0x000c2e93\n Wake : 0x5f3bbc26 0x00082269\n Calendar: 0x5f3bbcc3 0x000d93ae\n\nPanicked task 0xffffffe001d1a400: 2614 pages, 43 threads: pid 31: mediaserverd\nPanicked thread: 0xffffffe007954a70, backtrace: 0xffffffe05385a630, tid: 18542\n\t\t lr: 0xfffffff01dbcad48 fp: 0xffffffe05385a670\n\t\t lr: 0xfffffff01dbcaba4 fp: 0xffffffe05385a6e0\n\t\t lr: 0xfffffff01dcdfc68 fp: 0xffffffe05385a790\n\t\t lr: 0xfffffff01e1cd62c fp: 0xffffffe05385a7a0\n\t\t lr: 0xfffffff01dbca510 fp: 0xffffffe05385ab10\n\t\t lr: 0xfffffff01dbca868 fp: 0xffffffe05385ab60\n\t\t lr: 0xfffffff01f072a38 fp: 0xffffffe05385ab80\n\t\t lr: 0xfffffff01e5344fc fp: 0xffffffe05385ac00\n\t\t lr: 0xfffffff01e533d60 fp: 0xffffffe05385ac90\n\t\t lr: 0xfffffff01e5338fc fp: 0xffffffe05385acc0\n\t\t lr: 0xfffffff01e533598 fp: 0xffffffe05385ad00\n\t\t lr: 0xfffffff01e212174 fp: 0xffffffe05385ad20\n\t\t lr: 0xfffffff01e211fdc fp: 0xffffffe05385ad50\n\t\t lr: 0xfffffff01e13e3e8 fp: 0xffffffe05385adc0\n\t\t lr: 0xfffffff01e2129a0 fp: 0xffffffe05385ae20\n\t\t lr: 0xfffffff01e4054d8 fp: 0xffffffe05385aea0\n\t\t lr: 0xfffffff01e4052d8 fp: 0xffffffe05385af30\n\t\t lr: 0xfffffff01ea24d60 fp: 0xffffffe05385af70\n\t\t lr: 0xfffffff01ea25544 fp: 0xffffffe05385afa0\n\t\t lr: 0xfffffff01ea2468c fp: 0xffffffe05385afe0\n\t\t lr: 0xfffffff01ea22524 fp: 0xffffffe05385b040\n\t\t lr: 0xfffffff01ea22864 fp: 0xffffffe05385b070\n\t\t lr: 0xfffffff01e41ed00 fp: 0xffffffe05385b0e0\n\t\t lr: 0xfffffff01e414930 fp: 0xffffffe05385b160\n\t\t lr: 0xfffffff01e13e3e8 fp: 0xffffffe05385b1d0\n\t\t lr: 0xfffffff01e3fb774 fp: 0xffffffe05385b270\n\t\t lr: 0xfffffff01e40074c fp: 0xffffffe05385b320\n\t\t lr: 0xfffffff01e4003d0 fp: 0xffffffe05385b370\n\t\t lr: 0xfffffff01e40009c fp: 0xffffffe05385b3d0\n\t\t lr: 0xfffffff01e13bfd4 fp: 0xffffffe05385b420\n\t\t lr: 0xfffffff01e414d8c fp: 0xffffffe05385b4b0\n\t\t lr: 0xfffffff01e163918 fp: 0xffffffe05385b580\n\t\t lr: 0xfffffff01e1624e0 fp: 0xffffffe05385b5e0\n\t\t lr: 0xfffffff01e13e3e8 fp: 0xffffffe05385b650\n\t\t lr: 0xfffffff01e3f8d00 fp: 0xffffffe05385b6d0
[个人信息经过版主编辑]
jing100,您好
感谢您来到 Apple 支持社区!
我了解到您的 iPhone 遇到意外重新启动的情况。由于暂时还没有其他社区用户来与您一起讨论或回复您的帖子,在此之前,建议您不妨先尝试一下以下操作步骤:
若想了解更多信息,以下知识文章供您参考:
如果您的 iPhone、iPad 或 iPod touch 开不了机或死机怎么办
如果以上操作未能解决您的问题,请联系 Apple 支持来获得更多协助。请点击以下链接,选择“iPhone”:https://getsupport.apple.com
希望可以帮助到您,谢谢!
不要在意这个问题 正常更新系统 使用就好了
追加部分日志:
{"bug_type":"210","timestamp":"2020-07-10 22:24:10.30 +0800","os_version":"iPhone OS 13.3.1 (17D50)","incident_id":"ABE34884-19C4-4300-95DA-3248A8346260"}
{
"build" : "iPhone OS 13.3.1 (17D50)",
"product" : "iPhone12,1",
"kernel" : "Darwin Kernel Version 19.3.0: Thu Jan 9 21:11:10 PST 2020; root:xnu-6153.82.3~1\/RELEASE_ARM64_T8030",
"incident" : "ABE34884-19C4-4300-95DA-3248A8346260",
"crashReporterKey" : "54d52ab5fe0447dad40d3811fc43773cbf612d1e",
"date" : "2020-07-10 22:23:59.30 +0800",
"panicString" : "panic(cpu 0 caller 0xfffffff01fac331c): mbuf_watchdog: 15 waiters stuck for 66 secs\n38062\/169265 mbufs in use:\n\t955 mbufs allocated to data\n\t36880 mbufs allocated to packet headers\n\t227 mbufs allocated to socket names and addresses\n\t131203 mbufs allocated to caches\n166\/336 mbuf 2KB clusters in use\n8\/168 mbuf 4KB clusters in use\n37\/387 mbuf 16KB clusters in use\n49914 KB allocated to network (approx. 86% in use)\n86215 KB returned to the system\nVM allocation failures: contiguous 0, normal 0, one page 0\nworker thread runs: 6887, expansions: 8, cl 0\/0, bigcl 0\/0, 16k 143\/12652\nworker thread last run time: 2199146 (66 seconds ago)\ndrain routine last run time: 2198550 (662 seconds ago)\n\nmbuf leak detection table:\n\ttotal captured: 291238 (one per 500)\n\ttotal allocs outstanding: 984\n\tnew hash recorded: 204258 allocs, 195522 traces\n\thash collisions: 1255 allocs, 86536 traces\n\toverwrites: 202830 allocs, 0 traces\n\tlock conflicts: 0\n\ntop 5 outstanding traces:\n[1] 394 outstanding alloc(s), 738 hit(s), 44 collision(s)\n[2] 331 outstanding alloc(s), 1393 hit(s), 7 collision(s)\n[3] 94 outstanding alloc(s), 75318 hit(s), 66382 collision(s)\n[4] 46 outstanding alloc(s), 64 hit(s), 0 collision(s)\n[5] 37 outstanding alloc(s), 42 hit(s), 1 collision(s)\
请问bug type 210重启一般是什么原因导致的?