My previous theory about the position of drives cause oops is now proven
incorrect, this is the output from the latest crash.

How can i use this to track an error back to some c code ?

Does this look interesting to anyone ?


ksymoops 2.3.4 on i686 2.3.99-pre6.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.3.99-pre6/ (default)
     -m /boot/System.map-2.3.99-pre6 (default)

Warning: You did not tell me where to find symbol information.  I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc.  ksymoops -h explains the options.

No modules in ksyms, skipping objects
Warning (read_lsmod): no symbols in lsmod, is /proc/modules a valid
lsmod file?
CPU:    0
EIP:    0010:[<c01e9abb>]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00000006
eax: 00000050   ebx: c127dee0   ecx: c010db01   edx: 00009807
esi: c12d2da0   edi: 00000286   ebp: c03e4ec0   esp: c1273d80
ds: 0018   es: 0018   ss: 0018
Process swapper (pid: 1, stackpage=c1273000)
Stack: c127dee0 04000001 00000000 00000012 c010db01 00000000 c010db01
00000012
       c12d2da0 c1273de4 c0349a40 c0349a50 00000012 c1273ddc c010de34
00000012
       c1273de4 c127dbe0 c03e4f00 00000282 c1291128 00000000 c127dbe0
c1273e68
Call Trace: [<c010db01>] [<c010db01>] [<c010de34>] [<c010bee0>]
[<c01e0018>] [<c01ad1ab>] [<c013efd1>]
       [<c0140b61>] [<c015b521>] [<c015b160>] [<c010bee0>] [<c015b23d>]
[<c015b1ca>] [<c01e82fb>] [<c0110018>]
       [<c01071cb>] [<c0109010>]
Code: 81 3d 28 f4 2f c0 ad 4e 74 19 6a 5c 68 80 e2 2b c0 68

>>EIP; c01e9abb <ide_intr+9f/358>   <=====
Trace; c010db01 <handle_IRQ_event+4d/78>
Trace; c010db01 <handle_IRQ_event+4d/78>
Trace; c010de34 <do_IRQ+114/1dc>
Trace; c010bee0 <ret_from_intr+0/20>
Trace; c01e0018 <slhc_init+c8/138>
Trace; c01ad1ab <generic_unplug_device+b7/bc>
Trace; c013efd1 <__wait_on_buffer+281/398>
Trace; c0140b61 <bread+45/64>
Trace; c015b521 <msdos_partition+6d/36c>
Trace; c015b160 <check_partition+90/d0>
Trace; c010bee0 <ret_from_intr+0/20>
Trace; c015b23d <grok_partitions+6d/b0>
Trace; c015b1ca <register_disk+26/2c>
Trace; c01e82fb <ide_geninit+53/68>
Trace; c0110018 <handle_vm86_fault+aa8/fb8>
Trace; c01071cb <init+5f/1e4>
Trace; c0109010 <kernel_thread+28/38>
Code;  c01e9abb <ide_intr+9f/358>
00000000 <_EIP>:
Code;  c01e9abb <ide_intr+9f/358>   <=====
   0:   81 3d 28 f4 2f c0 ad      cmpl   $0x19744ead,0xc02ff428   <=====
Code;  c01e9ac2 <ide_intr+a6/358>
   7:   4e 74 19 
Code;  c01e9ac5 <ide_intr+a9/358>
   a:   6a 5c                     push   $0x5c
Code;  c01e9ac7 <ide_intr+ab/358>
   c:   68 80 e2 2b c0            push   $0xc02be280
Code;  c01e9acc <ide_intr+b0/358>
  11:   68 00 00 00 00            push   $0x0


2 warnings issued.  Results may not be reliable.
--
=-          To unsubscribe, email [EMAIL PROTECTED] with the       -=
=-                body of "unsubscribe linux-abit".                 -=

Reply via email to