Erik Forsberg writes:
 > Hi!
 > 
 > I'm trying to use ReiserFS (no special version, just compiled into the
 > 2.4.6 kernel) on a Alpha/366 (XLT) on top of a new-style (also from
 > the 2.4.6 kernel) raid1 device.
 > 
 > I'm experiencing Oops. Like this one:
 > 
 > Unable to handle kernel paging request at virtual address 3ffffc00b7c86020
 > bonnie++(380): Oops 0
 > pc = [<fffffc00004aa260>]  ra = [<fffffc00004aa4c0>]  ps = 0000
 > v0 = 00000000001c0540  t0 = 0000000000000000  t1 = 00000000001ab018
 > t2 = 3ffffc00b7c86040  t3 = 3ffffc00b7c86020  t4 = 0000000000000001
 > t5 = 3ffffc00b7c86018  t6 = 0000000000000002  t7 = fffffc0005408000
 > s0 = fffffc0007b9d8e8  s1 = 0000000000000900  s2 = fffffc0006f4a000
 > s3 = fffffc000676b300  s4 = fffffc0007b9d8c0  s5 = 0000000000000000
 > s6 = fffffc000709aea0
 > a0 = fffffc0006f4a000  a1 = fffffc000676b300  a2 = 0000000000000000
 > a3 = 0000000000000001  a4 = 0000000000000008  a5 = fffffc0006f4a018
 > t8 = 0000000000000024  t9 = 40000000b0d3c024  t10= 00000000001ab018
 > t11= fffffc0006f4a020  pv = fffffc000051e320  at = fffffc0006f4a01c
 > gp = fffffc00005ef2b0  sp = fffffc000540bc08
 > Code: 42f50406  addq t9,a5,t5
 >  a0f003d8  ldl t6,984(a0)
 >  42fc0403  addq t9,at,t2
 >  42f90404  addq t9,t11,t3
 >  40849524  subq t3,36,t3
 >  40c49526  subq t5,36,t5
 > *a0240000  ldl t0,0(t3)
 >  40649523  subq t2,36,t2
 > 
 > Trace:4ad110 351644 436464 436540 350a40 3527f8 3dc8e0 34684c 346a0c 3468c8 3d74e0 
 >33a99c 33acd4 33b21c 33b140 34dd2c 310da0 
 > 
 > (I was running the disk benchmarking program bonnie++ at the time).
 > 
 > First I suspected hardware errors, since one of the disks have behaved
 > oddly before, but after unconnecting that (running the raid mirror
 > with only one disk) I still got Oops. The above Oops is with only one
 > disk in the raidset.
 > 
 > I then deleted my raidset (This is not a production system - yet) and
 > made a ReiserFS on the raw partition previously used for the raidset,
 > and now bonnie++ went through it's whole program execution without
 > Oops.
 > 
 > This might very well not be a ReiserFS problem, but a Linux kernel
 > problem. Anyway, I thought I should ask here to see if anyone have
 > seen something like this before.
 > 
 > If there is any information I've not included that's needed, please
 > let me know!

Can you please try to run /usr/sbin/ksymoops on oops traceback
above. I am not sure that ksymoops can handle Alpha traceback, though.

 > 
 > \EF
 > -- 
 > Erik Forsberg                 http://www.lysator.liu.se/~forsberg/
 > GPG/PGP Key: 1024D/0BAC89D9 <[EMAIL PROTECTED]> 
 > Key Fingerprint: B308 87FC 566E 825A 5ABC  247C AC9B AB14 0BAC 89D9

Nikita.

Reply via email to