From: Ilyes G. <ily...@gm...> - 2007-10-09 10:16:24
|
No, gdb is for user-space programs. You need a kernel debugger. Hmm.. I don't see any reasons for such a crash... The trivial way to debug it is to throw printk (s) in the key functions such as the probing function (in m5602.c), v4l2 allocation, start and stop functions (in m5602_v4l2.c). Are you able to see the message buffer on the console when the kernel crashes. Are you able to tell if it's an OOps or something else? Do you have the kernel call stack (the list of functions called just before the crash)? If not, can you manage to get it? Normally that trace is printed in the root console. Does your machine just hang once the kernel crashes or does it reboot automatically? BR, Ilyes Gouta. On 10/9/07, J=E9r=E9my Lal <jer...@m4...> wrote: > Ok, i just did that and reproduced the crash... > this time it crashed at about frame 6. > As expected, no file is created. > I checked the module's messages and there's nothing between the module > loading and the crash. > > how do one debugs a module ? gdb ? > > Ilyes Gouta a =E9crit : > > Hi, > > > > Welcome to kernel device drivers development :) > > > > The driver has a verbose mode through the debug option. Just load the > > driver like this: > > > > $ insmod m5602.ko debug=3D8 > > > > and you should see some nice debugging messages when doing dmesg. Then > > launch v4l2dumper like: > > > > $ v4l2dumper test > > > > Where test is the prefix used to build the filenames where the frames > > content will be dumped. > > > > BR, > > Ilyes Gouta. > > > > On 10/9/07, J=E9r=E9my Lal <jer...@m4...> wrote: > > > >> i don't get anything if i do : > >> ./v4l2dumper test > log.txt > >> > >> i'm not good at redirecting output... how could i do ? > >> > >> J=E9r=E9my Lal a =E9crit : > >> > >>> Ilyes Gouta a =E9crit : > >>> > >>> > >>>> $ gcc v4l2dumper.c -lpthread -o v4l2dumper > >>>> > >>>> > >>>> > >>> impressive result !!! > >>> i never saw such a huge crash of my laptop : instant shutdown, three > >>> reboots before it can start again ! > >>> last message i remember was something like "grabbing frame <xx>" > >>> > >>> i launched it with > >>> ./v4l2dumper test > >>> > >>> after modules were loaded : > >>> v4l1-compat > >>> videodev > >>> m5602 > >>> > >>> nothing interesting in kern.log or messages... i wonder if something = has > >>> been logged about that crash. > >>> i'm going to test it again and post the result. > >>> > >>> > >>> > >>> > >>>> BR, > >>>> Ilyes Gouta. > >>>> > >>>> On 10/9/07, J=E9r=E9my Lal <jer...@m4...> wrote: > >>>> > >>>> > >>>> > >>>>> Ilyes Gouta a =E9crit : > >>>>> > >>>>> > >>>>> > >>>>>> Hi, > >>>>>> > >>>>>> Here is the small user-space program I wrote and used to dump the = raw > >>>>>> bayer frames on R=E9mi's machine. I used to download them later on= my > >>>>>> machine and used a software (like Paint Shop Pro) to view them. Pl= ease > >>>>>> don't forget to set the picture width equal to 648. > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>> could you tell me how you compile it ? > >>>>> naively i did : > >>>>> gcc v4l2dumper.c > >>>>> > >>>>> /tmp/ccYy9RI6.o: In function `start': > >>>>> v4l2dumper.c:(.text+0x71d): undefined reference to `pthread_create' > >>>>> /tmp/ccYy9RI6.o: In function `stop': > >>>>> v4l2dumper.c:(.text+0x7b0): undefined reference to `pthread_join' > >>>>> collect2: ld returned 1 exit status > >>>>> > >>>>> thanks > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>>> BR, > >>>>>> Ilyes Gouta. > >>>>>> > >>>>>> On 10/8/07, Ilyes Gouta <ily...@gm...> wrote: > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>>> You're welcome :) > >>>>>>> > >>>>>>> On 10/8/07, J=E9r=E9my Lal <jer...@m4...> wrote: > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>>> Ilyes Gouta a =E9crit : > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>>> Hi, > >>>>>>>>> > >>>>>>>>> On 10/8/07, J=E9r=E9my Lal <jer...@m4...> wrote: > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>>> Bonjour, > >>>>>>>>>> j'ai vu que tu avais mis l'ov9650-2 dans le d=E9p=F4t svn(103)= , j'ai (avec > >>>>>>>>>> impatience !) test=E9 le module, > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>> D=E9sol=E9 J=E9r=E9my, mais je dois r=E9pondre en anglais. > >>>>>>>>> > >>>>>>>>> Yes. Yesterday, I committed my latest changes to sf.net's SVN > >>>>>>>>> repository. I had access to the machine provided by R=E9mi, dur= ing the > >>>>>>>>> previous week-end, to test it too. > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>>> mais =E7a n'a pas l'air de fonctionner avec xawtv, j'ai une er= reur de > >>>>>>>>>> segmentation, et deux messages > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>> Right now, Xawtv isn't supported. It expects RGB frames whereas= the > >>>>>>>>> driver offers only raw bayer frames (307200 bytes each) at a > >>>>>>>>> resolution of 648x474 (sensor's VGA). The OV9650 is able to pro= vide > >>>>>>>>> RGB and YUV but these aren't supported yet by my driver. > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>>> d'erreurs d'appels v4l2 non support=E9s. Cela dit, /dev/video0= est bien cr=E9=E9. > >>>>>>>>>> Peux-tu me dire o=F9 tu en es, comme =E7a je pourrai faire des= tests qui > >>>>>>>>>> correspondent... > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>> You can use LiveCam (livecam.sf.net). I wrote it a while ago (f= or the > >>>>>>>>> m5603c-mt9v011 driver) specifically to have access to the bayer > >>>>>>>>> frames, to convert them in RGB in user-space and to display the= m. It's > >>>>>>>>> a Qt 3.x application. However, to get it working with the exper= imental > >>>>>>>>> driver, you'll have to tweak the code a little bit which is ava= ilable > >>>>>>>>> through SVN (no formal releases are available yet). This mainly > >>>>>>>>> includes the V4L2 client code. You'll have also to download the= source > >>>>>>>>> version of ffmpeg and adjust the build system to refer to its i= nclude > >>>>>>>>> and lib folders (it's easy ^_^), if you want to get the MPEG-1 > >>>>>>>>> encoding feature. I'm planning to work on it this week-end to g= et it > >>>>>>>>> inline with my experimental driver. > >>>>>>>>> > >>>>>>>>> BR, > >>>>>>>>> Ilyes Gouta. > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>> ok i compiled livecam ok and as expected it doesn't work out of = the box. > >>>>>>>> I'll have a look at this later. > >>>>>>>> please note that your web page gives a wrong url for the svn rep= ository > >>>>>>>> (svn.sourceforge.net -> livecam.svn.sourceforge.net) > >>>>>>>> > >>>>>>>> i'll also try to see how your driver works so i could help imple= menting > >>>>>>>> RGB and YUV frames grabbing. > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>> > >>>> > >>> ---------------------------------------------------------------------= ---- > >>> This SF.net email is sponsored by: Splunk Inc. > >>> Still grepping through log files to find problems? Stop. > >>> Now Search log events and configuration files using AJAX and a browse= r. > >>> Download your FREE copy of Splunk now >> http://get.splunk.com/ > >>> _______________________________________________ > >>> M560x-driver-devel mailing list > >>> M56...@li... > >>> https://lists.sourceforge.net/lists/listinfo/m560x-driver-devel > >>> > >>> > >> > > > > > > > |