关闭uboot MMU 会导致android2.3 S5pv210 系统不稳定?!why

gooogleman 2013-05-23 09:57:32
在uboot里面屏蔽了MMU 使能
//#define CONFIG_ENABLE_MMU
就导致android 2.3 在S5pv210 上不稳定了,如果没屏蔽就稳定很多,why?!
坑爹的人啊,问了一些做了几年linux和android的人说没影响的,啥玩意啊,怎么会这么挫呢!
尤其是S5pv210 的GPU 驱动,出问题最频繁,如果是我内存参数传递有误,系统是不会启动的,怎么搞成这样呢?
有经验的过来说说吧。

下面是这几天的实验现象


重复启动会遇到这种问题,系统死机了:
[ 2.896160] android_usb gadget: high speed config #1: Android Composite
[ 4.510793] request_suspend_state: wakeup (3->0) at 3981410419 (2010-01-01 12:00:04.019802543 UTC)
[ 4.521102] init: untracked pid 51 exited
[ 4.523756] init: untracked pid 55 exited
[ 13.611361] Internal error: Oops - undefined instruction: 0 [#1] PREEMPT
[ 13.616584] last sysfs file: /sys/power/state
[ 13.620944] Unable to handle kernel paging request at virtual address 0a0000de
[ 13.628110] pgd = c0004000
[ 13.630795] [0a0000de] *pgd=00000000
[ 21.121137] BUG: spinlock lockup on CPU#0, /0, c0510374
[ 21.124869] Backtrace:
[ 21.127324] [<c0031fb8>] (dump_backtrace+0x0/0x110) from [<c0392880>] (dump_stack+0x18/0x1c)
[ 21.135703] r6:00000000 r5:c0088000 r4:c0510374 r3:e1a00005
[ 21.141343] [<c0392868>] (dump_stack+0x0/0x1c) from [<c01976c4>] (do_raw_spin_lock+0x128/0x168)
[ 21.150008] [<c019759c>] (do_raw_spin_lock+0x0/0x168) from [<c0395804>] (_raw_spin_lock_irq+0x2c/0x30)
[ 21.159272] r8:00000005 r7:c049cd52 r6:c0088038 r5:c008a0d0 r4:c008a0d0
[ 21.165951] [<c03957d8>] (_raw_spin_lock_irq+0x0/0x30) from [<c0032330>] (die+0x30/0x1cc)
[ 21.174098] [<c0032300>] (die+0x0/0x1cc) from [<c00348cc>] (__do_kernel_fault+0x6c/0x8c)
[ 21.182149] r8:00000000 r7:00000005 r6:00000000 r5:c008a0d0 r4:0a0000de
[ 21.188827] [<c0034860>] (__do_kernel_fault+0x0/0x8c) from [<c0034acc>] (do_page_fault+0x1e0/0x1fc)
[ 21.197834] r8:00000000 r7:0a0000de r6:00000001 r5:c008a0d0 r4:c0571fd0
[ 21.204333] r3:c008a0d0
[ 21.206939] [<c00348ec>] (do_page_fault+0x0/0x1fc) from [<c0034b98>] (do_translation_fault+0x24/0xa0)
[ 21.216125] [<c0034b74>] (do_translation_fault+0x0/0xa0) from [<c002d2f4>] (do_DataAbort+0x3c/0xa0)
[ 21.225131] r6:0a0000de r5:c051044c r4:00000005 r3:c05103fc
[ 21.230769] [<c002d2b8>] (do_DataAbort+0x0/0xa0) from [<c002da6c>] (__dabt_svc+0x4c/0x60)




又遇到这种问题了
ext4format 按复位10次不到又死机了。
[ 11.329304] Modules linked in:
[ 11.332340] CPU: 0 Not tainted (2.6.35.7 #1)
[ 11.336932] PC is at 0xe41ab000
[ 11.340059] LR is at do_PrefetchAbort+0x3c/0xa0
[ 11.344558] pc : [<e41ab000>] lr : [<c002d254>] psr: 60000193
[ 11.344564] sp : ee9d3c28 ip : 00000004 fp : 3162c3ef
[ 11.355994] r10: c051e8d8 r9 : 20000193 r8 : 3b1235a2
[ 11.361194] r7 : ee9d3cb0 r6 : e52d1004 r5 : c051063c r4 : c002d2f4
[ 11.367693] r3 : c05105fc r2 : ee9d3cb0 r1 : c002d2f4 r0 : e52d1004
[ 11.374194] Flags: nZCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment user
[ 11.381385] Control: 10c5387d Table: 4e9d4019 DAC: 00000015
[ 11.387103]
[ 11.387106] PC: 0xe41aaf80:
[ 11.391348] af80 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 11.399494] afa0 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 11.407639] afc0 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 11.415785] afe0 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 11.423931] b000 ff000000 ff000000 ff000000 ff000000 ff000000 ff000000 ff000000 ff000000
[ 11.432076] b020 ff000000 ff000000 ff000000 ff000000 ff000000 ff000000 ff000000 ff000000
[ 11.440222] b040 ff000000 ff000000 ff000000 ff000000 ff000000 ff000000 ff000000 ff000000
[ 11.448368] b060 ff000000 ff000000 ff000000 ff000000 ff000000 ff000000 ff000000 ff000000
[ 11.456514]
[ 11.456516] LR: 0xc002d1d4:
[ 11.460760] d1d4 e50be09c e3a0e004 e50b5098 e50be0a4 e28ee002 e50bc0a0 e58de000 eb0014ce
[ 11.468905] d1f4 e24bd020 e89da9f0 c051035c c051036c c054b344 c049c790 c049c7ba 00030001
[ 11.477051] d214 c049c7be e1a0c00d e92dd8f0 e24cb004 e24dd088 e201cb01 e1a04001 e201100f
[ 11.485196] d234 e59f3070 e181c32c e3841102 e1a06000 e1a07002 e083520c e1a0e00f e793f20c
[ 11.493342] d254 e3500000 0a000011 e595100c e1a02004 e1a03006 e59f0040 eb0d95c2 e595c008
[ 11.501488] d274 e595e004 e1a01007 e1a03004 e59f002c e24b209c e50bc094 e50be09c e3a0c000
[ 11.509633] d294 e50b6090 e58dc000 e50bc098 eb0014a2 e24bd01c e89da8f0 c05105fc c049cc57
[ 11.517779] d2b4 c04b5b5c e1a0c00d e92dd8f0 e24cb004 e24dd088 e201cb01 e1a04001 e201100f
[ 11.525925]
[ 11.525928] SP: 0xee9d3ba8:


