[Prism54-devel] 2.4.23 Kernel oops

[Sven Geggus]

Hi there,

trying to use the cvs20031208 CVS snapshot (Kernel patch) in conjunction
with 2.4.23 (vanilla + xfs patch applied) I get the following Kernel-oops.
May the problem arise becaue of the ipv6 support enabled in my Kernel?

ksymoops 2.4.5 on i686 2.4.23-xfs.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.4.23-xfs/ (default)
     -m /boot/System.map-2.4.23-xfs (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.

CPU:    0
EIP:    0010:[<c886ec83>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010246
eax: 00000000   ebx: 00000000   ecx: 00000286   edx: c6d0e79c
esi: c4091f74   edi: c6d0e160   ebp: c4091f80   esp: c4091df4
ds: 0018   es: 0018   ss: 0018
Process keventd (pid: 2, stackpage=c4091000)
Stack: c6d0e160 c6d0e280 c4091fe0 00000000 c7834000 c6f76140 00000000 00000246 
       c4091e2c c0114d21 c4091e2c c4091e2c 00000286 0000000a 00000000 00000000 
       00004029 c4090000 c50a3c00 c6d0e160 c6d0e7cc 00000001 c886e370 c50a3c00 
Call Trace: [schedule_timeout+121/148]  [<c886e370>]  [schedule+762/804]  [wait_for_completion+118/164]  [__free_pages+27/28]  [free_pages+26/28]  [release_task+342/364]  [sys_wait4+899/912]  [<c886f836>]  [__run_task_queue+80/92]  [context_thread+283/416]  [arch_kernel_thread+40/56] 
Code: 0f 0b 6c 01 d8 6d 87 c8 90 8d 74 26 00 8b 87 5c 08 00 00 bb 


>>EIP; c886ec83 <END_OF_CODE+fbfc/????>   <=====

>>edx; c6d0e79c <_end+69546e0/847ff44>
>>esi; c4091f74 <_end+3cd7eb8/847ff44>
>>edi; c6d0e160 <_end+69540a4/847ff44>
>>ebp; c4091f80 <_end+3cd7ec4/847ff44>
>>esp; c4091df4 <_end+3cd7d38/847ff44>

Code;  c886ec83 <END_OF_CODE+fbfc/????>
00000000 <_EIP>:
Code;  c886ec83 <END_OF_CODE+fbfc/????>   <=====
   0:   0f 0b                     ud2a      <=====
Code;  c886ec85 <END_OF_CODE+fbfe/????>
   2:   6c                        insb   (%dx),%es:(%edi)
Code;  c886ec86 <END_OF_CODE+fbff/????>
   3:   01 d8                     add    %ebx,%eax
Code;  c886ec88 <END_OF_CODE+fc01/????>
   5:   6d                        insl   (%dx),%es:(%edi)
Code;  c886ec89 <END_OF_CODE+fc02/????>
   6:   87 c8                     xchg   %ecx,%eax
Code;  c886ec8b <END_OF_CODE+fc04/????>
   8:   90                        nop    
Code;  c886ec8c <END_OF_CODE+fc05/????>
   9:   8d 74 26 00               lea    0x0(%esi,1),%esi
Code;  c886ec90 <END_OF_CODE+fc09/????>
   d:   8b 87 5c 08 00 00         mov    0x85c(%edi),%eax
Code;  c886ec96 <END_OF_CODE+fc0f/????>
  13:   bb 00 00 00 00            mov    $0x0,%ebx


1 warning issued.  Results may not be reliable.

Regards

Sven

P.S.: Pleas CC me in your reply, as Im not on your list.

-- 
Sven Geggus @ Fraunhofer IITB, Fraunhoferstr. 1, 76131 Karlsruhe, Germany
Web: http://wsd.iitb.fhg.de/ Phone: +49 721 6091-422, Fax: +49 721 6091-213
Linux powered DATA aquisition and evaluation, embedded systems,
combustion engine diagnosis