[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: [rtl] kernel crashes with RT-Linux



Thomasz,

thank you very much for your help.

I installed the insmod-wrapper as the systems "standard" insmod, reproduced the
crash and got the oops run through the decoder program you sent me.
There I get the following

3027 symbols from /boot/System.map
  13 symbols [4816000-4816730] from /lib/modules/loadmaps/rt_com
  30 symbols [481d000-481df2c] from /lib/modules/loadmaps/rt_hidaq
  24 symbols [4818000-4819828] from /lib/modules/loadmaps/rtl_fifo
  21 symbols [481b000-481b66c] from /lib/modules/loadmaps/rtl_sched

EIP:   0x0481d960 t (rt_hidaq+)rt_hidaq_putSR400+0x0/0x40
EIP:   <0481d960>                               [klogd]
trace: 0x048188c2 t (rtl_fifo+)rtf_write+0x1de/0x1f4
trace: 0x00125a27 T sys_write+0x14b/0x184
trace: 0x0010b65e T s_sti+0x4e/0x50
trace: 0x0010a685 T system_call+0x55/0x7c


So the actually offending function is rt_hidaq_putSR400 ?
Can I read the trace the same way as a backtrace in gdb ? So I assume
rt_hidaq_putSR400 was called by rtf_write which in turn was called by
sys_write, ... . That would make sense to me. But I haven't found any bug in
that function (or even in the related functions) yet.

What seems to give most info to me, are the numbers in
rt_hidaq_putSR400+0x0/0x40 - What do they mean ?


The following oops is what I got right after the first, but I guess it's just a
followup induced by the first ?


EIP:   0x0010ab90 T die_if_kernel+0x280/0x2c0
EIP:   <0010ab90>                               [klogd]
trace: 0x0018002b T vt_ioctl+0x123f/0x1b44
trace: 0x04800000 B _ctmp+0x4627a74/0x463da74
trace: 0x05000000 ???
trace: 0x04800000 B _ctmp+0x4627a74/0x463da74
trace: 0x001138ba T do_page_fault+0x2ce/0x2e0
trace: 0x001135ec T do_page_fault+0x0/0x2e0
trace: 0x0010a7f8 t error_code+0x40/0x48
trace: 0x0481d960 t (rt_hidaq+)rt_hidaq_putSR400+0x0/0x40
trace: 0x0481d960 t (rt_hidaq+)rt_hidaq_putSR400+0x0/0x40
trace: 0x048188c2 t (rtl_fifo+)rtf_write+0x1de/0x1f4
trace: 0x00125a27 T sys_write+0x14b/0x184
trace: 0x0010b65e T s_sti+0x4e/0x50
trace: 0x0010a685 T system_call+0x55/0x7c
code:  00000000 <oops>:
code:     0:    64 8a 04 0e     movb   %fs:(%esi,%ecx,1),%al
code:     4:    0f a1           popl   %fs
code:     6:    88 c2           movb   %al,%dl
code:     8:    81 e2 ff 00 00  andl   $0xff,%edx
code:     d:    00
code:     e:    89 54 24 10     movl   %edx,0x10(%esp,1)
code:    12:    52              pushl  %edx
code:    13:



Greetings,
Jochen
-----------------------------------------------------------------------
  Jochen K"upper

  Heinrich-Heine-Universit"at D"usseldorf   jochen@uni-duesseldorf.de
  Institut f"ur Physikalische Chemie I
  Universit"atsstr. 1, Geb 26.43 Raum 02.29    phone ++49-211-8113681
  40225 D"usseldorf                            fax   ++49-211-8115195
  Germany             http://www-public.rz.uni-duesseldorf.de/~jochen
-----------------------------------------------------------------------
--- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail majordomo@rtlinux.cs.nmt.edu OR
echo "unsubscribe rtl <Your_email>" | mail majordomo@rtlinux.cs.nmt.edu
----
For more information on Real-Time Linux see:
http://www.rtlinux.org/~rtlinux/