LINUX.IE, website of the Irish Linux Users' Group
Tux rules!

   
Home
New Users
Articles
Download
Projects
Community
Vendors

  Print Version
Email to...
 
Archives:


planetILUG

Recent News

News Archive


Join the
ILUG
on FaceBook


Join the
ILUG
on LinkedIn


Join the
ILUG SETI
Group



















 
 :: Mailing Lists

[ILUG] Device driver debugging

[ILUG] Device driver debugging

Mark Dennehy Mark.Dennehy at cs.tcd.ie
Sat Oct 13 01:14:26 IST 2001


Okay, I need suggestions!
My PhD project involves a mobile robot which is controlled by
an onboard PC104+ PC running debian 2.2 and the 2.2.19
kernel (Standard, not RTLinux). I've had to tweak the bttv
driver a bit for the framegrabber I'm using, and there are
two drivers I'm writing from scratch, one for motion control
and one for the laser rangefinder. All of which sounded like
really cool and neat stuff at the start, but for the past
four days I've been trying to make a window in a brick wall
with my head over an oops that the kernel module is causing.
It occours at the point where init_module() is exiting, which
is why I'm so puzzled - all the code I've written appears to
have happily finished and then everything goes south. 
The module then has a broken loading sequence - the /proc
files are there but they cause an oops if you use them - but
the demo test program I wrote seems to get some valid data
from the module anyway. *gah*

Here's the oops text - if anyone's seen this before, or if
anything sounds familiar, I'd appreciate the pointer!


Unable to handle kernel paging request at virtual address 76697461
current->tss.cr3 = 0317d000, %cr3 = 0317d000
*pde = 00000000
Oops: 0000
CPU:    0
EIP:    0010:[<c01c53f1>]
EFLAGS: 00010297
eax: 76697461   ebx: c3ab3009   ecx: 76697461   edx: fffffffe
esi: ffffffff   edi: c217bed8   ebp: ffffffff   esp: c217be7c
ds: 0018   es: 0018   ss: 0018
Process insmod (pid: 881, process nr: 30, stackpage=c217b000)
Stack: 00000000 00000034 c3c073e8 c2ac00a0 c3c073e8 00000000 c2ac00a0 c2ac00a0 
       c3c073e8 c01c5566 c3ab3000 c01c9e79 c217becc c3ee2be0 c333c0c0 00001000 
       40017000 c01156ab c3ab3000 c01c9e72 00000008 6c65725f 76697461 c484aec0 
Call Trace: [<c01c5566>] [<c01c9e79>] [<c01156ab>] [<c01c9e72>] [<c484aec0>] [<c012b501>] [<c014dcdd>] 
       [<c014dfd1>] [<c014df1e>] [<c01240aa>] [<c0107b95>] [<c0107a78>] 
Code: 80 38 00 74 07 40 4a 83 fa ff 75 f4 29 c8 89 c6 8b 54 24 1c 

This is reproducable BTW, and the klogd version is happily
blaming sprintf for the fault. As it's a module, getting the
addresses translated is a problem so I dont know if I can
trust klogd or ksymoops' output.

-- 
Mark Dennehy, 				Email : Mark.Dennehy at cs.tcd.ie
Computer Vision and Robotics Research Group,
Computer Science Dept., Trinity College Dublin		




More information about the ILUG mailing list
Read this without the formatting.
                                                                                                    

 

Hosted by HEAnet


Maintained by the ILUG website team. The aim of Linux.ie is to support and help commercial and private users of Linux in Ireland. You can display ILUG news in your own webpages, read backend information to find out how. Networking services kindly provided by HEAnet, server kindly donated by Dell. Linux is a trademark of Linus Torvalds, used with permission. No penguins were harmed in the production or maintenance of this highly praised website. Looking for the Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
RSS Version
Powered by Dell