omapl138核心板系统热启动后ubifs报段地址访问异常错误

custar

我们在使用的核心板是OMAPL138 128M内存规格，但是在开发板快速体验手册中提供的U-BOOT参数配置命令是：从SD卡启动：
/ Q1 R. h& s1 i  k) F在3秒内按任意键进入u-boot命令行，执行以下命令设置为SD卡启动：
U-Boot > setenv bootcmd 'mmcinfo;mmc init;fatload mmc 0 c0700000 uImage;bootm'
! I6 T9 B1 F' V, t& N  } U-Boot > setenv bootargs console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootfstype=ext3 mem=128M
; T0 f0 Z4 @6 |. }5 X' N
6 S0 [$ f9 K' z+ \9 q  o* W从FLASH启动：
在U-Boot命令行执行以下命令来设置为NAND FLASH启动系统。
9 P6 v4 ]4 V( G+ I' P1 QU-Boot > setenv bootcmd 'nboot.e 0xc0700000 0 0x120000; bootm'
U-Boot > setenv bootargs 'console=ttyS2,115200n8 ip=off ubi.mtd=4,2048 root=ubi0_0 rootfstype=ubifs mem=32M@0xc0000000 mem=64M@0xc4000000'
U-Boot > saveenv
, J7 a' p% x9 K4 X- z$ s6 @
9 A2 t3 @" A& ?4 e. j( S
请问这是笔误还是从SD卡启动和从NAND启动内存大小设置不同？
另外我设置从NAND启动 内存大小为128M，在 rc5.d中创建s99restart脚本，内容为
6 I+ k- ?, v8 W/ R$ E* E4 Ksleep 5
( V" M: [# a- Y$ I, E6 [/ creboot
意图是通过不断的热启动来验证系统UBIFS对NAND的读写是否稳定，但是发现会概率性出现以下的段访问异常错误，掉电重启后又恢复正常，
- J. c) i  h5 g# {# a内核版本为创龙提供的2014.11.15的版本，请问这会是什么原因导致的，错误信息如下：

[    2.637774] UBI: attaching mtd4 to ubi0
& E( V8 F5 s+ O4 i$ d, a5 n[    2.641673] UBI: physical eraseblock size:   131072 bytes (128 KiB)
+ N) j! I( B0 p! {; i2 ]1 I1 p5 o[    2.648283] UBI: logical eraseblock size:    126976 bytes
[    2.653769] UBI: smallest flash I/O unit:    2048
[    2.658648] UBI: sub-page size:              512
  |( F) _% c7 j( G! J' y( h[    2.663309] UBI: VID header offset:          2048 (aligned 2048)
[    2.669464] UBI: data offset:                4096
[    6.060848] UBI: max. sequence number:       2386299
, u+ W% B1 y& \* H: ]3 _; j2 C[    6.083946] Unable to handle kernel paging request at virtual address 872281a4
[    6.091390] pgd = c0004000
. e2 n6 D6 \) ~3 \) d( C8 q[    6.094134] [872281a4] *pgd=00000000
* p9 v3 k% d) ?& V  ][    6.097850] Internal error: Oops: 805 [#1] PREEMPT
[    6.102678] Modules linked in:
[    6.105775] CPU: 0    Not tainted  (3.3.0 #15)
[    6.110284] PC is at ubi_wl_init_scan+0x218/0x31c
[    6.115032] LR is at ubi_wl_init_scan+0x1f8/0x31c
[    6.119777] pc : [<c0240324>]    lr : [<c0240304>]    psr: a0000013
6 }1 h6 R1 g3 F2 Q+ D[    6.119794] sp : c7835e40  ip : c7b6fc90  fp : c7835e6c
( [1 g( b% @1 t! z6 X[    6.131337] r10: c7950b78  r9 : c05cbd68  r8 : c7950b84
7 k2 S, U+ @# ?6 i$ K[    6.136600] r7 : c7b9e860  r6 : c7bb0090  r5 : c7950800  r4 : c7bb0078
: T! w0 e7 r9 m4 T* K( ?2 K0 o[    6.143174] r3 : c7b68000  r2 : afdb0069  r1 : c7950b78  r0 : c7b6fc90
2 x- Y( ]' b& {* c1 N  C[    6.149751] Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
$ E% i: L$ @/ l0 `" o( v  m! w" r# n[    6.157111] Control: 0005317f  Table: c0004000  DAC: 00000017
[    6.162898] Process swapper (pid: 1, stack limit = 0xc7834270)
[    6.168773] Stack: (0xc7835e40 to 0xc7836000)
4 t6 q" i% \3 B& j. o, G[    6.173179] 5e40: 00000081 00000000 c7950800 c7906a80 00000000 00000000 00000000 00000000
! K! U+ A' ?  S) U# }[    6.181433] 5e60: c7835f64 c7835e70 c023a224 c024011c c7835eb4 c7835e80 c7835eb4 c7b9ce00
0 [8 b) [: t+ [& E7 X6 c[    6.189685] 5e80: c00e380c c0407108 c7835eb4 c7835e98 c00e2ea4 c00e2d28 00000000 c794cfa0
[    6.197935] 5ea0: 00000000 c78c6320 c7835ef4 c7835eb8 c00e40ac c00e3800 00000000 c7835ed0
[    6.206188] 5ec0: c7835ef4 c7835ed0 c78c6320 00000000 c05bb8a4 c780ec00 c04f7caa 00000000
1 Z# m& Y( n& B# a3 ^[    6.214442] 5ee0: 00000014 c04f7caa c7835f04 c7835ef8 c780ec00 00000018 c7835f38 c057c08c
[    6.222691] 5f00: 00000014 c7835f7c c057c08c c057c08c 00000000 00000000 00000000 00000000
[    6.230941] 5f20: c7835f54 c7835f30 c01a327c c01a739c 00000000 0000000a c7b9ce00 c05cbce8
[    6.239191] 5f40: c7b9ce00 c057c08c 00000000 00000000 00000000 00000000 c7835fa4 c7835f68
[    6.247444] 5f60: c0567b60 c0239d70 00000000 c7835f78 c01ed618 c01ed5a8 c057e848 c057c08d
[    6.255695] 5f80: c001baf0 c057e84c c055120c c001baf0 00000013 c0567998 c7835fdc c7835fa8
[    6.263949] 5fa0: c00087ec c05679a8 c7835fc4 c7835fb8 c0038acc c01a06e8 c057e84c c055120c
, i$ l( L  B: U" V[    6.272200] 5fc0: c001baf0 00000013 00000000 00000000 c7835ff4 c7835fe0 c0551288 c000875c
[    6.280451] 5fe0: 00000000 c055120c 00000000 c7835ff8 c001baf0 c055121c 00004010 00005019
[    6.288678] Backtrace:
[    6.291178] [<c024010c>] (ubi_wl_init_scan+0x0/0x31c) from [<c023a224>] (ubi_attach_mtd_dev+0x4c4/0xb24)
[    6.300767] [<c0239d60>] (ubi_attach_mtd_dev+0x0/0xb24) from [<c0567b60>] (ubi_init+0x1c8/0x2d4)
; L% K. B+ ^9 ^5 c[    6.309642] [<c0567998>] (ubi_init+0x0/0x2d4) from [<c00087ec>] (do_one_initcall+0xa0/0x178)
/ [; u7 @6 N# c. W: K: ~$ N9 c[    6.318137]  r8:c0567998 r7:00000013 r6:c001baf0 r5:c055120c r4:c057e84c
[    6.324958] [<c000874c>] (do_one_initcall+0x0/0x178) from [<c0551288>] (kernel_init+0x7c/0x124)
+ K5 e: P" e9 o[    6.333766] [<c055120c>] (kernel_init+0x0/0x124) from [<c001baf0>] (do_exit+0x0/0x720)
, I/ h* e, C9 q, i& A[    6.341738]  r5:c055120c r4:00000000
[    6.345365] Code: e58c2010 e5943000 e58c300c e59533f8 (e783c102)
[    6.351895] ---[ end trace c93823a902b142fe ]---
[    6.356612] Kernel panic - not syncing: Attempted to kill init!
, a$ J3 ]5 _7 W1 j

nihao123

我也遇到过，是重新做的文件系统

custar

nihao123 发表于 2015-8-14 10:56
) B  x7 ~7 O- R8 F* P# J7 O我也遇到过，是重新做的文件系统

不太像文件系统的问题。