Erik Forsberg writes:
 > Nikita Danilov <[EMAIL PROTECTED]> writes:
 > 
 > > 
 > > Can you please try to run /usr/sbin/ksymoops on oops traceback
 > > above. I am not sure that ksymoops can handle Alpha traceback, though.
 > 
 > Hmm..
 > 
 > Ksymoops is available on the platform, but I'm not entirely sure my
 > Oops is correctly formatted, because the output looks like this:

(Just to double-check: you have ran ksymoops on Alpha, right?)

 > 
 > --snip--
 > lanfear:forsberg ~ % ksymoops -m /usr/src/linux/System.map ksymoops.alpha.reiser 
 > ksymoops 2.4.1 on alpha 2.4.6.  Options used
 >      -V (default)
 >      -k /proc/ksyms (default)
 >      -l /proc/modules (default)
 >      -o /lib/modules/2.4.6/ (default)
 >      -m /usr/src/linux/System.map (specified)
 > 
 > No modules in ksyms, skipping objects
 > Warning (read_lsmod): no symbols in lsmod, is /proc/modules a valid lsmod file?
 > Warning (compare_maps): mismatch on symbol partition_name  , ksyms_base says 
 >fffffc00004ad420, System.map says fffffc000037e8c0.  Ignoring ksyms_base entry
 > Unable to handle kernel paging request at virtual address 3ffffc00b7c86020
 > bonnie++(380): Oops 0
 > pc = [<fffffc00004aa260>]  ra = [<fffffc00004aa4c0>]  ps = 0000
 > Using defaults from ksymoops -t elf64-alpha -a alpha
 > 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
 > Warning (Oops_code): trailing garbage ignored on Code: line
 >   Text: 'Code: 42f50406  addq t9,a5,t5'
 >   Garbage: 'q t9,a5,t5'
 > Error (Oops_code_values): invalid value 0xadd in Code line, must be 2, 4, 8 or 16 
 >digits, value ignored
 > 
 > >>PC;  fffffc00004aa260 <raid1_read_balance+180/200>   <=====
 > Code;  fffffc00004aa260 <raid1_read_balance+180/200>
 > 0000000000000000 <_PC>:
 > Code;  fffffc00004aa260 <raid1_read_balance+180/200>
 >    0:   06 04 f5 42       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
 >  40649523  subq t2,36,t2
 > Trace:4ad110 351644 436464 436540 350a40 3527f8 3dc8e0 34684c 346a0c 3468c8 3d74e0 
 >33a99c 33acd4 33b21c 33b140 34dd2c 310da0 
 > Warning (Oops_read): Code line not seen, dumping what data is available
 > 
 > Trace; 00000000004ad110 Before first symbol
 > Trace; 0000000000351644 Before first symbol
 > Trace; 0000000000436464 Before first symbol
 > Trace; 0000000000436540 Before first symbol
 > Trace; 0000000000350a40 Before first symbol
 > Trace; 00000000003527f8 Before first symbol
 > Trace; 00000000003dc8e0 Before first symbol
 > Trace; 000000000034684c Before first symbol
 > Trace; 0000000000346a0c Before first symbol
 > Trace; 00000000003468c8 Before first symbol
 > Trace; 00000000003d74e0 Before first symbol
 > Trace; 000000000033a99c Before first symbol
 > Trace; 000000000033acd4 Before first symbol
 > Trace; 000000000033b21c Before first symbol
 > Trace; 000000000033b140 Before first symbol
 > Trace; 000000000034dd2c Before first symbol
 > Trace; 0000000000310da0 Before first symbol
 > 
 > 
 > 4 warnings and 1 error issued.  Results may not be reliable.
 > --snap--
 > 
 > The "Code line not seen.." line doesn't sound good to me.

Well, then, if you still courageous enough, do it hard manual way: take
each address from the traceback: 4ad110 351644 436464 436540 350a40
3527f8 3dc8e0 34684c 346a0c 3468c8 3d74e0 33a99c 33acd4 33b21c 33b140
34dd2c 310da0, and check by /proc/ksyms what function this address is
in. All kernel addresses have the same "prefix" part (fffffc0000),
prepend it to an address from traceback and search in the /proc/ksyms
greatest address less than result.

This doesn't look at the most interesting work on the Earth, yes.

 > 
 > \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