android 平台开机自动重启

最新推荐文章于 2023-02-13 17:01:31 发布

原创最新推荐文章于 2023-02-13 17:01:31 发布 · 1.2k 阅读

0 ·

CC 4.0 BY-SA版权

工作同时被 2 个专栏收录

7 篇文章

订阅专栏

android

6 篇文章

订阅专栏

本文记录了一次Android设备在启动过程中出现的不断重启问题，并详细展示了系统日志中关于SQLite数据库操作及文件系统错误的信息。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

最近android平台遇到开机不断重启现象，log如下，有了解这方面的大牛，请指导下，谢谢！

This is DataBaseImpl Config()!
[10:19:33]
[10:19:33]
[10:19:33] sqlite3_libversions:3.7.11------threadsafe:2 ,thread_ID :1091249116
[10:19:33]
[10:19:33]
[10:19:33] NodeImpl::Visitor
[10:19:33]
[10:19:33] size is:1
[10:19:33] NodeImpl::Visitor
[10:19:33]DataBaseImpl:open database successful ! pthread_self(): 1091249116 ,DBName:[ file::memory:?cache=shared ]
[10:19:33]This is MemoryDB Config!
[10:19:33]This is DataBaseImpl Config()!
[10:19:33]
[10:19:33]
[10:19:33] sqlite3_libversions:3.7.11------threadsafe:2 ,thread_ID :1091249116
[10:19:33]
[10:19:33]
[10:19:33] NodeImpl::Visitor
[10:19:33]
[10:19:33] size is:1
[10:19:33] CreateStructByFilevisitor, attr type is createfile!!
[10:19:33]
[10:19:33] NodeImpl::Visitor
[10:19:33]
[10:19:33] NodeImpl::Visitor
[10:19:33]
[10:19:33] size is:1
[10:19:33] NodeImpl::Visitor
[10:19:33]
[10:19:33] AllocateDiskDB::Visitor
[10:19:33]
[10:19:33] AllocateDiskDB::Visitor
[10:19:33]AllocateDiskDB success :/data/ConfigDB.db !
[10:19:33]DataBaseImpl:open database successful ! pthread_self(): 1091249116 ,DBName:[ /data/ConfigDB.db ]
[10:19:33]This is DiskDB Config!
[10:19:33]This is DataBaseImpl Config()!
[10:19:33]
[10:19:33]
[10:19:33] sqlite3_libversions:3.7.11------threadsafe:2 ,thread_ID :1091249116
[10:19:33]
[10:19:33]
[10:19:33] NodeImpl::Visitor
[10:19:36][ 165.141894] EXT4-fs error (device mmcblk0p2): ext4_iget:3925: inode #90: comm er.ServerThread: bad extended attribute block 1073741824
[10:19:36][ 165.154299] Aborting journal on device mmcblk0p2-8.
[10:19:36][ 165.160495] Kernel panic - not syncing: EXT4-fs (device mmcblk0p2): panic forced after error
[10:19:36][ 165.160495]
[10:19:36][ 165.170657] CPU0: stopping
[10:19:36][ 165.173461] [<c0138d60>] (unwind_backtrace+0x0/0xf0) from [<c0137058>] (handle_IPI+0xf4/0x180)
[10:19:36][ 165.182287] [<c0137058>] (handle_IPI+0xf4/0x180) from [<c0108574>] (gic_handle_irq+0x58/0x60)
[10:19:36][ 165.191022] [<c0108574>] (gic_handle_irq+0x58/0x60) from [<c013207c>] (__irq_usr+0x3c/0x60)
[10:19:36][ 165.199574] Exception stack(0xde715fb0 to 0xde715ff8)
[10:19:36][ 165.204748] 5fa0: 40022414 04000000 00000000 88000000
[10:19:36][ 165.213125] 5fc0: 04000000 b8022414 0002d744 00000152 00000000 42e736a0 00000000 42e73694
[10:19:36][ 165.221500] 5fe0: 00000019 42e73438 002c4dd0 002c4dd0 00000010 ffffffff
[10:19:41]0xb8000804=0x00F00010
[10:19:41]0xb8000808=0xF030F000
[10:19:41]0xb8000810=0x10101010
[10:19:41]0xb8000814=0xF0101010
[10:19:41]0xb8000818=0x10101010
[10:19:41] part cfg : 0x02
[10:19:41] boot cfg : 0x00
[10:19:41] boot wp sts : 0x00
[10:19:41] boot wp : 0x00
[10:19:41] part cfg : 0x01
[10:19:41] boot cfg : 0x00
[10:19:41] boot wp sts : 0x00
[10:19:41] boot wp : 0x00
[10:19:41] part cfg : 0x00
[10:19:41] boot cfg : 0x00
[10:19:41] boot wp sts : 0x00
[10:19:41] boot wp : 0x00