HI3515的Unable to handle kernel paging request错误

Divingbear

最近在用海思的HI3515设计一款工控机，第一版做完后，开始开发第二版，主要改动是增删了部分硬件功能，DDR颗粒从原来的HY5PS1G1631CFP-Y5C换成了H5PS1G63EFRY5C。
) t: v/ W# m6 Z8 `( y0 w 结果发现第二版的程序在引导过程中偶尔会出现Unable to handle kernel paging request的错误，且后边的地址经常会变化，并不是固定的错误。错误的引导信息如下：
+ d: V( O2 }# e4 E4 u% ?, {* F* pUnable to handle kernel NULL pointer dereference at virtual address 0000003c
pgd = c1de4000
0 @+ W( f7 P$ M+ R0 @' P [0000003c] *pgd=c1de3031, *pte=00000000, *ppte=00000000
Internal error: Oops: 817 [#1]
+ G! {2 m- y3 u- K9 g' L( K3 ? Modules linked in:
/ o: G, {/ S9 C' G( D* U CPU: 0    Not tainted  (2.6.24-rt1-hi3515v100 #24)
8 ~1 X3 a* m! a0 B- `  O5 H; h PC is at generic_file_aio_read+0x20/0x1a4
6 A  @: v$ c, i) B! P( v3 E7 w LR is at do_sync_read+0xc8/0x114
; \  g+ x8 K3 L" o  m pc : [<c0060904>]    lr : [<c007cc1c>]    psr: a0000013
8 u) y6 ^4 P4 @" C7 l1 e2 n sp : c1dd9d18  ip : 00000000  fp : c1dd9d60
r10: 00000000  r9 : 00000000  r8 : c1dd9e50
r7 : c1dd9d6c  r6 : c1dbb660  r5 : c1dd9dbc  r4 : c1dd9d74
% Y2 [* K) S' o$ S* Q r3 : 00000000  r2 : 00000001  r1 : 0000003c  r0 : c1dd9d74
Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
4 z0 A$ N& H1 c9 D' I  K, V5 G Control: 0005317f  Table: c1de4000  DAC: 00000017
$ @9 e# @' k  }' s3 K Process rcS (pid: 219, stack limit = 0xc1dd8258)
" j; s- `* K( D9 z) d9 V+ Y Stack: (0xc1dd9d18 to 0xc1dda000)
* P3 _4 r. Y1 c5 j' @, { 9d00:                                                       c0093cc4 c00f95cc
9d20: 00000000 c1dd9e28 c1dd9da4 c1dd9d38 c0085be8 c0093cb4 c1dd9d74 c1dd9dbc
: \5 V' }; j% U/ q0 p 9d40: c1dbb660 c1dd9d6c c1dd9e50 00000000 00000000 c1dd9e24 c1dd9d68 c007cc1c
" v4 j  ?. c  M+ b 9d60: c00608f8 00000000 00000000 c1d6bdc0 00000080 00000000 c1dd9fb0 00000000
9d80: 00000001 ffffffff c1dbb660 00000000 00000000 00000000 00000000 c1c5c0e0
; N! r+ ~& d2 v% N  k9 ]- o: d 9da0: 00000000 00000000 c1dd9de0 c1c5c0e0 c0049d48 c1dd9db4 c1dd9db4 00000000
* s6 r7 c: D( F% p5 X 9dc0: 00000000 c0044454 c0044004 c1dd9df8 c1dbb660 c1dd9e08 00000080 c007bde0
9de0: c0065b7c c1dbb660 c1dd9e28 c1dd9fb0 c1dd8000 c0294ac8 c1dd9fb0 00000080
* U% A! u, @$ y( R 9e00: c1dbb660 c1d6bdc0 c1dd9e50 c007cb54 00000000 c1dd9fb0 c1dd9e4c c1dd9e28
4 s  q6 t4 A+ W" b5 l 9e20: c007cd14 c007cb64 c1801b40 bf000000 00000000 c1dd9e50 c1dd8000 c0294ac8
9e40: c1dd9e70 c1dd9e50 c00814b8 c007cc78 00000000 00000000 00000080 c1d6bdc0
9e60: 00000000 c1dd9e8c c1dd9e74 c0081d24 c0081474 c1dd9e98 c1d6bdc0 c1dd9fb0
9e80: c1dd9f30 c1dd9e90 c00ad608 c0081c98 c1d6bdc2 00000000 6e69622f 0068732f
8 T* K/ i# O5 Y& C$ u 9ea0: c1db2320 beffff7b c1dd9ee8 c1dd9eb8 c006e3e4 00000000 00000020 00000000
9ec0: c1dd8000 00000001 00000000 c1d6bdc0 00000000 00000000 00000000 c1dd9f1c
. y8 F% T2 n" }- i) Q1 h) r- Q 9ee0: 00000000 00000000 00000000 c1dd9fb0 00000000 c1dd9efc 00000000 00000f7b
: ~, ?4 N) C* V* Z5 x; ]' X& q 9f00: c1dd9f1c c1dd9f10 c0294e54 c1d6bdc0 fffffffe c1dd8000 c0294e34 c1d6bdc0
2 ~! Z5 |9 u$ t  c7 {0 K 9f20: fffffff8 c1dd9f5c c1dd9f34 c0081fc0 c00ad3fc c1d6bdc0 beffff92 00000000
9f40: 001d7bcc 001d7bc4 c1dd8000 c1dd9fb0 c1dd9f84 c1dd9f60 c0082248 c0081f2c
7 n4 y6 l  n! `1 v 9f60: c1c99000 001d7bcc c1dd9fb0 c1c99000 c001ffe4 001c71fc c1dd9fa4 c1dd9f88
9f80: c00237c4 c0082124 001d7bc4 001d7ba4 00000001 0000000b 00000000 c1dd9fa8
9fa0: c001fe40 c0023798 001d7bc4 001d7ba4 001d7ba4 001d7bc4 001d7bcc 001d7ba4
, E7 Q! I. a; s0 s5 q4 q: ^) b 9fc0: 001d7bc4 001d7ba4 00000001 001d7bcc 001d7bcc 00000001 001c71fc 00000000
9fe0: 400833c4 be813a44 00069d44 400833cc 20000010 001d7ba4 00000000 00000000
Backtrace:
* l, d: a5 Z1 p5 Q8 L5 t" |! Y6 @ [<c00608e8>] (generic_file_aio_read+0x4/0x1a4) from [<c007cc1c>] (do_sync_read+0xc8/0x114)
. A7 X" e; s$ S [<c007cb54>] (do_sync_read+0x0/0x114) from [<c007cd14>] (vfs_read+0xac/0x144)
[<c007cc68>] (vfs_read+0x0/0x144) from [<c00814b8>] (kernel_read+0x54/0x84)
  r8:c0294ac8 r7:c1dd8000 r6:c1dd9e50 r5:00000000 r4:bf000000
  d: N* r/ ~9 S* q [<c0081464>] (kernel_read+0x0/0x84) from [<c0081d24>] (prepare_binprm+0x9c/0x108)
  r6:00000000 r5:c1d6bdc0 r4:00000080
+ L4 V! L* ^' i  q& B3 G [<c0081c88>] (prepare_binprm+0x0/0x108) from [<c00ad608>] (load_script+0x21c/0x240)
  r6:c1dd9fb0 r5:c1d6bdc0 r4:c1dd9e98
- x: @9 H8 {0 r: g% {' Q$ T' Y [<c00ad3ec>] (load_script+0x0/0x240) from [<c0081fc0>] (search_binary_handler+0xa4/0x1f8)
1 S' K4 O: V) Z+ J3 a  r6:fffffff8 r5:c1d6bdc0 r4:c0294e34
[<c0081f1c>] (search_binary_handler+0x0/0x1f8) from [<c0082248>] (do_execve+0x134/0x184)
* R2 W  v+ N6 [2 N- D [<c0082114>] (do_execve+0x0/0x184) from [<c00237c4>] (sys_execve+0x3c/0x5c)
" X" C  B$ s% m7 g% l5 h, p" ~ [<c0023788>] (sys_execve+0x0/0x5c) from [<c001fe40>] (ret_fast_syscall+0x0/0x2c)
  r7:0000000b r6:00000001 r5:001d7ba4 r4:001d7bc4
Code: e24dd020 e3a0c000 e58b3004 e1a04000 (e1a0a001)
  [% L* ~/ y8 W$ Z# F6 b8 j ---[ end trace e292f16b7bf51848 ]---
Segmentation fault
我先是把第一版和第二版上的NAND FLASH颗粒进行互换，发现新旧板上的颗粒在第一版的板子上都没有报错，而两个颗粒在第二版的板子上都会出现报错，初步确定问题是随着板子走的，而不是颗粒。
6 y6 U6 f1 c0 [" ` 然后将第二版上的硬件改动还原，尽量还原到和第一版一样，然后启动还是会出现报错信息，说明外围硬件的改动没有影响到引导驱动程序出错。
现在在把新板子寄回工厂，准备把DDR颗粒换成和第一版一样，然后再尝试一下，这个需要一些时间。
2 K* G+ k9 k& o7 X; j- B3 ` 然后比对了前后两种DDR颗粒的spec，未见明显的参数差别。
5 Q2 C  M) T6 Q  V" V
9 Y% ~2 }. N" V) h5 i  ?3 b" h
PS:
这几天集中研究了一下这个问题，汇报一下：
- r# b& D& ^* n( k& Z1 n 1.启动UBOOT后，用网络下载后边的文件到内存中的方式来启动，问题依旧会出现，排除掉NAND flash的问题。
7 ^" m/ f( i5 ^. W& T 2.抓了1.8V，VREF_DDR的电压波形,没有发现drop和ripple.排除电压的问题
3.把老板子上HY5PS1G1631CLFP-Y5C和新板子上的H5PS1G63EFR-Y5C互换了一下。旧版运行到现在一次都没出错
而新版运行到现在报过一次错。
4.买了几颗HY5PS1G1631CFP-Y5C（与原来板子上DDR比较少了一个L,原来的DDR颗粒停产了，现在这个颗粒IDD6电流略高，其他参数一样）换到板上，暂时还没看到报错，还需多跑跑看。
5.基于以上的实验，感觉是layout的问题，查了新旧版的走线，是完全一样的，etch length和manhattan length一样。
6.准备再次比对堆叠厚度，因为前后两版PCB是不同的厂子压合的，板子堆叠厚度是根据我提供的匹配阻抗由板厂自己计算的。

wenqing89

牛人，不过3515 支持的DDR2,最大200MHz吧，对布线要求这么高嘛？