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

custar

我们在使用的核心板是OMAPL138 128M内存规格，但是在开发板快速体验手册中提供的U-BOOT参数配置命令是：从SD卡启动：
9 e) i) l+ O3 T7 c在3秒内按任意键进入u-boot命令行，执行以下命令设置为SD卡启动：
: J7 m! O" x/ V/ B3 gU-Boot > setenv bootcmd 'mmcinfo;mmc init;fatload mmc 0 c0700000 uImage;bootm'
& t( |. x: Q. D3 H, | U-Boot > setenv bootargs console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootfstype=ext3 mem=128M
4 Y7 ?# e& r3 L& c! `
从FLASH启动：
1 G) s" V& _& E4 g$ \在U-Boot命令行执行以下命令来设置为NAND FLASH启动系统。
: H) ?6 r* \7 N. vU-Boot > setenv bootcmd 'nboot.e 0xc0700000 0 0x120000; bootm'
6 f$ C( g4 [1 p/ B9 B0 y6 r' VU-Boot > setenv bootargs 'console=ttyS2,115200n8 ip=off ubi.mtd=4,2048 root=ubi0_0 rootfstype=ubifs mem=32M@0xc0000000 mem=64M@0xc4000000'
) D0 F- d0 w" x+ U; y( T U-Boot > saveenv
- b5 Y$ n0 Y1 b. a' m4 J( }0 ~1 B1 S1 |3 y
# S: ?7 F8 [& R& ?) m! b! R& i0 p
请问这是笔误还是从SD卡启动和从NAND启动内存大小设置不同？
另外我设置从NAND启动 内存大小为128M，在 rc5.d中创建s99restart脚本，内容为
sleep 5
2 g3 ?6 O1 Q* c0 N1 a. xreboot
4 e$ R/ A/ ~* \5 z3 Y) s意图是通过不断的热启动来验证系统UBIFS对NAND的读写是否稳定，但是发现会概率性出现以下的段访问异常错误，掉电重启后又恢复正常，
2 b( u' |8 D3 G4 M# p内核版本为创龙提供的2014.11.15的版本，请问这会是什么原因导致的，错误信息如下：

[    2.637774] UBI: attaching mtd4 to ubi0
* J/ n9 X0 _3 E[    2.641673] UBI: physical eraseblock size:   131072 bytes (128 KiB)
  `4 W. }' p/ A) f# G, `[    2.648283] UBI: logical eraseblock size:    126976 bytes
[    2.653769] UBI: smallest flash I/O unit:    2048
[    2.658648] UBI: sub-page size:              512
[    2.663309] UBI: VID header offset:          2048 (aligned 2048)
6 o. \$ Y: W  i, V1 N; Q( E[    2.669464] UBI: data offset:                4096
[    6.060848] UBI: max. sequence number:       2386299
: N  v+ A+ u* `2 v3 A) d* W$ B[    6.083946] Unable to handle kernel paging request at virtual address 872281a4
[    6.091390] pgd = c0004000
  {! [% A: C" U/ `6 @7 I' o$ O4 l; K[    6.094134] [872281a4] *pgd=00000000
[    6.097850] Internal error: Oops: 805 [#1] PREEMPT
, t" S" D3 O! y+ |* }& y% ^* K[    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
$ n6 a# A& \9 m5 [2 r[    6.119794] sp : c7835e40  ip : c7b6fc90  fp : c7835e6c
[    6.131337] r10: c7950b78  r9 : c05cbd68  r8 : c7950b84
; v! O6 A6 w2 }* t; E' y, M[    6.136600] r7 : c7b9e860  r6 : c7bb0090  r5 : c7950800  r4 : c7bb0078
: z: l, e& \* X/ ~6 x* x[    6.143174] r3 : c7b68000  r2 : afdb0069  r1 : c7950b78  r0 : c7b6fc90
4 C& Z( N* v5 x1 o- C[    6.149751] Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
[    6.157111] Control: 0005317f  Table: c0004000  DAC: 00000017
1 J- I9 A) A% u  S4 L& I[    6.162898] Process swapper (pid: 1, stack limit = 0xc7834270)
! i6 H0 q$ i9 `[    6.168773] Stack: (0xc7835e40 to 0xc7836000)
[    6.173179] 5e40: 00000081 00000000 c7950800 c7906a80 00000000 00000000 00000000 00000000
; b0 G. t' P9 }$ `1 {  C8 |1 r, L[    6.181433] 5e60: c7835f64 c7835e70 c023a224 c024011c c7835eb4 c7835e80 c7835eb4 c7b9ce00
[    6.189685] 5e80: c00e380c c0407108 c7835eb4 c7835e98 c00e2ea4 c00e2d28 00000000 c794cfa0
& c7 T" a/ ^) Z$ g' [- m1 E0 P[    6.197935] 5ea0: 00000000 c78c6320 c7835ef4 c7835eb8 c00e40ac c00e3800 00000000 c7835ed0
[    6.206188] 5ec0: c7835ef4 c7835ed0 c78c6320 00000000 c05bb8a4 c780ec00 c04f7caa 00000000
$ B5 J3 L+ c1 V! N; _% ~& u% u; n# C[    6.214442] 5ee0: 00000014 c04f7caa c7835f04 c7835ef8 c780ec00 00000018 c7835f38 c057c08c
[    6.222691] 5f00: 00000014 c7835f7c c057c08c c057c08c 00000000 00000000 00000000 00000000
# R8 h; R6 e' m: Y[    6.230941] 5f20: c7835f54 c7835f30 c01a327c c01a739c 00000000 0000000a c7b9ce00 c05cbce8
[    6.239191] 5f40: c7b9ce00 c057c08c 00000000 00000000 00000000 00000000 c7835fa4 c7835f68
- n: x$ f: [$ E+ {" X[    6.247444] 5f60: c0567b60 c0239d70 00000000 c7835f78 c01ed618 c01ed5a8 c057e848 c057c08d
[    6.255695] 5f80: c001baf0 c057e84c c055120c c001baf0 00000013 c0567998 c7835fdc c7835fa8
5 j) h/ N5 a0 `" u6 M! `5 f, n[    6.263949] 5fa0: c00087ec c05679a8 c7835fc4 c7835fb8 c0038acc c01a06e8 c057e84c c055120c
; q" E- z& Y' i; s) g, R[    6.272200] 5fc0: c001baf0 00000013 00000000 00000000 c7835ff4 c7835fe0 c0551288 c000875c
9 u4 Y9 A1 U( a& G/ ]2 q[    6.280451] 5fe0: 00000000 c055120c 00000000 c7835ff8 c001baf0 c055121c 00004010 00005019
5 v. \  V* o3 Z, x% X3 s6 O& c1 V5 p[    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)
[    6.309642] [<c0567998>] (ubi_init+0x0/0x2d4) from [<c00087ec>] (do_one_initcall+0xa0/0x178)
' O- Z% `: N9 d. H[    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)
[    6.333766] [<c055120c>] (kernel_init+0x0/0x124) from [<c001baf0>] (do_exit+0x0/0x720)
/ G0 A: K/ x9 m[    6.341738]  r5:c055120c r4:00000000
[    6.345365] Code: e58c2010 e5943000 e58c300c e59533f8 (e783c102)
[    6.351895] ---[ end trace c93823a902b142fe ]---
8 d! ]9 U" d0 @/ R% D3 b# Y! J[    6.356612] Kernel panic - not syncing: Attempted to kill init!

$ H# X! q5 v+ p/ X3 |

nihao123

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

custar

nihao123 发表于 2015-8-14 10:56
+ ?4 Z* \9 q) D! \! N我也遇到过，是重新做的文件系统

) f/ j( O5 D. G( F+ n: O. I不太像文件系统的问题。