还是wince稳定啊。
晕ext3format 之后又来了一次不启动
[ 2.712437] warning: `rild' uses 32-bit capabilities (legacy support in use)
[ 3.021029] android_usb gadget: high speed config #1: Android Composite
[ 10.009783] request_suspend_state: wakeup (3->0) at 9480398418 (2010-01-01 12:00:09.518617168 UTC)
[ 12.192678] Unable to handle kernel paging request at virtual address 76453320
[ 12.198419] Unable to handle kernel paging request at virtual address 300af87d
[ 12.205610] Unable to handle kernel paging request at virtual address 300af87d
[ 12.212802] Unable to handle kernel paging request at virtual address 300af87d
[ 12.219995] Unable to handle kernel paging request at virtual address 300af87d
[ 12.227187] Unable to handle kernel paging request at virtual address 300af87d
[ 12.234380] Unable to handle kernel paging request at virtual address 300af87d
[ 12.241572] Unable to handle kernel paging request at virtual address 300af87d
[ 12.248765] Unable to handle kernel paging request at virtual address 300af87d
[ 12.255957] Unable to handle kernel paging request at virtual address 300af87d
[ 12.263149] Unable to handle kernel paging request at virtual address 300af87d
[ 12.270342] Unable to handle kernel paging request at virtual address 300af87d
...全文
181 7 打赏 收藏 转发到动态 举报
写回复
用AI写文章
7 条回复
切换为时间正序
请发表友善的回复…
发表回复
  • 打赏
  • 举报
回复
引用 3 楼 gooogleman 的回复:
已经找到原因,居然是文件系统不对的问题,是我有点点设置不对。 不过感觉这个android 2.3.4 不稳定啊,实验了一下和我的原来稳定的android2.3.1 没什么两样的,还是不升级了,不整先了, 把重心放在4412 的android4.0 上先!
我也遇到类似的问题了,有点纳闷,文件系统与MMU之间有什么关系呢,不过我也偿试换了几个文件系统问题还在,能分享下你这个问题的答案吧。
guodongfu 2014-10-17
  • 打赏
  • 举报
回复
大神能说一下,文件系统哪不对吗?
gooogleman 2013-05-23
  • 打赏
  • 举报
回复
引用 3 楼 gooogleman 的回复:
已经找到原因,居然是文件系统不对的问题,是我有点点设置不对。 不过感觉这个android 2.3.4 不稳定啊,实验了一下和我的原来稳定的android2.3.1 没什么两样的,还是不升级了,不整先了, 把重心放在4412 的android4.0 上先!
android2.3.4 有时候他会有点怪怪的,开机重启30~50次总有那么一次不启动成功。 问题倒是不大,不过我的S5pv210 原有的android2.3.1 却表现很稳定,GPU 也不会打印那些信息。
gooogleman 2013-05-23
  • 打赏
  • 举报
回复
明天结贴,快来接分!
gooogleman 2013-05-23
  • 打赏
  • 举报
回复
已经找到原因,居然是文件系统不对的问题,是我有点点设置不对。 不过感觉这个android 2.3.4 不稳定啊,实验了一下和我的原来稳定的android2.3.1 没什么两样的,还是不升级了,不整先了, 把重心放在4412 的android4.0 上先!
xqhrs232 2013-05-23
  • 打赏
  • 举报
回复
你这个错误像是LINUX下的典型错误啊!
gooogleman 2013-05-23
  • 打赏
  • 举报
回复
换了一个内核,照样会。汗! 看来只能不关闭MMU先了。

80,351

社区成员

发帖
与我相关
我的任务
社区描述
移动平台 Android
androidandroid-studioandroidx 技术论坛(原bbs)
社区管理员
  • Android
  • yechaoa
  • 失落夏天
加入社区
  • 近7日
  • 近30日
  • 至今
社区公告
暂无公告

试试用AI创作助手写篇文章吧