Re: incomplete kdb backtraces in 2.4.20 with gcc 3.3.4

[Keith Owens]

On Wed, 2 Feb 2005 09:33:29 -0800, 
Bruce Edge <[EMAIL PROTECTED]> wrote:
>Here's the backtrace info:
>
>[3]kdb> bt
>Stack traceback for pid 1268
>0xba282000     1268     1247  1    3   R  0xba282370 *svm_sac
>EBP        EIP        Function (args)
>0xba283ea8 0xc547a956 [t3-css]sendreq_psc (0xb3a83dc8, 0xba283e7c, 0x4010a830, 
>0xba283e68, 0x4010a856)
>                              t3-css .text 0xc5439060 0xc547a956 0xc547b0f2
>          0xc548e93e [t3-css]css_send_kio+0x181 (0x0, 0x0, 0xb3a83e54, 
> 0xb3a83e54, 0xb3a83dc8)
>                              t3-css .text 0xc5439060 0xc548e7bd 0xc548f11c
>          0x4010970c error_code+0x34
>                              kernel .text 0x40100000 0x401096d8 0x40109714
>Interrupt registers:
>eax = 0xb3a83ed0 ebx = 0x00000000 ecx = 0x00000000 edx = 0xb3a83e54 esi = 
>0xb3a83e54 edi = 0xb3a83dc8 esp = 0xb3a83e54 eip = 0x00000018 ebp = 0xb3a83e54 
>xss = 0xb3a83ed0 xcs = 0xffffffff eflags = 0xb3a83e54 xds = 0xba283f48 xes = 
>0x00000000 origeax = 0x00000018 &regs = 0xba283e6c
>Interrupt from user space, end of kernel trace
>[3]kdb> rd
>eax = 0xb3a83dc8 ebx = 0xb3a83dd0 ecx = 0xb4800180 edx = 0xb4800180 esi = 
>0xb48002d8 edi = 0xb3a83ed0 esp = 0xba283e2c eip = 0xc547a956 ebp = 0xba283ea8 
>xss = 0x40300018 xcs = 0x00000010 eflags = 0x00000202 xds = 0xb3a80018 xes = 
>0x00000018 origeax = 0xffffffff &regs = 0xba283df8
>[3]kdb> md 0xba283e2c
>0xba283e2c c548e93e b3a83dc8 ba283e7c 4010a830   >�H��=��|>(�0�.@

mds is better for dumping stack contents, it does word by word with
automatic symbolic lookup.

Time to debug the debugger :(.  Reproduce the problem and send me (not
the list) the output from these kdb commands

  set LINES 20000
  bt
  set KDBDEBUG 0xffff
  bt
  set KDBDEBUG 0
  set MDCOUNT 0x200
  mds %esp-0x200
  set MDCOUNT 10

That will generate quite a bit of output.  I assume that you can run a
serial console and capture the kdb output over the serial console.  If
you cannot capture using a serial console then issue 'set LOGGING 1'
first, when you type go the kdb output will be sent to syslog.  Of
course that assumes that the system can resume and still log to disk, a
serial console is much better.


---------------------------
Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe.